Mailinglist Archive: opensuse-project (95 mails)
| < Previous | Next > |
[opensuse-project] openSUSE 10.3 beta 1: problem with libata and hard drive geometry
- From: "Michel Salim" <michel.sylvan@xxxxxxxxx>
- Date: Sat, 18 Aug 2007 13:13:11 -0400
- Message-id: <f224c6140708181013y265ca45eg45b305f52a404216@xxxxxxxxxxxxxx>
I tried running the openSUSE 10.3b1 installer (using the GNOME x86
CD), and ran across a problem with detected disk geometry on a
Thinkpad T41p, with no other OS installed.
I have had problems in the past with openSUSE 10.2: fdisk detects a
C/H/S geometry of 9729/255/63, while the kernel itself would detect a
much higher C value, with H=16. On my first install things worked fine
for a while, until the system locked up during use a few days
afterwards (running the latest kernel), which is probably due to the
kernel accessing the disk (and writing to it) using the wrong
geometry.
On 10.2 I can just pass 'hda=9729,255,63' to force the kernel to use
the same geometry used to partition the disk.
On 10.3, I tried passing 'sda=9729,255,63' but to no avail; YaST would
warn that parted could not access the disk and thus I could not touch
the partition table, and dropping to a console and checking with fdisk
shows that only 9300-something cylinders are detected.
Has something changed in the kernel between 2.6.18 and 2.6.22 that
causes even fdisk/parted to see a different geometry? How can I
override this at boot time?
Out of curiosity, I've seen claims that keeping a Windows partition on
disk would force parted etc. to use the disk geometry that Windows
sees, so a consistent geometry is always used. Any truth to that?
Many thanks,
--
Michel
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
CD), and ran across a problem with detected disk geometry on a
Thinkpad T41p, with no other OS installed.
I have had problems in the past with openSUSE 10.2: fdisk detects a
C/H/S geometry of 9729/255/63, while the kernel itself would detect a
much higher C value, with H=16. On my first install things worked fine
for a while, until the system locked up during use a few days
afterwards (running the latest kernel), which is probably due to the
kernel accessing the disk (and writing to it) using the wrong
geometry.
On 10.2 I can just pass 'hda=9729,255,63' to force the kernel to use
the same geometry used to partition the disk.
On 10.3, I tried passing 'sda=9729,255,63' but to no avail; YaST would
warn that parted could not access the disk and thus I could not touch
the partition table, and dropping to a console and checking with fdisk
shows that only 9300-something cylinders are detected.
Has something changed in the kernel between 2.6.18 and 2.6.22 that
causes even fdisk/parted to see a different geometry? How can I
override this at boot time?
Out of curiosity, I've seen claims that keeping a Windows partition on
disk would force parted etc. to use the disk geometry that Windows
sees, so a consistent geometry is always used. Any truth to that?
Many thanks,
--
Michel
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |