E02 no ssh after pacman -Syu

[karog]

I have been running up to date on an E02 with a USB hard drive, /boot on /dev/sda1 ext2 and / on /dev/sda2 ext4.

Today (2012/07/17) I did a pacman -Syu and several things updated including new initscripts (often a danger it seems). After reboot the E02 appears to come up with solid LED but no ssh access and does not appear in my router device list as it normally does.

I formatted a USB flash drive to ext2 and installed a new rootfs and can boot from that with ssh access and can then mount the USB hard drive.

After having failed to boot with the hard drive and then mounting it after booting from flash, I looked in /media/rootfs/var/log and there appears to be nothing new since the pacman update and reboot.

I am seeking suggestions on what to do next. Any ideas?

Here is the pacman.log
$this->bbcode_second_pass_code('', '
[2012-07-17 09:39] Running 'pacman -Syu'
[2012-07-17 09:39] synchronizing package lists
[2012-07-17 09:39] starting full system upgrade
[2012-07-17 09:40] upgraded libsystemd (185-4.1 -> 186-2)
[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.
[2012-07-17 09:40] upgraded kmod (9-1 -> 9-2)
[2012-07-17 09:40] upgraded util-linux (2.21.2-3 -> 2.21.2-5)
[2012-07-17 09:40] upgraded systemd-tools (185-4.1 -> 186-2)
[2012-07-17 09:40] upgraded initscripts (2012.06.1-1 -> 2012.06.3-2.1)
[2012-07-17 09:40] >>> Updating module dependencies. Please wait ...
[2012-07-17 09:40] upgraded linux (3.1.10-11 -> 3.1.10-12)
[2012-07-17 09:41] upgraded linux-headers (3.1.10-11 -> 3.1.10-12)
[2012-07-17 09:41] upgraded lirc-utils (1:0.9.0-18 -> 1:0.9.0-20)
[2012-07-17 09:41] upgraded perl-dbi (1.618-2 -> 1.622-1)
[2012-07-17 09:41] upgraded perl-error (0.17017-1 -> 0.17018-1)
[2012-07-17 09:41] upgraded procps-ng (3.3.3-1 -> 3.3.3-3)
[2012-07-17 09:41] upgraded smartmontools (5.42-4 -> 5.43-1)
[2012-07-17 09:41] upgraded syslog-ng (3.3.5-1.1 -> 3.3.5-2)
')

[WarheadsSE]

Pretty 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.

[karog]

$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.

[WarheadsSE]

Have a look at the rest of the logs, specifically dmesg/everything.

[karog]

$this->bbcode_second_pass_quote('WarheadsSE', 'H')ave a look at the rest of the logs, specifically dmesg/everything.

[corbo]

I believe my Dockstar is having the same issue. I've even started fresh. I dropped the rootfs onto my drive and updated again to the same results. Nothing in the logs after the reboot.

[portnumber53]

mv /lib/modules/2.6.31.6_SMP_820 /usr/lib/modules

seems to solve this problem for me.

I also did
cp /lib/modules/gmac_copro_firmware /usr/lib/modules
just for the sake of doing it

[karog]

$this->bbcode_second_pass_quote('portnumber53', 'm')v /lib/modules/2.6.31.6_SMP_820 /usr/lib/modules

seems to solve this problem for me.

I also did
cp /lib/modules/gmac_copro_firmware /usr/lib/modules
just for the sake of doing it

[corbo]

I rebuilt again last night. I've updated now, but haven't rebooted. Looking in /lib, I have no modules directories. Just have some files owned by glibc.

Rebooting at this point, the system will not come backup. So as much as I wish it was the /lib/modules -> /usr/lib/modules issue, it doesn't seem to be so.

[BrianD]

I have a similar setup on an E02, separate /boot and / partitions, and experienced the same issue. After connecting a serial cable, I found the following:

$this->bbcode_second_pass_code('', 'Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2857200 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-12-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2857136 Bytes = 2.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 5.250578] rtc-mv rtc-mv: internal RTC not ticking
[ 5.258663] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
INIT: version 2.88 booting

> Arch Linux ARM

> http://www.archlinuxarm.org

------------------------------
:: Mounting Root Read-Only [BUSY] [FAIL]
:: Adjusting system time and setting kernel timezone [BUSY] [DONE]
:: Starting UDev Daemon [BUSY] [DONE]
:: Triggering UDev uevents [BUSY] [DONE]
:: Loading User-specified Modules [BUSY] [DONE]
:: Waiting for UDev uevents to be processed [BUSY] [DONE]
:: Configuring Virtual Consoles [BUSY] G [DONE]
:: Bringing up loopback interface [BUSY] [DONE]
:: Unlocking encrypted volumes [BUSY] [DONE]
:: Checking Filesystems [BUSY] /dev/sda2 is mounted.
e2fsck: Cannot continue, aborting.


[FAIL]

***************** FILESYSTEM CHECK FAILED ****************
* *
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write type: mount -o remount,rw / *
* When you exit the maintenance shell the system will *
* reboot automatically. *
* *
************************************************************

Give root password for maintenance
(or type Control-D to continue): ')

After editing the /etc/fstab and disabling fsck on all partitions, the unit will now successfully boot.