Hi again, I've just successfully moved my root filesystem to a new drive, and now I'm trying to boot to the drive when it is hooked up using esata.
Everything works great when the new boot drive is installed in an internal bay, but if I put it in an esata enclosure, and hook it up to an esata port the box will not boot. I'm using UUID's in /etc/fstab, so changing drive positions should not matter, or does the flash-kernel stuff translate it back in to device names? I wondered if the esata kernel module wasn't installed in the initramfs, but ahci seems to be in there. Any hints? -- Mark Small -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201202141341.12792.msm...@eastlink.ca