[SOLVED] Netgear Stora - type Control-D to continue...

I've finally dusted off my old Stora and this weekend "upgraded" to Debian with the new 4.8 Kernel.

When I boot from Hard Disk I am being presented with the following output;

INIT: Entering runlevel: 1
[info] Using makefile-style concurrent boot in runlevel 1.
[ ok ] Asking all remaining processes to terminate...done.
[ ok ] All processes ended within 1 seconds....done.
[info] Will now switch to single-user mode.
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
Give root password for maintenance
(or type Control-D to continue):

having to type Ctrl-D in order to get it to finish booting. below is the output from printenv;

Netgear Stora> printenv
arcNumber=2743
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 bootdelay 1
bootcmd=ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; bootargs $(console) root=LABEL=rootfs rootdelay=10; bootm 0x800000 0x1100000; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=aa:bb:cc:dd:ee:ff (changed)
ipaddr=192.168.10.2
mainlineLinux=yes
rootfstype=ext2
serverip=192.168.10.1
set=bootargs_usb
stderr=serial
stdin=serial
stdout=serial
usb=start
usb_root=/dev/sda1

It should be noted that when first "built" I was booting from USB, though found it gave I/O errors at times so moved to HD

Seems that the "transition" from USB to HDD boot required additional updates / changes to the boot loader config, which now looks like this;

arcNumber=2743
baudrate=115200
bootargs=ttyS0,115200 root=LABEL=rootfs bootdelay 10
bootcmd=ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; rootdelay=10; bootm 0x800000 0x1100000; reset
console=ttyS0,115200
ethact=egiga0
ethaddr=aa:bb:cc:dd:ee:ff (changed)
ipaddr=192.168.10.2
mainlineLinux=yes
rootfstype=ext3
serverip=192.168.10.1
stderr=serial
stdin=serial
stdout=serial



Edited 1 time(s). Last edit at 10/12/2016 02:27AM by beggles.

beggles,

This usually has a couple of reasons. You should have posted the entire bootlog (not snipet where problem occurred). However, here are possible reasons: either your rootfs has file system errors, or the rootfs could not be mounted because of wrong u-boot envs for bootargs.

Based on your u-boot envs, bootargs seems to be the cause. These envs were malformed:

bootcmd=ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; bootargs $(console) root=LABEL=rootfs rootdelay=10; bootm 0x800000 0x1100000; reset
set=bootargs_usb
usb=start

Power up, interrupt serial console and

setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 root=LABEL=rootfs rootdelay=10'
setenv bootcmd 'ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000; reset'
boot

After you've booted this way a couple times successfully, then save it permenently before boot

setenv bootargs 'console=ttyS0,115200 root=/dev/sda1 root=LABEL=rootfs rootdelay=10'
setenv bootcmd 'ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000; reset'
saveenv
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for the reply bodhi,

I'm guessing it was boot arguments too. I've managed to successfully boot a few times now, so am comfortable in calling it "case closed". As you will have noticed, I have carried out a cleanup of the "u-boot envs", and removed all superfluous entries.

Thanks again,
beggles

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)