PDA

View Full Version : [SOLVED] error: hd0,1 read error. Help please!



jackflamer
July 31st, 2010, 05:21 AM
Hi all,

I would be appreciated if someone can help me solve this, as I have no idea about where to start.

I have recently purchased a new MoBo (MSI 785GTM-E45) along with Athlon II x2 450 and 2G RAM. After trying to install ubuntu10.04, I stuck at the point of system booting. Every time when I boot, the screen shows : " error: hd0,1 read error" then shows me a "grub resume" prompt. I have tried to install ubuntu through USB stick which is created through another working ubuntu installation. Doesn't matter which partitioning method I chose ( automatically entire disk or manually partitioning with both ext3 and ext4) it fails at boot and return something like above or simply "read error".

To provide more information, I have the following information printed :

fdisk -l



Disk /dev/sda: 10.0 GB, 10005037056 bytes
255 heads, 63 sectors/track, 1216 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e1d15

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1193 9581568 83 Linux
/dev/sda2 1194 1217 186369 5 Extended
/dev/sda5 1194 1217 186368 82 Linux swap / Solaris

bootinfoscript



Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for /boot/grub.

sda1: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04 LTS
Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

sda2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 10.0 GB, 10005037056 bytes
255 heads, 63 sectors/track, 1216 cylinders, total 19541088 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start End Size Id System

/dev/sda1 * 2,048 19,165,183 19,163,136 83 Linux
/dev/sda2 19,167,230 19,539,967 372,738 5 Extended
/dev/sda5 19,167,232 19,539,967 372,736 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 c736ac6e-ae15-4962-8a48-54c1b00fcd61 ext3
/dev/sda2: PTTYPE="dos"
/dev/sda5 446b1cf4-9c1a-4e32-8a85-350ff4c54a0e swap
/dev/sda: PTTYPE="dos"

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sdb1 /cdrom vfat (ro,noatime,fmask=0022,dmask=0022,codepage=cp437,i ocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 /rofs squashfs (ro,noatime)


=========================== sda1/boot/grub/grub.cfg: ===========================

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}

function recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
}
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set c736ac6e-ae15-4962-8a48-54c1b00fcd61
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set c736ac6e-ae15-4962-8a48-54c1b00fcd61
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set c736ac6e-ae15-4962-8a48-54c1b00fcd61
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=c736ac6e-ae15-4962-8a48-54c1b00fcd61 ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
}
menuentry 'Ubuntu, with Linux 2.6.32-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set c736ac6e-ae15-4962-8a48-54c1b00fcd61
echo 'Loading Linux 2.6.32-21-generic ...'
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=c736ac6e-ae15-4962-8a48-54c1b00fcd61 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-21-generic
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set c736ac6e-ae15-4962-8a48-54c1b00fcd61
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,1)'
search --no-floppy --fs-uuid --set c736ac6e-ae15-4962-8a48-54c1b00fcd61
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
if [ ${timeout} != -1 ]; then
if keystatus; then
if keystatus --shift; then
set timeout=-1
else
set timeout=0
fi
else
if sleep --interruptible 3 ; then
set timeout=0
fi
fi
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

=============================== sda1/etc/fstab: ===============================

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=c736ac6e-ae15-4962-8a48-54c1b00fcd61 / ext3 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=446b1cf4-9c1a-4e32-8a85-350ff4c54a0e none swap sw 0 0

=================== sda1: Location of files loaded by Grub: ===================


1.0GB: boot/grub/core.img
1.1GB: boot/grub/grub.cfg
1.1GB: boot/initrd.img-2.6.32-21-generic
1.1GB: boot/vmlinuz-2.6.32-21-generic
1.1GB: initrd.img
1.1GB: vmlinuz
As you may see too, I have found that the partition /dev/sda1 started at '2048' instead of '1'. I think this is where the problem is, however, I just don't know how to fix it. When I use 'Gparted', I see there is a 1mb unallocated space sits in the beginning of the disk, if this is the case, why not "1024"? Is this a indicator that the "1~1024 " is marked as bad sector, so that the ubuntu automatically added a padding 1024 right after it? Is this mean my 10GB hard disk is bad? BTW, I have tried to move the partition to the beginning of the disk, but has no luck to fix my problem.

Any comment is welcome, thanks!

oldfred
July 31st, 2010, 05:39 AM
With fdisk -lu it shows the detail. Linux & XP always started at 63 and then Vista changed to 2048. Now with Lucid the installer also uses 2048. I think it may have to do with SSDs but am not sure. It is correct as it is.

I would look at BIOS settings and see if some drive setting may be causing an issue. Is there a IDE compatiblity setting, ACHI disabled? Or some other setting since your drive is 10GB. Is that an SSD or an old drive?

jackflamer
July 31st, 2010, 06:15 AM
Hi oldfred,

Yes, this is a very old 3.5 inch desktop hard disk connected with an IDE 40 pin cable. If I am looking into the mobo bios setting, what particular section should I pay attention to? The mobo manual doesn't mention too much about this compatibility stuff though.

Thanks for helping, again! You are the treasure of this community!

jackflamer
July 31st, 2010, 06:23 AM
Hi oldfred,

Your input really helped me! I replaced the old 40 pin IDE cable, and it boots now with no problem! Unbelievable effective community!

Thanks again with best regards!

Jack

oldfred
July 31st, 2010, 04:14 PM
I am not sure I really helped than much but am glad you got it working.

The old 40 wire cables are pretty well obsolete, as they were replaced with the 80 wire that could use cable select. As soon as I saw the advantages of SATA I made sure as I upgraded to buy SATA even though originally they were a few dollars more.

One of the big advantages was the elimination of oldfred screwing up system. Every time I opened case I moved some parallel cable around an the connector would disconnect just enough to look connected, sometime even power up but not work fully. Reopen case push connectors back in an then it worked. Originally some of the the same issue with SATA but found locking connect cables and I now am not as afraid to open case.