[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Installing Wheezy on DreamPlug: Unable to make the system bootable

Le samedi 31 août 2013 à 22:36 +0200, Paul Kocialkowski a écrit :
> From the working installation's installer syslog, I can tell that
> generating a new initramfs and the u-boot images comes right next after
> the u-boot-tools's installation.
> Now my guess is that the problem is in flash-kernel's
> flash_kernel_set_root, which is the one dealing with the rootfs.
> In a case, it is possible that flash_kernel_set_root waits for stdin and
> hence would make the whole thing hang (read _ignored) in the installer
> context. It is called as a hook when generating the initramfs.
> It seems like a long shot since this case is not supposed to be reached,
> but I also noticed that the images I generated on the working
> installation wouldn't boot without the root=/dev/sda2 cmdline argument
> from the bootloader (and I don't mean the ones I generated using my
> computer and uploaded to the Dreamplug to make it boot the first time).
> However I didn't get the error message that's supposed to come before
> (read _ignored). So I might very well be wrong, but there is no doubt
> the issue happens when running something from flash-kernel, and
> flash_kernel_set_root is definitely related to the rootfs.

Well, it turns out my guess was the right one! I enabled ssh on the
installation and monitored syslog as the installation went and I found
the following message:

Aug 31 21:54:52 in-target: update-initramfs:
Generating /boot/initrd.img-3.2.0-4-kirkwood
Aug 31 21:54:57 in-target: UUID 55794117-e5d0-47e5-b371-9ed10ee4ad2c
doesn't exist in /dev/disk/by-uuid
Aug 31 21:54:57 in-target: Warning: root
device /dev/disk/by-uuid/55794117-e5d0-47e5-b371-9ed10ee4ad2c does not
Aug 31 21:54:57 in-target: 
Aug 31 21:54:57 in-target: Press Ctrl-C to abort build, or Enter to

I get this from ssh:
/dev/disk/by-uuid # ls

This situation should not happen, it should instead properly display an
error message to the user, or silently die, but not this.

Running "udevadm trigger" brings the expected UUID, so I think there is
a problem somewhere in the partitioner tool since it doesn't
refresh /dev/disk/by-uuid after making an ext2 partition (but it
probably does it for ext3).

So finally, I was able to complete my installation with ext2!

Reply to: