Le dimanche 01 septembre 2013 à 00:05 +0200, Paul Kocialkowski a écrit : > 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 > exist > Aug 31 21:54:57 in-target: > Aug 31 21:54:57 in-target: Press Ctrl-C to abort build, or Enter to > continue > > I get this from ssh: > /dev/disk/by-uuid # ls > 34c362d5-e3ae-43f2-ad77-4571c33f3694 > 40c127f5-f54c-4e85-9248-97ec447efc8 > > 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!
Sidenote: I am currently installing Wheezy on my SheevaPlug (with ext2) and the exact same issue occurs! -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
