Comment 6 for bug 222322
Revision history for this message
| Don Malcolm (lpad6) wrote Re: IDE addressing screwed in Hardy | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
No Darko, it is not to do with uuid in the fstab.
For the record, the fstab does use UUID to identify the disks.
Please read more carefully. You will see that I have stated, that fdisk -l does not report all my disks. Furhermore you will see that I have included output from lshw. If you would kindly take the time to examine the output of lshw from Dapper and Hardy installs, you will see that a disk is missing from the Hardy install that is present in the Dapper install. Note that this output was taken from my current hardware configuration. As I have stated above, Dapper is installed in the second partition on the master of the primary controller. Hardy is installed on the first partition on the master of the primary controller.
Furthermore please note that when attempting to install Hardy in a disk on the seconday IDE controller, the install fails because it fails in the kernel to identify all my drives. I suspect the reason for the file not found message I stated above, was that it installed on the disk on the secondary controller, but then on reboot, the disk was no longer visible.
It does not appear to me to be a configuration issue, but rather a kernel issue. Why? As I stated above, the problem also exists in Fedora Core 8, also by booting Hardy but with the Gutsy kernel, all disks are identified properly. Simply changing the kernel and only the kernel to an earlier kernel, the system is fully operational with all disks correctly identified in fdisk -l.
Point taken regarding use of sda in place of hda. I was not aware of this change. It would seem there are bugs in this change over.
Configurations that failed for me in Hardy:
1) Two drives, with one as master on the primary controller, and one as master on the secondary controller. Only one drive shows up in fdisk -l
2) Three drives, with two on the primary controller and the other as master on the secondary. Only two drives show up.
3) Three drives, with two on the secondary controller and the other as master on the primary. Only two drives show up.
At the moment, I am running Hardy with two drives on the primary controller, with both drives accessible, and the third as master on the secondary controller, and is not visible in fdisk -l.