I notice you have partitions /dev/sdc[1-7] listed in Feisty, but no partitions on /dev/sd[abd]. If you could dmesg | grep for lines matching 'scsi' OR 'mesh' (sorry, don't know the correct grep syntax for this) -- or maybe just do 'dmesg | grep -A1 -B1 scsi' -- that could give clearer context of what's happening at boot.
I bet if you'd used the netboot initrd for Feisty, the partitioner would offer you /dev/sdc (but nothing else) for partitioning and installation. Apparently it's counting the external SCSI as Bus 0, so the Zip drive got /dev/sda, then the internal IBM drive ID:0 got /dev/sdb, which means your internal Quantum drive (heh, sounds like something from Star Trek!) at ID:1 would be the accessible one at /dev/sdc? If you installed, I reckon the assignments of sd[a-d] would change in the installed system. Any chance that Quantum disk is an adapter-converted Wide device like my Seagate? -- Disks on internal SCSI bus offlined during Feisty boot, no I/O thereafter https://bugs.launchpad.net/bugs/118319 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
