Did you format the disk by its own IDE controller prior to the SuSE installation?
IDE is run by the microprocessor and thus a pulled hard disk can lose data when going i/o.
Don't you still have the original SCSI drive with the data? Either get a SCSI controller install it to the new machine or get a replacement new IDE drive and redo the data transfer.
And someone should do a true backup.
Adam
-----Original Message-----
From: Matthew Stringer
Subj: [SLE] DMA killed IDE disk
Date: Sat Aug 20, 2005 11:41 am
Size: 1K
To: suse-linux-e@suse.com
I've got an old Compaq ML370 server with SCSI disks and RAID 5.
The operating system (red hat 7.2) had died so I was asked to rebuild the
machine with Suse 9.3
So I copied using rsync the entire SCSI drive over to a 120GB IDE disk.
Flattened the machine and installed Suse.
Everything went well, mounted the IDE disk and wanted to restore the data.
However the IDE disk was performing really slow as DMA mode wasn't enabled. I
had 70GB worth of websites to restore ASAP as customer was offline, I didn't
want it to take forever.
Opened YaST and enabled DMA.
However when the server rebooted it complained that the IDE disk couldn't be
mounted, concluded it must be due to the DMA mode so switched it back off and
rebooted it again.
Still couldn't mount it.
Ran FSCK but it couldn't see a filesystem, ran fsck.reiserfs which told me to
use the --rebuild-tables switch.
Done this but the contents of the disk have been destroyed in the process.
I'm in the shit now as the customer has lost 300000 pictures that weren't
backed up (their fault for no backup).
However, although I've learned not use do this again in the future, it would
be nice to know why this simple function was able to destroy the contents
like that!
Matthew
--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
