| View previous topic :: View next topic |
| Author |
Message |
amarodeeps
n00b
Joined: 28 May 2002
Posts: 50
|
 Posted: Fri Mar 26, 2004 9:25 pm Post subject: hard drive/emerge issue? |
 |
|
Hi folks,
I'm getting some strange problems that maybe someone has seen before. Basically, I'm getting this dumped to my system log:
| Code: |
Mar 26 14:24:13 monger hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: DMA disabled
Mar 26 14:24:13 monger ide0: reset: success
Mar 26 14:24:13 monger hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger hda: read_intr: status=0x51 { DriveReady SeekComplete Error }
Mar 26 14:24:13 monger hda: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=78142491, sector=75909456
Mar 26 14:24:13 monger ide0: reset: success
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@\
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@\
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@\
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@<snip>
|
THEN, my system goes funky--the file system suddenly switches to read-only. Although fstab and mount list it as being read-write (i.e., it is definitely mounted read-write, and mount seems to think it remains so).
So, then I have to reboot, run fsck manually, clean it up, and I can use the system again.
WHY it does this, I have no idea, but it only seems to happen when I run emerge, and it only seems to happen when I run emerge on specific builds. For instance, when I tried to run it on OpenOffice the other night, I came in the next morning with a read-only fs, same as the 3 times today I tried to emerge gimp2. Other things build fine though; I also installed gpdf today, for example.
At this point, I'm guessing I'm having some issue with some specific chunk of my hard drive that emerge uses for a certain 'region' of ebuilds, and I need to replace the drive (it is on a refurbished dell gx270 that I just installed gentoo on Tuesday/Wednesday). But I'm looking for a second/third/fourth etc. opinion. I'd love to NOT reinstall gentoo if I don't have to, and I'm nervous that it is my install screwing up too--I'd like to just run dd and copy this drive to another drive but I don't know enough to say if this wouldn't just screw up a second disk.
Any help is much appreciated!
Thanks,
Dave |
|
| Back to top |
|
 |
gwlinden
n00b
Joined: 06 Jan 2003
Posts: 70
Location: Utrecht, The Netherlands
|
| Posted: Fri Mar 26, 2004 9:36 pm Post subject: |
|
|
I would guess you have a hardware error. Power-supply voltage, drive temperature, cable/connector problems, or drive error may possible causes...
The driver may switch to read-only mode when it detects too many errors, so that is expected behaviour in this case.
_________________
Gwendolyn |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
