question about SATA vs (SATA via USB)

question about SATA vs (SATA via USB)

[Harri]

Hi folks,

I have seen a file system corruption when I conected a
previously written SATA disk to my PC using a SATA-via-USB
connector. Probably this wasn't supposed to happen, was it?

I had bought a new 500 GB SATA disk to be built into my
PC. To copy the boot partition I attached it to the PC
using a cheap SATA-via-USB connector. Probably you have
seen these devices on Ebay before. Its a strange socket
to be plugged into the back side of the disk, providing
both IDE and SATA. It also includes an external power
supply.

Creating a partition table and copying the boot disk went
fine. After that I replaced the internal disk with the new
one, fixed the mbr and tried to boot. It worked.

Next I mounted (rw, shame on me) the old SATA disk via USB
to the PC, and tried to copy the data. But during the copy
there were some syslog messages about file system corruptions
on the old disk. I stopped rsync, unmounted the disk,
and ran fsck, but it was damaged beyond repair. No chance
to recover any data.


The question is what has happened here? I checked the old
disk on a real SATA connector; it seems to be OK.


???


Regards

Harri

Re: question about SATA vs (SATA via USB)

[Tejun Heo]

Harri wrote:
> Next I mounted (rw, shame on me) the old SATA disk via USB
> to the PC, and tried to copy the data. But during the copy
> there were some syslog messages about file system corruptions
> on the old disk. I stopped rsync, unmounted the disk,
> and ran fsck, but it was damaged beyond repair. No chance
> to recover any data.

Hmmm... interesting.  That isn't supposed to happen.  Do you have kernel
logs saved?

-- 
tejun

Re: question about SATA vs (SATA via USB)

[Harald Dunkel]

Hi Tejun,

Tejun Heo wrote:
> Harri wrote:
>> Next I mounted (rw, shame on me) the old SATA disk via USB
>> to the PC, and tried to copy the data. But during the copy
>> there were some syslog messages about file system corruptions
>> on the old disk. I stopped rsync, unmounted the disk,
>> and ran fsck, but it was damaged beyond repair. No chance
>> to recover any data.
> 
> Hmmm... interesting.  That isn't supposed to happen.  Do you have kernel
> logs saved?
> 

Sorry, but the logs have been lost. The new 500 GB disk had
an I/O error and had to be replaced. I doubt that this I/O
error was the reason for corrupting the filesystem on the
other disk, but there is no way to be sure, afaics.

I would suggest to ignore this problem for now.


Regards

Harri