Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nano boot fails(kernel panic) #17

Open
kevinyeah00 opened this issue Mar 30, 2022 · 25 comments
Open

Nano boot fails(kernel panic) #17

kevinyeah00 opened this issue Mar 30, 2022 · 25 comments

Comments

@kevinyeah00
Copy link

Thank you very much for the image!
I used balenaEtcher to flash this image to a 128GB SD Card, but I can't boot my Jetson Nano B01 4GB, it shows:

[1.175793] tegradc tegradc.1: dpd enable lookup fail:-19
[1.323835] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
[1.323901] imx219 7-0010: board setup failed
[1.347757] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
[1.347815] imx219 8-0010: board setup failed
cp: not writing throught dangling symlink 'etc/resolve.conf'
[2.404920] Kernel panic - not syncing:Attempted to kill init! exitcode=0x00000000
[2.404920]
[2.414104] CPU:1 Pid: 1 Comm: sh Not tainted 4.9.253-tegra #1
[2.420047] Hardware name: NVIDIA Jetson Nano Developer Kit(DT)
[2.426075] Call trace:
……
……
……
[2.575663] Rebooting in 5 seconds..

and reboot endlessly...

Could you give me some suggestions about it?
It would be nice if you provide the md5sum of this image, then I can see if I had trouble downloading the image.

@Qengineering
Copy link
Owner

Qengineering commented Mar 30, 2022

See if this helps you: JetsonNano.zip md5sum: d186a59a0b4d95a3bb9a327feabbfa25

@dmvoro
Copy link

dmvoro commented Mar 31, 2022

I ve got the same problem on my 3 sd cards. Maybe something went wrong with the image?
I checked md5 of an image - its wrong - 1e8ad1525cad58f920ae63df47901b2c

@kevinyeah00
Copy link
Author

I downloaded the image again and this time it worked, It should be about 31GB, my md5 is 1e8ad1525cad58f920ae63df47901b2c, just the same as yours ,but it works. Maybe there's something wrong with your card reader?

@DeerLickObservatory
Copy link

DeerLickObservatory commented Jun 13, 2022

Hi!
I ran into this issue as well, same log and reboot cycle. I re-flashed twice before checking here.
Here's my file's md5:

bucky ~ % md5 Jetson\ Nano/JetsonNano.img 
MD5 ( ~/Jetson Nano/JetsonNano.img) = 0e928f21c3e536e4461aaf00087ebfe6

bucky ~ % md5 Jetson\ Nano/JetsonNano.zip 
MD5 (~/Jetson Nano/JetsonNano.zip) = d186a59a0b4d95a3bb9a327feabbfa25

My .zip file matched the author's expected md5, but the unzipped didn't--and thats when I thought to try just dragging the .zip file into balenaEtcher, instead of the unzipped .img

After flashing, the Jetson Nano boots successfully. Can anyone else confirm if they were trying to write the .img or the .zip? balenaEtcher will successfully take and write both, but it seems only the .zip one produces a bootable system.

@turowicz
Copy link

turowicz commented Sep 15, 2022

Same problem here booting from 256GB USB stick. It is in a reboot loop cycle until it finally boots up. Must try different USB sticks.

I am using the Jetson Mate carrier board and Xavier NX (production).

@alana314
Copy link

Thanks for this image! I couldn't get the .img.xz file to work with balenaEtcher, but it did work with Pi Imager.

@garvitkhera
Copy link

Thanks for this image! I couldn't get the .img.xz file to work with balenaEtcher, but it did work with Pi Imager.

Same!!

@taothienpeter
Copy link

Help! I tried to flash it with both Pi imager and balenaEtcher, but nothing works
image
I tried to check for the MD5, SHA-1 from the downloaded file

  • MD5: d738f1fe20088a1bdbd10e2358b512f7
  • SHA-1: b5ca8b13031478b75b2faef366f193bcf0c31728
    and it does not match the ones you guys have. Also, the image did not come with its MD5 so I can't check from the source
    Im working with the jetson nano Dev kit 4Gb and try to boot it with Ubuntu 20.04 for ROS2

@Qengineering
Copy link
Owner

We apologize for the inconvenience. At the moment Sync has serious server issues. Pleas try to download later again.
(Qengineering/Jetson-Nano-Ubuntu-20-image#92)

@taothienpeter
Copy link

We apologize for the inconvenience. At the moment Sync has serious server issues. Pleas try to download later again. (Qengineering/Jetson-Nano-Ubuntu-20-image#92)

is it still the same md5sum (d186a59a0b4d95a3bb9a327feabbfa25) as above?

@Qengineering
Copy link
Owner

The md5sum of JetsonNano.img.xz : 621F2E4E0B7775E5293E2186C96E91AA
Please note, it is the img.xz download, not the old *.zip one.

@osamaabdelatif
Copy link

I have downloaded the image couple of times, but never managed to get the same md5sum mentioned above, nor having it booting on the Jetson Nano.

@Qengineering
Copy link
Owner

Qengineering commented Sep 2, 2024

To be sure, I downloaded the image myself from the Sync fileserver and checked its md5sum. It should work:
image

@rishikoushikz
Copy link

i too have the same problem i download it now
Screenshot 2024-09-03 150632
Screenshot 2024-09-03 150648

@osamaabdelatif
Copy link

Again i test another download today and i am getting the same reported by @rishikoushikz

Capture

@Qengineering
Copy link
Owner

Your download has the correct MD5 sum.
Please see: Qengineering/Jetson-Nano-Ubuntu-20-image#96 (comment)

@osamaabdelatif
Copy link

Thank you for confirming the MD5 sum, since it's the correct image, after writing it using balenaEtcher. the device isn't booting. i am getting below screen.
Capture

@Qengineering
Copy link
Owner

@osamaabdelatif
Copy link

Hi, yes i saw the comment and actually tried both balenaEtcher and Raspberry Pi Imager both didn't work.

@Qengineering
Copy link
Owner

Still, it boils down on a hardware issue with you card. Your download is good. Your Jetson Nano is good.
BTW, you erased the SD card before flashing? Not just a quick format.

@osamaabdelatif
Copy link

I have formatted the SSD with 7 security-check to ensure it's totally erased, still same issue.
even used another brand new SSD for that and didn't work either. Not sure if someone test to write this image recently and boot Jetson Nano from it.

@osamaabdelatif
Copy link

I check the SSD image after writing on another system,
sudo fsck /dev/sdb
fsck from util-linux 2.37.2
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768

Found a gpt partition table in /dev/sdb

#checking all the superblocks
sudo dumpe2fs /dev/sdb1 | grep superblock
dumpe2fs 1.46.5 (30-Dec-2021)
Primary superblock at 0, Group descriptors at 1-2
Backup superblock at 32768, Group descriptors at 32769-32770
Backup superblock at 98304, Group descriptors at 98305-98306
Backup superblock at 163840, Group descriptors at 163841-163842
Backup superblock at 229376, Group descriptors at 229377-229378
Backup superblock at 294912, Group descriptors at 294913-294914
Backup superblock at 819200, Group descriptors at 819201-819202
Backup superblock at 884736, Group descriptors at 884737-884738
Backup superblock at 1605632, Group descriptors at 1605633-1605634
Backup superblock at 2654208, Group descriptors at 2654209-2654210
Backup superblock at 4096000, Group descriptors at 4096001-4096002

and repairing the first one

sudo e2fsck -b 32768 /dev/sdb1
e2fsck 1.46.5 (30-Dec-2021)
/dev/sdb1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (0, counted=130).
Fix? yes
Free blocks count wrong for group #1 (0, counted=3692).
Fix? yes
Free blocks count wrong for group #2 (0, counted=341).
Fix? yes
Free blocks count wrong for group #3 (0, counted=1312).
Fix? yes
Free blocks count wrong for group #11 (0, counted=4200).
Fix? yes
Free blocks count wrong for group #13 (0, counted=841).
Fix? yes
Free blocks count wrong for group #17 (0, counted=15).
Fix? yes
Free blocks count wrong for group #18 (0, counted=42).
Fix? yes
Free blocks count wrong for group #23 (0, counted=812).
Fix? yes
Free blocks count wrong for group #24 (0, counted=6706).
Fix ('a' enables 'yes' to all) ? yes
Free blocks count wrong for group #25 (0, counted=396).
Fix ('a' enables 'yes' to all) ? yes
Free blocks count wrong for group #26 (0, counted=11150).
Fix ('a' enables 'yes' to all) ? yes
Free blocks count wrong for group #27 (0, counted=1024).
Fix ('a' enables 'yes' to all) ? yes
Free blocks count wrong for group #28 (0, counted=3719).
Fix? yes
Free blocks count wrong for group #29 (0, counted=5086).
Fix? yes
Free blocks count wrong for group #32 (0, counted=1).
Fix? yes
Free blocks count wrong for group #33 (0, counted=86).
Fix? yes
Free blocks count wrong for group #34 (0, counted=626).
Fix? yes
Free blocks count wrong for group #36 (0, counted=3).
Fix? yes
Free blocks count wrong for group #37 (0, counted=201).
Fix? yes
Free blocks count wrong for group #38 (0, counted=458).
Fix? yes
Free blocks count wrong for group #39 (0, counted=1).
Fix? yes
Free blocks count wrong for group #40 (0, counted=15).
Fix? yes
Free blocks count wrong for group #41 (0, counted=515).
Fix? yes
Free blocks count wrong for group #42 (0, counted=868).
Fix? yes
Free blocks count wrong for group #43 (0, counted=5542).
Fix? yes
Free blocks count wrong for group #44 (0, counted=85).
Fix? yes
Free blocks count wrong for group #50 (0, counted=82).
Fix? yes
Free blocks count wrong for group #51 (0, counted=4099).
Fix? yes
Free blocks count wrong for group #52 (0, counted=259).
Fix? yes
Free blocks count wrong for group #53 (0, counted=925).
Fix? yes
Free blocks count wrong for group #54 (0, counted=16).
Fix? yes
Free blocks count wrong for group #55 (0, counted=1).
Fix? yes
Free blocks count wrong for group #56 (0, counted=2).
Fix? yes
Free blocks count wrong for group #57 (0, counted=1966).
Fix? yes
Free blocks count wrong for group #58 (0, counted=6).
Fix? yes
Free blocks count wrong for group #65 (0, counted=371).
Fix? yes
Free blocks count wrong for group #66 (0, counted=163).
Fix? yes
Free blocks count wrong for group #80 (0, counted=1).
Fix? yes
Free blocks count wrong for group #81 (0, counted=561).
Fix? yes
Free blocks count wrong for group #82 (0, counted=4).
Fix? yes
Free blocks count wrong for group #83 (0, counted=629).
Fix? yes
Free blocks count wrong for group #84 (0, counted=5590).
Fix? yes
Free blocks count wrong for group #85 (0, counted=7074).
Fix? yes
Free blocks count wrong for group #86 (0, counted=5227).
Fix? yes
Free blocks count wrong for group #87 (0, counted=132).
Fix? yes
Free blocks count wrong for group #88 (0, counted=8304).
Fix? yes
Free blocks count wrong for group #89 (0, counted=708).
Fix? yes
Free blocks count wrong for group #96 (0, counted=14).
Fix? yes
Free blocks count wrong for group #99 (0, counted=444).
Fix? yes
Free blocks count wrong for group #100 (0, counted=758).
Fix? yes
Free blocks count wrong for group #101 (0, counted=6569).
Fix? yes
Free blocks count wrong for group #102 (0, counted=14711).
Fix? yes
Free blocks count wrong for group #103 (0, counted=8625).
Fix? yes
Free blocks count wrong for group #104 (0, counted=3360).
Fix? yes
Free blocks count wrong for group #105 (0, counted=10524).
Fix? yes
Free blocks count wrong for group #106 (0, counted=16498).
Fix? yes
Free blocks count wrong for group #107 (0, counted=4589).
Fix? yes
Free blocks count wrong for group #108 (0, counted=2125).
Fix? yes
Free blocks count wrong for group #109 (0, counted=6054).
Fix? yes
Free blocks count wrong for group #110 (0, counted=5293).
Fix? yes
Free blocks count wrong for group #111 (0, counted=303).
Fix? yes
Free blocks count wrong for group #112 (0, counted=4066).
Fix? yes
Free blocks count wrong for group #113 (0, counted=25).
Fix? yes
Free blocks count wrong for group #114 (0, counted=305).
Fix? yes
Free blocks count wrong for group #115 (0, counted=10920).
Fix? yes
Free blocks count wrong for group #116 (0, counted=18471).
Fix? yes
Free blocks count wrong for group #117 (0, counted=12146).
Fix? yes
Free blocks count wrong for group #118 (0, counted=5552).
Fix? yes
Free blocks count wrong for group #119 (0, counted=10437).
Fix? yes
Free blocks count wrong for group #120 (0, counted=9804).
Fix? yes
Free blocks count wrong for group #121 (0, counted=9676).
Fix? yes
Free blocks count wrong for group #122 (0, counted=11154).
Fix? yes
Free blocks count wrong for group #123 (0, counted=18238).
Fix? yes
Free blocks count wrong for group #124 (0, counted=15425).
Fix? yes
Free blocks count wrong for group #125 (0, counted=11061).
Fix? yes
Free blocks count wrong for group #126 (0, counted=13202).
Fix? yes
Free blocks count wrong for group #127 (0, counted=7950).
Fix? yes
Free blocks count wrong for group #128 (0, counted=205).
Fix? yes
Free blocks count wrong for group #129 (0, counted=2223).
Fix? yes
Free blocks count wrong for group #130 (0, counted=4450).
Fix? yes
Free blocks count wrong for group #131 (2401, counted=13461).
Fix? yes
Free blocks count wrong for group #132 (6412, counted=6973).
Fix? yes
Free blocks count wrong for group #133 (11123, counted=11137).
Fix? yes
Free blocks count wrong for group #134 (13192, counted=11505).
Fix? yes
Free blocks count wrong for group #135 (9016, counted=6493).
Fix? yes
Free blocks count wrong for group #136 (6000, counted=5391).
Fix? yes
Free blocks count wrong for group #138 (1572, counted=1029).
Fix? yes
Free blocks count wrong for group #140 (3693, counted=3769).
Fix? yes
Free blocks count wrong for group #145 (7389, counted=7481).
Fix? yes
Free blocks count wrong for group #151 (4739, counted=5554).
Fix? yes
Free blocks count wrong for group #153 (9283, counted=9287).
Fix? yes
Free blocks count wrong for group #155 (6194, counted=10096).
Fix? yes
Free blocks count wrong for group #156 (4258, counted=5980).
Fix? yes
Free blocks count wrong for group #157 (6536, counted=8082).
Fix? yes
Free blocks count wrong for group #160 (6773, counted=7618).
Fix? yes
Free blocks count wrong for group #161 (1889, counted=1990).
Fix? yes
Free blocks count wrong for group #162 (12508, counted=12956).
Fix? yes
Free blocks count wrong for group #164 (24000, counted=25333).
Fix? yes
Free blocks count wrong for group #165 (32768, counted=24601).
Fix? yes
Free blocks count wrong for group #166 (32768, counted=19987).
Fix? yes
Free blocks count wrong for group #167 (32768, counted=7293).
Fix? yes
Free blocks count wrong for group #168 (32768, counted=3863).
Fix? yes
Free blocks count wrong for group #170 (32768, counted=31870).
Fix? yes
Free blocks count wrong for group #171 (32768, counted=6107).
Fix? yes
Free blocks count wrong for group #172 (32768, counted=6507).
Fix? yes
Free blocks count wrong for group #173 (32768, counted=2742).
Fix? yes
Free blocks count wrong for group #174 (32768, counted=2479).
Fix? yes
Free blocks count wrong for group #175 (32768, counted=596).
Fix? yes
Free blocks count wrong for group #176 (6702, counted=11246).
Fix? yes
Free blocks count wrong for group #177 (23760, counted=2041).
Fix? yes
Free blocks count wrong for group #178 (32768, counted=24326).
Fix? yes
Free blocks count wrong for group #179 (32632, counted=21419).
Fix? yes
Free blocks count wrong for group #180 (32768, counted=28588).
Fix? yes
Free blocks count wrong for group #181 (32768, counted=20345).
Fix? yes
Free blocks count wrong for group #182 (32768, counted=31204).
Fix? yes
Free blocks count wrong for group #183 (32768, counted=32732).
Fix? yes
Free blocks count wrong for group #188 (31380, counted=32768).
Fix? yes
Free blocks count wrong for group #192 (22860, counted=25265).
Fix? yes
Free blocks count wrong for group #198 (15840, counted=15901).
Fix? yes
Free blocks count wrong for group #202 (1655, counted=1654).
Fix? yes
Free blocks count wrong (1301338, counted=1374844).
Fix? yes
Inode bitmap differences: -(974849--1048576) -(1081345--1179648) -(1204225--1310720) -(1327105--1329459) -(1329461--132 9499) -(1330906--1331395) -(1335297--1335303) -(1343489--1441792) -(1449985--1449987) -(1458177--1572864) -(1597441--168 7552)
Fix? yes
Free inodes count wrong for group #0 (1704, counted=6799).
Fix? yes
Directories count wrong for group #0 (324, counted=208).
Fix? yes
Free inodes count wrong for group #1 (8186, counted=8192).
Fix? yes
Directories count wrong for group #1 (6, counted=0).
Fix? yes
Free inodes count wrong for group #32 (11, counted=14).
Fix? yes
Free inodes count wrong for group #33 (0, counted=58).
Fix? yes
Free inodes count wrong for group #34 (0, counted=199).
Fix? yes
Free inodes count wrong for group #35 (56, counted=455).
Fix? yes
Free inodes count wrong for group #36 (0, counted=1).
Fix? yes
Free inodes count wrong for group #38 (0, counted=2).
Fix? yes
Free inodes count wrong for group #39 (481, counted=38).
Fix? yes
Free inodes count wrong for group #40 (1261, counted=1032).
Fix? yes
Free inodes count wrong for group #44 (8068, counted=8064).
Fix? yes
Directories count wrong for group #44 (124, counted=128).
Fix? yes
Free inodes count wrong for group #48 (2, counted=35).
Fix? yes
Free inodes count wrong for group #49 (81, counted=49).
Fix? yes
Free inodes count wrong for group #64 (847, counted=850).
Fix? yes
Free inodes count wrong for group #68 (7831, counted=7830).
Fix? yes
Directories count wrong for group #68 (361, counted=362).
Fix? yes
Free inodes count wrong for group #80 (1271, counted=187).
Fix? yes
Free inodes count wrong for group #81 (576, counted=33).
Fix? yes
Free inodes count wrong for group #82 (1927, counted=9).
Fix? yes
Free inodes count wrong for group #83 (5670, counted=5212).
Fix? yes
Free inodes count wrong for group #84 (7921, counted=7877).
Fix? yes
Directories count wrong for group #84 (17, counted=61).
Fix? yes
Free inodes count wrong for group #96 (2413, counted=2224).
Fix? yes
Directories count wrong for group #96 (529, counted=525).
Fix? yes
Free inodes count wrong for group #97 (3560, counted=3673).
Fix? yes
Free inodes count wrong for group #98 (1079, counted=1092).
Fix? yes
Directories count wrong for group #98 (374, counted=372).
Fix? yes
Free inodes count wrong for group #99 (7709, counted=7716).
Fix? yes
Directories count wrong for group #99 (120, counted=115).
Fix? yes
Free inodes count wrong for group #112 (196, counted=238).
Fix? yes
Directories count wrong for group #112 (802, counted=800).
Fix? yes
Free inodes count wrong for group #113 (2808, counted=2809).
Fix? yes
Free inodes count wrong for group #115 (7077, counted=7069).
Fix? yes
Directories count wrong for group #115 (1115, counted=1123).
Fix? yes
Free inodes count wrong for group #117 (2252, counted=2254).
Fix? yes
Directories count wrong for group #117 (361, counted=359).
Fix? yes
Free inodes count wrong for group #128 (70, counted=440).
Fix? yes
Directories count wrong for group #128 (716, counted=711).
Fix? yes
Free inodes count wrong for group #129 (2662, counted=1394).
Fix? yes
Free inodes count wrong for group #130 (3894, counted=4839).
Fix? yes
Free inodes count wrong for group #131 (8116, counted=8115).
Fix? yes
Directories count wrong for group #131 (76, counted=77).
Fix? yes
Free inodes count wrong for group #144 (2257, counted=2258).
Fix? yes
Free inodes count wrong for group #160 (8129, counted=8192).
Fix? yes
Directories count wrong for group #160 (13, counted=0).
Fix? yes
Free inodes count wrong (1444699, counted=1445833).
Fix? yes
Padding at end of inode bitmap is not set. Fix? yes

/dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sdb1: 241719/1687552 files (0.4% non-contiguous), 5357956/6732800 blocks

@Qengineering
Copy link
Owner

I did test the image myself a few days ago. Everything just fine, no problem.
Did I read it right? SSD? It works only with an SD card.
For an SSD version, please look at Qengineering/Jetson-Nano-Ubuntu-20-image#32, and other related issues.

@osamaabdelatif
Copy link

it's SD card, ScanDisk. i am trying all option to get that image work in a boot way. is there any thing missing?

@Qengineering
Copy link
Owner

Can you flash the SD card with a regular Jetpack Nano OS. And does it boot?
Once again, I've tested it, and it works like a charm. Somehow your image isn't flashed correctly.
The The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt hints on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants