You are not logged in.
Pages: 1
This is an issue which is apparently spanning across multiple linux distributions. I am not sure if this is a linux kernel issue, or if my hard drive is dieing. Here is the story.
I went to install Ubuntu 8.04 a few days ago, but the Live CD wasn't detecting any hard drives. So, I decided I would see what Fedora 8 was going to do. I opened GParted on the Fedora 8 Live CD and I was presented with the hard drive, but an error was being displayed:
The device /dev/sda1 doesn't exist.
Failed to check '/dev/sda1' mount state: No such file or directory
Probably /etc/mtab is missing. It's too risky to continue.So, I saw that the hard drive was being detected, I just couldn't "make use of it". So I was curious to see if I could mount the thing and look at the Windows files on it. I was. I was able to mount it through the terminal to /media/Windows, and I was able to browse all the files on the hard drive. When I did that and opened GParted again, obviously it showed the hard drive as being locked since it was mounted, but it actually showed how much data was being used graphically this time around. That light brown color was shading in how much data had been used. So I unmounted it, but again, the same problem persists.
I then decided to try the GParted 0.3.6-7 Live CD. During the whole hardware detection phase, I was presented with this:
ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl SATA mode
ahci 0000.00:1f.2: flags: 64 bit ncq pm led slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 cmd 0xf8830d00 ctl 0x00000000 bmdma 0x00000000 irq 22
ata2: SATA max UDMA/133 cmd 0xf8830d80 ctl 0x00000000 bmdma 0x00000000 irq 22
ata3: SATA max UDMA/133 cmd 0xf8830e00 ctl 0x00000000 bmdma 0x00000000 irq 22
ata4: SATA max UDMA/133 cmd 0xf8830e80 ctl 0x00000000 bmdma 0x00000000 irq 22
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0x27)
ata1.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (781422768)
ata1.00: ATA-7: HDS724040KLSA80, KFA0A20N, max UDMA/133
ata1.00: 781422768 sectors, multi 8: LBA48
ata1.00: failed to set xfermode (err_mask=0x40)
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0x80)
ata1: COMRESET failed (errno=-16)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0x27)
ata1.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (781422768)
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/133:P103
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0x80)
ata1: COMRESET failed (errno=-16)
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: qc timeout (cmd 0x27)
ata1.00: ata_hpa_resize 1: hpa sectors (0) is smaller than sectors (781422768)
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: disabled
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)Once I actually get into the graphical interface in GParted, it doesn't show any hard drives. I am presented with nothing.
A few days ago I had also downloaded ArchLinux, because after installing Ubuntu installing Arch was going to be my next order of business. Unfortunately, Arch is also getting hung up on this problem. I receive the same messages I posted above during the hardware detection phase. I was hoping someone could offer any sort of insight.
Note: I have also booted GParted in Failsafe mode, which entails a lot of different parameters to try to get the boot to run smoothly. (noacpi acpi=off, etc)
Does anyone have any ideas? I used to run Ubuntu and Fedora on this same hard drive just a few months ago, but I knocked them all out for Windows because of school. This hard drive used to work fine with linux, and now it isn't. Is the hard drive dieing? Windows runs absolutely fine, in fact I ran a chkdsk earlier today and not a single bad kB was found on the disk.
I'd appreciate any help,
Thanks.
Offline
Update:
The testing version of GParted 0.3.7-2, is able to find my hard drive without any errors.
Does this settle it that it's a kernel issue? Even if the testing version of GParted can find my hard drive, it seems as though all the linux distros still won't be able to find it. How can I go about getting Arch, or any other distro installed on it?
Offline
Pages: 1