Windows

[Hodgins Family]

Good evening!

> I can qualify that a bit better on the NTFS part. I had a corrupted NTFS 
> filesystem (Approx 300GB of data on a 500GB disk that was getting errors) 
> and using Ubuntu (Hoary) I managed to copy off all the data that was even 
> remotely possible to read, without much trouble (terminal/shell and using 
> cp no less).
>
> Under Windows, I couldn't even access parts of the filesystem at all. Note 
> that Windows wasn't actually on the disk in question, it was just storage 
> space. It would fail, and depending on what Windows felt like, the disk 
> would (listed in order of occurance) either:
> 1. Lock, causing the system to lock and requiring a reboot.
> 2. Be automatically unmounted.
> 3. Skip the problem areas, pretending the remainder of any particular 
> directory from that point on didn't exist. This means that if the 
> corrupted file was the first file in the directory, we couldn't get 
> anything out of the remainder of the directory. This is really annoying 
> when there are corrupted files in the top level of the filesystem.
>
> BTW: Yes, the kernel complained bitterly about all the file problems, but 
> it copied the files, and we recovered enough to make it worthwhile.

This is very good information. Thank you.

> PS: Yes there should've been a backup. The idiot responsible now knows 
> better.
                                                                       ^^^
This is most definitely NOT helpful. We have no idea what his backup 
schedule looks like...maybe the problem happened in between incremental 
backups. I don't know. Neither do you.

Rob