Starting Kernel Hang

[dixonl90]

Hello,

I've been happily running my PogoPlug v2 (pink) for almost a year now with no issues. However, after a recent update i can no longer boot into the arch linux on my USB harddrive. I can reboot back into the PogoOS fine without the HDD attached. I've Google'd the hell out of this and nothing i try seems to work.

I've tried updating the uBoot to the latest version as i saw there were some issues with the latest Kernel but that hasn't helped either. Really not sure what else to do now but a reinstall which will be a right pain.

Here is the uBoot log:
$this->bbcode_second_pass_code('', '
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 728
UBI: number of bad PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2952192 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.2.1-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2952128 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

')

EDIT: Also when plugging the HDD into my main PC, i can't boot to it. Does this mean something is up with that rather than my pogo? Maybe i need to do a fsck...

Any thoughts, comments or advise is appreciated.

[WarheadsSE]

The 3.2 kernel is the issue, at this point if that is an E02, we're currently maintaining a 3.1.10-9-ARCH not the 3.2.x because of that aforementioned u-boot issue. If you cannot access the drive (you said boot) from your other ext2/3 speaking computer, then there may be further issues.

It is possible to install the package from another pacman-speaking computer with certain flags in the pacman call, causing it to update the alternate system.

$this->bbcode_second_pass_quote('WarheadsSE', 'T')he 3.2 kernel is the issue, at this point if that is an E02, we're currently maintaining a 3.1.10-9-ARCH not the 3.2.x because of that aforementioned u-boot issue.

[WarheadsSE]

Yeah, you can't chroot into the ALARM install on an x86. If you run an Arch livecd, you can force the update in by downloading the tarball from the repo. ..

$this->bbcode_second_pass_code('', '
pacman -U ${tarball} --cachedir ${mount_dir}/var/cache/pacman/pkg -r ${mount_dir}
')

[dixonl90]

$this->bbcode_second_pass_quote('WarheadsSE', 'Y')eah, you can't chroot into the ALARM install on an x86. If you run an Arch livecd, you can force the update in by downloading the tarball from the repo. ..

$this->bbcode_second_pass_code('', '
pacman -U ${tarball} --cachedir ${mount_dir}/var/cache/pacman/pkg -r ${mount_dir}
')

[WarheadsSE]

Arch live cd, upstream x86/etal

Then mount the ALARM install's drive, and proceed after downloading http://us.mirror.archlinuxarm.org/arm/c ... pkg.tar.xz

[kmihelich]

On a side note, this was not a recent update. The 3.2 kernel lasted in the repositories for approximately one week at the end of January before the issue was fully discovered and subsequently downgraded. Nearly a full three months ago is not recent.

For future reference, please be honest, don't try to play us.

$this->bbcode_second_pass_quote('WarheadsSE', 'A')rch live cd, upstream x86/etal

Then mount the ALARM install's drive, and proceed after downloading http://us.mirror.archlinuxarm.org/arm/c ... pkg.tar.xz

[kmihelich]

People regularly try to pass off old problems as new ones.