my box has been acting strangely recently. When it was been on for long periods (like 24hrs) it seems to crash and has loads of problems with the file systems.

on more than one occasion it takes 2-3 reboots before the file systems mount properly.
Also dmesg outputs these results that has got me a bit paranoid.

hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }

Is my hard disk about to fail. Should i rush out and buy a fresh one before it implodes.

DM

hi there,

what happens if you disable dma??
if the error persist, i would advice to start the burial preparations.

regards

slackie1000

Rush out to back up all your data... And find the receipt...

ok the general concensus is that its f##d right, my hard disk has my hole disertation sitting on it.

I'm backing it up as i'm typing. Its just a shame that i will have to do a re-install, again. i'm getting pretty good at that now.

is there any way i could mirror the disk, i have heard bits about ghosting but i'm not really sure what its about.

cheers for your advice guys/

Yes, you can mirror it. If you get a harddrive that is exactly the same size you can put both in a the same time and do it w/ linux.

Assuming your original drive is /dev/hda and your new drive is /dev/hdb:

dd if=/dev/hda of=/dev/hdb

Wait for it to finish and you'll have an exact copy. If the new drive is bigger you'll have some empty space on the end that you'll have to deal with.

The big problem you may now have is some corruption because of previous failures. That has happened to me before. You may just be better off reinstalling to the new drive. Of course you can try the mirroring and if it works out good then fine.

Hey...


Sice two weeks ago, I gwt the same error messages, but JUST AT Windows partitios, nad by the way, I can't boot wein anymore.

This is the error I see at dmesg :

Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdb: DMA disabled
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device ide0(3,3)) ...
for (ide0(3,3))
ide0(3,3):Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.



I use Slack 10.0, and boot with lilo, first option linux (kernel 2.4) and then I have a new 2.6 kernel and the windows. The windos at hda1 just doesn't boot.

But the linux is ok, so I wander if this is not a hardware faillure advice, but some kind of winproblem?

hi there,
did you realize that you hijacked a thread 2 months old to ask about a windows problem?
bad...
regards
slackie1000

Have you run any kind of confidence test on the harddrive? It is possible there is simply a corrupted partition but it doesn't really look that way. You can probably find a confidence test that you boot from floppy from the website of the harddrive manufacturer. If the test from the manuafacturer fails then you need a new drive.

I'd hurry. If it is failing you may not have much time rescue your data.

hey again,

slackie1000, you said:
" ...did you realize that you hijacked a thread 2 months old to ask about a windows problem?
bad.. "

Sorry, but I don't think so. I booted from my 2.6 kernel ( I almost never use it ) and those mesages just desapered. So there is 'something' slck/linux related here.

Yes, I do have a dual-boot machine, but a lot of people too. I use my win almost one a year, to calculate my taxes (here in Brazil, where I am, we pay it by internet and the program is windows)

My win doesn't work anymore; I can browse the win partitions from linux, I already did my backup, and to make it working again is simple: I just get the win cd and repair the c drive, where the system is, I can even reformat it, since I have my data in another partion.

And I am NOT asking how to solve THAT. I would like to UNDERSTAND those error messages. I was digging this forum and the net about it< and I didn't found ANY asnwwe where I could see : That is the problaim, by sure. I saw a lot of people saing that 'probabily' is a hardware faut, but my machine just doesn't seams to be having that kind of problem.

And as I said now, if I boot with the 2.6 there are no error messages.

I think that there is an error, but that 'possibly' the error is at the error message itself... :-)

I can repair or reformat that partition now, I could have it already done, but then 'probably' the problem WILL DESAPEAR and I will never understand it. From like a decade to now I always have like 2 or 3 partitions at my win, and at my clients too... because one of the most certain things to happen in this world is that you will lose all your windows install...



benjithegreat98,
thanks... I am considering that.... and yes, I did a big backup, and I will buy another hd and transfer all my linux to that new one.

May be it's a 2.4.x bug... which was solved in 2.6.x.
If not,
Remember what you was doing before this error came up. That would be a better thing to find a "bug" if it exists, than live with a spoiled partition.
I don't know... watch your log files...