Hello,
I encountered an issue while trying to setup debian on my Netgear Stora. The thing is that I did everything mentioned in this tutorial but I managed to get into mounting error while booting into the system.
Error:
The Debian is booted from USB formatted in ext2 in MBR/DOS partition scheme. After this error I'm being dropped into initramfs busybox shell.
fstab:
I also tried with noatime,errors=remount-ro fstab option but ended up with same result. I'm connected to Stora via RS232 to TTL adapter made with arduino so I'm operating from serial console.
Output after typing ' dmesg | grep -i 'bad' ':
Setenv commands executed in Marvell u-boot:
Interestingly after typing usb reset I'm no longer able to see my connected USB and the ext2ls command returns Bad parition message. After restarting and typing exactly same command I can list all files on the USB. That's why after I deleted the usb reset command from bootcmd environmental variable.
Thats actually my very first time doing something like this and I'm sure I messed something up.
Thanks in advance,
TheYanusz
P.S
Sorry for bad spelling
I encountered an issue while trying to setup debian on my Netgear Stora. The thing is that I did everything mentioned in this tutorial but I managed to get into mounting error while booting into the system.
Error:
Begin: Will now check root file system ... fsck from util-linux 2.38.1 fsck: error 2 (No such file or directory) while executing fsck.ext2 for /dev/sda1 fsck exited with status code 8 done. Warning: File system check failed but did not detect errors mount: mounting /dev/sda1 on /root failed: No such device Failed to mount /dev/sda1 as root file system.
The Debian is booted from USB formatted in ext2 in MBR/DOS partition scheme. After this error I'm being dropped into initramfs busybox shell.
fstab:
LABEL=rootfs / ext2 defaults 0 2
I also tried with noatime,errors=remount-ro fstab option but ended up with same result. I'm connected to Stora via RS232 to TTL adapter made with arduino so I'm operating from serial console.
Output after typing ' dmesg | grep -i 'bad' ':
[ 5.922319][ T1] Scanning device for bad blocks [ 5.970409][ T1] Bad eraseblock 400 at 0x000003200000 [ 5.976034][ T1] Bad eraseblock 403 at 0x000003260000 [ 5.982949][ T1] Bad eraseblock 418 at 0x000003440000 [ 6.012720][ T1] Bad eraseblock 645 at 0x0000050a0000 [ 6.113638][ T1] Bad eraseblock 1532 at 0x00000bf80000 [ 6.119187][ T1] Bad eraseblock 1533 at 0x00000bfa0000 [ 6.131852][ T1] Bad eraseblock 1600 at 0x00000c800000 [ 6.137403][ T1] Bad eraseblock 1601 at 0x00000c820000 [ 6.181632][ T1] Bad eraseblock 1960 at 0x00000f500000 [ 6.187178][ T1] Bad eraseblock 1961 at 0x00000f520000 [ 6.199409][ T1] Bad eraseblock 2024 at 0x00000fd00000 [ 6.204934][ T1] Bad eraseblock 2025 at 0x00000fd20000
Setenv commands executed in Marvell u-boot:
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial' setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' setenv load_uinitrd 'ext2load usb 0:1 0x2100000 /boot/uInitrd' setenv usb_boot 'mw 0x800000 0 1; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000' setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot' setenv bootcmd 'run usb_bootcmd; usb stop; reset'
Interestingly after typing usb reset I'm no longer able to see my connected USB and the ext2ls command returns Bad parition message. After restarting and typing exactly same command I can list all files on the USB. That's why after I deleted the usb reset command from bootcmd environmental variable.
Thats actually my very first time doing something like this and I'm sure I messed something up.
Thanks in advance,
TheYanusz
P.S
Sorry for bad spelling