I have installed Ubuntu at the second SSD drive in my laptop, but when the Grub shows up and I choose Ubuntu - the following error appears: "error: failure reading sector 0x728b6c0 from hd1. You need to load the Kernel first." The sector is different each time I try to boot in. Windows 8 boots in normally. Do you have any ideas how to fix this? Grub repair doesn't help...
I suggest that you do three things...
- Use the
Disks app to check the SMART Data & Tests
Edit your question with a screenshot of the SMART Data and I'll take a look
run the SMART Tests
fsck your Ubuntu partition
- boot to a Ubuntu Live DVD/USB
- open a
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
sudo fsck -f /dev/sdb3# replacing XXXX with the number you found earlier
- repeat the fsck command if there were errors
- Perform a bad block scan
Boot to a Ubuntu Live DVD/USB, backup any data from /dev/sdb3, and in the
Note: do NOT abort a bad block scan! Note: do NOT bad block a SSD Note: backup your important files FIRST!
sudo e2fsck -fcky /dev/sdb3 # read-only test
sudo e2fsck -fccky /dev/sdb3 # non-destructive read/write test (recommended)
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fccky parameter...
-f Force checking even if the file system seems clean. -c This option causes e2fsck to use badblocks(8) program to do a read-only scan of the device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or direc‐ tory. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test. -k When combined with the -c option, any existing bad blocks in the bad blocks list are preserved, and any new bad blocks found by running badblocks(8) will be added to the existing bad blocks list. -y Assume an answer of `yes' to all questions; allows e2fsck to be used non-interactively. This option may not be specified at the same time as the -n or -p options.
After checking the BIOS version with
sudo dmidecode -s bios-version it was determined that there was a newer BIOS available. Installed the newer version and so far it seems to have fixed the problem.