[Top] [All Lists]

RE: Power loss causes bad magic number??

To: "Dave Chinner" <david@xxxxxxxxxxxxx>
Subject: RE: Power loss causes bad magic number??
From: "Stephen Porter" <stephenp@xxxxxxxxxx>
Date: Wed, 16 Jul 2008 18:17:37 +1000
Cc: <xfs@xxxxxxxxxxx>, <sandeen@xxxxxxxxxxx>
References: <F46A887185FC6044A7FAC577E31118AE022316C0@xxxxxxxxxxxxxxxxxxx> <487D5F80.1050909@xxxxxxxxxxx> <F46A887185FC6044A7FAC577E31118AE021E0623@xxxxxxxxxxxxxxxxxxx> <20080716073503.GE29319@disturbed>
Sender: xfs-bounce@xxxxxxxxxxx
Thread-index: AcjnFn45xIyZpPgfSQGKyoVirjQ2BwAAi30X
Thread-topic: Power loss causes bad magic number??

-----Original Message-----
From: Dave Chinner [mailto:david@xxxxxxxxxxxxx]

> That looks like a boot loader.

That's what I thought, but again, this isn't a boot volume, could running 
xfs_repair without the -n have done this?

> And at 0x200 I'd expect to see an AGF header, not zeros. To
> me, that says that either XFS is inside a partition on the drive
> or someone ran a partitioning tool on /dev/sdc and overwrote the
> XFS filesystem headers...

relevant line from /etc/fstab:

/dev/sdc        /home/username/Data     xfs     defaults        0       2

the raid management tool is reporting everythings ok... any idea what could 
have caused this?  


Ok, my apologies, I've just done an ls of /dev/sd* and the devices have been 
remapped (any idea what would have caused that?), sdc is no longer sdc, it is 
now sda, the boot devices are now detected as sdb and sdc (2 mirrored physical 
disks, used to be sda and sdb).  How was the machine able to boot?  I'm more 
confused than ever now, but the data is all there.

Sorry for wasting everyones time.



[[HTML alternate version deleted]]

<Prev in Thread] Current Thread [Next in Thread>