Linux Mint Forums
[Solved]LM 14 and Windows 7 dual boot -Disk read error
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
[Solved]LM 14 and Windows 7 dual boot -Disk read error
Post by YanOri » Tue Dec 18, 2012 10:10 pm
Hi, I’m trying for a dual boot here with linux mint 14 and windows 7. I’ve made separate partition of about 15GB for LM and about 6 GB of swap, everything works fine on the linux part, except for the grub menu. When i select windows 7, I get this error ‘A Disk Read Error Occurred. Press CTRL+ALT+DEL to restart’ and on restarting and choosing windows 7 again, I get the same error.
Well, I can fix this by using my windows 7 DVD, Go to repair -> Command prompt ->
bootrec /fix boot bootrec /fixmbr But then when I do that, I loose the grub menu ad the computer directly boots into windows.
This does not happen on any version of LM other than 14 (I tried LM 14 KDE, LM 14 64 bit and LM 14 32 bit, also tried ubuntu 12.10 — Same problem). While LM13 and ubuntu 12.04 worksgreat along with windows.
I like the simplicity of linux, but there are some apps and work I have to do on windows, that keeps me away from eliminating it. Any help would be greatly appreciated.
EDIT: Currently I’m on Linux mint 14 KDE (fresh install, 25GB system and 6.7 GB swap — I just allotted the unused space as swap). Right now I can’t boot into windows, thought grub shows windows 7 on boot menu, I get the same ‘disk read error’
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Linux Mint Forums
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
Can’t launch Linux Mint, «Read Error»
Post by sashkello » Wed Jan 20, 2016 1:32 am
Sorry for unloading this personal problem in here, but I’m getting a bit desperate with this.
I’ve got an Acer Aspire S3 laptop and have just replaced the hard drive (upgrading it from 250 to 500 Gb, it was failing and old as well).
After this, I, as usual, made a bootable USB with Linux Mint (17.3 this time), and proceeded to install it with no troubles whatsoever. However, after installation went through, and I rebooted, it didn’t even start booting any OS, all I see is a black screen with «Read Error». Sometimes (seems random), it shows
Now, a few things which I have checked:
1. I tried to reinstall Linux Mint several times, trying to make manual partitions, to no noticeable effect.
2. I can see the new hard drive in BIOS.
3. When I boot from USB, I can see my partitions in GParted as well as the standard linux file structure. So, it looks like Mint IS there on the drive.
4. I have tried Boot Repair, both Recommended Repair and a few other options in Advanced, to no success.
5. I have tried reinstalling GRUB2 as described here, again, without any result.
UPDATE:
6. Tried to go through grub-rescue as described here, but get the same error («attempt to read or write outside of disk») on insmod command.
7. Tried to install some other distros, Linux Lite didn’t do anything new, but with Fedora I managed to get to the boot menu (somehow it works 50/50), and a couple of times it even went through to load OS itself, although most times it shows me «failure reading sector . from hd0», if it gets to boot menu at all («Read Error» is what I usually see).
8. Run
sudo badblocks -wsvf /dev/sdaWhat could be going on, how do I diagnose my problem further?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 5 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
«Read Error» on boot
So my computer froze while it was in powersave mode, and I could not reboot it with REISUB, or access it over the network, forcing me to hard reboot. When I rebooted, I was greeted with the message «Read Error» in the top left corner. I booted into a LiveCD, and tried
root@ubuntu:/home/ubuntu# fdisk -l fdisk: unable to read /dev/sda: Inappropriate ioctl for device I immediately imaged the drive with gddrescue, and then proceeded to run e2fsck. That seemed to complete successfully, and now when I run fsck, I get:
fsck from util-linux 2.20.1e2fsck 1.42.8 (20-Jun-2013) /dev/sda1: clean, 1475560/18317312 files, 48594157/73242187 blocks So all seems good over there. However, I still cannot get any output from fdisk, and when I reboot, I still get the same error.
It showed an ext4 partition at sda1 and an extended partition at sda1 which when expanded, opens up to show a swap partition at ext5
Yes, I was able to mount /dev/sda1. The end of the day, I just reformatted and reinstalled Ubuntu, and now all is fine. Just wish somebody would tell me why fdisk -l didn’t work.
3 Answers 3
I faced the same issue, What resolved the issue for me was using the live CD i installed Boot Repair,that repaired my file system which was mounted on partition sd1. After rebooting the initial boot took a bit more time than usual but the machine worked fine after that.
Well, It’s my first time installing Ubuntu and had the same «Read error» and I solved it in an almost silly way.
I had disassembled my sister’s netbook to make a back up of the hard drive before installing Ubuntu. Her netbook was running so slow on Windows that so I had to disassamble to have access to the drive. Then I installed Ubuntu (the Lubuntu distribution) easily but when I reebooted I had this read error. So I simply suspected that when I re-assambled the netbook, I did not plug well the hard drive (excuse my poor english, I mean I didn’t connect it correctly).
MY SOLUTION
So I simply disassambled the netbook again and connected strongly the hard drive. When I rebooted, the Lubuntu worked normally.