n_sectors mismatch error during boot
There is occasional mention of this problem in various forums, but I have tried various remedies and seen no improvement.
Motherboard: biostar_geforce6100m9
sata driver: sata_nv
drives: have seen this when booting off either a WD Red 2.0TB HD or a Samsung 830 SSD. Had previously had a Samsung HD160JJ/P installed with NO such problems - strange!
On bootup the output is often of at least one of the following errors:
(1) after the "Verifying DMI Pool Data" line receive the error message "unrecognized file system", then drops to grub rescue
(2) receive an error message such as: "ata3.00: n_sectors mismatch 500118192 != 2251799813685248" followed later by "ata3.00: revalidation failed (errno=-5 or -19)
ata3.00: disabled"
(3) very occasionally see a "model number mismatch" error
Things I have tried to rectify this situation, without success:
(a) install Ubuntu 12.04 LTS (had been using 10.04 LTS) on a separate partition. Errors occur regardless of which Ubuntu version I try to boot into.
(b) 3 different SATA cables
(c) plugging into SATA port 2 instead of SATA port 1
(d) add the following to /etc/default/grub (Ubuntu 10.04 and 12.04):
GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=30 splash"
GRUB_CMDLINE_LINUX="sata_nv.swncq=0 libata.force=noncq,1.5G"
- I have tried different rootdelay durations (irrelevant I think, based on when the errors occur) and GRUB_CMDLINE_LINUX command combinations
Once the system is booted, it seems to run quite well. So it seems to be more of a booting issue and specifically related to grub not receiving accurate info from the SATA device during the booting process. This is why I tried different SATA cables & ports, but to no avail.
The error that requires most reboots during the booting process is the "n_sectors mismatch" error.
hdparm -i /dev/sda output: LBAsects=500118192
500118192 is always seen within the error message (e.g. n_sectors mismatch 2251799813685248 != 500118192), and consistently the output of hdparm -i is LBAsects=500118192, so is there a way of "forcing" this #LBA sectors during the boot process ?
hdparm -I /dev/sda shows that 2251799813685248 is actually the # of LBA48 user addressable sectors, so it's not a completely gibberish number
Last edited by byline; January 29th, 2013 at 01:18 AM.
Sue
"Life is what happens to you while you're busy making other plans." John Lennon
Bookmarks