E02 no ssh after pacman -Syu

[maik]

@BrainD

I have the same Problem.
What have you changed in your /etc/fstab?
How can I disable the fsck?

[corbo]

Set the last number on each line to 0.

For more info see:
http://www.tuxfiles.org/linuxhelp/fstab.html

Looks like it worked. Thank you Mr. BrianD sir.

[karog]

@BrianD (I like maik's ref as BrainD )

The fstab fix worked for me too. Thanks so much.

But what is the underlying problem that we can no longer have the fsck?

As I have my rootfs on /dev/sda2 as ext4 and had no other method to access ext4 other than my E02, when I setup a new flash drive, it did not work at first and I had to use install_uboot_mtd0.sh to get it to work. Later when I tried the fstab fix it did not work at first but I had forgotten to reset the fw env usb_* params for ext4 and sda2. Once I fixed that, bingo!

I also was going to try to make a serial cable. I have an old pc waiting for electronic recycling and I found an audio cable in it from the old CD-ROM to a sound card. But the connectors were too wide (as wide as the outer edge of the board connector) and the holes were just a bit too far apart. I thought such a connector was supposed to fit. Well not mine. Sigh.

[BrianD]

As I am very green (noob) with Linux, I can only speculate, but it appears changes to the /etc/rc.sysinit file with the newer initscripts is the likely culprit.

[corbo]

I'm hoping at some point we can return to fsck'ing on startup. I like to keep my filesystem clean, if you know what I mean.

[BrianD]

After a little more testing, I believe I have corrected, at least temporarily, the source of the trouble. It appears when the following bootlogd command is placed PRIOR to remounting root as read-only, the remount will fail; this will also cause the fsck to fail when the root and boot are on different partitions. Note, the failure to mount the root as read-only most likely occurs on all devices using initscripts-2012.06.3-2.1

/etc/rc.sysinit$this->bbcode_second_pass_code('', '# log all console messages
bootlogd -p /run/bootlogd.pid

if [[ ! -e /run/initramfs/root-fsck ]]; then
# remount root ro to allow for fsck later on, we remount now to
# make sure nothing can open files rw on root which would block a remount
findmnt / --options ro &>/dev/null ||
status "Mounting Root Read-Only" mount -o remount,ro /
fi
')

I simply commented out the bootlogd command in the /etc/rc.sysinit file then re-enabled fsck in /etc/fstab. Now after reboot, all is well (until after another upgrade to initscripts)

[alfred1]

$this->bbcode_second_pass_quote('WarheadsSE', 'P')retty straight forward
$this->bbcode_second_pass_code('', '
[2012-07-17 09:40] ==> Kernel modules are now only read from /usr/lib/modules, all custom
[2012-07-17 09:40] built kernels and modules must be moved there before rebooting.
')

Check /media/rootfs/lib for modules. If it is is there, move it. We've moved them in the new kernel packages. Upstream bit us on that one.

$this->bbcode_second_pass_quote('alfred1', '')$this->bbcode_second_pass_quote('WarheadsSE', 'P')retty straight forward
[path to usb disk]/lib/ to [path to usb disk]/usr/lib/
with sudo cp -R lib/* usr/lib/

[corbo]

I see initscripts was updated today. Has anyone tried enabling fsck on startup without commenting out logging?

[BrianD]

The updated /etc/rc.sysinit file packaged with initscripts-2012.07.5-1 works like a champ on my E02 devices. It appears they moved the bootlogd to run after remounting the / root partition....

$this->bbcode_second_pass_code('', '
if [[ ! -e /run/initramfs/root-fsck ]]; then
# remount root ro to allow for fsck later on, we remount now to
# make sure nothing can open files rw on root which would block a remount

findmnt / --options ro &>/dev/null ||
status "Mounting root read-only" mount -o remount,ro /
fi

# log all console messages

bootlogd -p /run/bootlogd.pid
')