iskandarprins at gmail.com
Mon Jul 14 19:17:00 UTC 2008
Problem solved. It seemed one of my sata cables was loose, I reconnected it
and and I got all my data back :-) I'm happy now.
The tip about the raid made me relook into the raid array again
Thanks for the help
On Mon, Jul 14, 2008 at 9:03 PM, Iskandar Prins <iskandarprins at gmail.com>
> Yup, there is a Raid1 underlying. I'm using a *XFX REVO 64 SPU 3 Port SATA
> Raid Card **for my raid1 setup. Don't I lose my entire data when I break
> the raid?
> Yup, even with the fsck -f option, the drive is clean.
> The windows was connecting via samba (hence windows).
> On Sun, Jul 13, 2008 at 7:56 PM, Matija Nalis <mnalis-ml at voyager.hr>
>> On Sun, Jul 13, 2008 at 01:01:27AM +0200, Iskandar Prins wrote:
>> > At the moment I'm looking at the filesystem (onto which I made those
>> > last week) , but it seems I'm looking at the filesystem from a month ago
>> > june 20th).
>> is underlying block device a single hard disk, or maybe a RAID1 or similar
>> I had a similar problem once, which turned out to be RAID1 which was out
>> sync (but wrongly thining it is OK!), so sometimes it read "right" data
>> one disk, and some times "bad" data from other disk. Solution was to break
>> the RAID, force fsck it, and recreate the raid afterwards.
>> > I did a fsck/e2fsck on the umounted devs and they can't get any cleaner.
>> you did specify -f to force it, I assume ?
>> Opinions above are GNU-copylefted.
>> Ext3-users mailing list
>> Ext3-users at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ext3-users