Sorry, but your disk would appear to be in very bad shape after this,
those bad magic number values actually appear to be copies of the xfs
super block. There appears to have been some random splattering of
data onto the disk.
Do you have any syslog messages from before the system went down?
Also, what type of partition was this? Were you using md/lvm, what
was the hardware involved. Also, which compiler did you use?
Steve
p.s. 2.4.10 is supposedly not the best kernel to be running, 2.4.13
is out on the ftp site, and 2.4.14 should arrive there today.
On Mon, 2001-11-05 at 15:50, Stefan Frank wrote:
> Hi,
>
> a few days ago i retired my old P166 Mhz machine and moved to a new
> 2x866 PIII box. In the beginning i used the same kernel (UP !) as before
> (2.4.10 + XFS patch (i BELIEVE the 10/03 dated one, but i also have the
> 09/25). Later on while i was working on my 2nd machine reading news,
> suddenly GNUS got stuck. When i went back to the new SMP machine
> i realised that XFS had unmounted the /var partition. On the console
> was a message like "kernel: access beyound end of device" and the
> notification of XFS that it closed down the /var partition.
> Note that there was no indication of a Kernel oops.
>
> When i rebooted, this partition could'nt be mounted. The error message
> is: XFS: mounting filesystem sd(8,6)
> XFS: failed to read root inode
>
> Running xfs_check yields in :
>
> bad magic # 0x58465342 in btbno block 0/0
> bad magic # 0x58465342 in btcnt block 0/0
> bad magic # 0x58465342 in inobt block 0/0
> block 3/69 expected type unknown got free2
>
> Also xfs_repair is not able to fix the problem.
> See it's log below :
>
> Phase 1 - find and verify superblock...
> sb root inode value 18446744073709551615 inconsistent with calculated value
> 13835049534067048576
> resetting superblock root inode pointer to 18446744069414584448
> sb realtime bitmap inode 18446744073709551615 inconsistent with calculated
> value 13835049534067048577
> resetting superblock realtime bitmap ino pointer to 18446744069414584449
> sb realtime summary inode 18446744073709551615 inconsistent with calculated
> value 13835049534067048578
> resetting superblock realtime summary ino pointer to 18446744069414584450
> Phase 2 - using internal log
> - zero log...
> - scan filesystem freespace and inode maps...
> bad agbno 0 for btbno root, agno 0
> bad agbno 0 for btbcnt root, agno 0
> bad agbno 0 for inobt root, agno 0
> root inode chunk not found
> Phase 3 - for each AG...
> - scan and clear agi unlinked lists...
> - process known inodes and perform inode discovery...
> - agno = 0
> imap claims in-use inode 131 is free, correcting imap
> imap claims in-use inode 132 is free, correcting imap
> imap claims in-use inode 133 is free, correcting imap
> imap claims in-use inode 134 is free, correcting imap
> imap claims in-use inode 135 is free, correcting imap
> imap claims in-use inode 136 is free, correcting imap
> imap claims in-use inode 137 is free, correcting imap
> imap claims in-use inode 138 is free, correcting imap
> imap claims in-use inode 139 is free, correcting imap
> imap claims in-use inode 140 is free, correcting imap
> imap claims in-use inode 141 is free, correcting imap
> imap claims in-use inode 142 is free, correcting imap
> imap claims in-use inode 143 is free, correcting imap
> imap claims in-use inode 144 is free, correcting imap
> imap claims in-use inode 145 is free, correcting imap
> imap claims in-use inode 146 is free, correcting imap
> imap claims in-use inode 147 is free, correcting imap
> imap claims in-use inode 148 is free, correcting imap
> imap claims in-use inode 149 is free, correcting imap
> imap claims in-use inode 150 is free, correcting imap
> imap claims in-use inode 151 is free, correcting imap
> imap claims in-use inode 152 is free, correcting imap
> imap claims in-use inode 153 is free, correcting imap
> imap claims in-use inode 154 is free, correcting imap
> imap claims in-use inode 155 is free, correcting imap
> imap claims in-use inode 156 is free, correcting imap
> imap claims in-use inode 157 is free, correcting imap
> imap claims in-use inode 158 is free, correcting imap
> imap claims in-use inode 159 is free, correcting imap
> imap claims in-use inode 160 is free, correcting imap
> imap claims in-use inode 161 is free, correcting imap
> imap claims in-use inode 162 is free, correcting imap
> imap claims in-use inode 163 is free, correcting imap
> imap claims in-use inode 164 is free, correcting imap
> imap claims in-use inode 165 is free, correcting imap
> imap claims in-use inode 166 is free, correcting imap
> imap claims in-use inode 167 is free, correcting imap
> imap claims in-use inode 168 is free, correcting imap
> imap claims in-use inode 169 is free, correcting imap
> imap claims in-use inode 170 is free, correcting imap
> imap claims in-use inode 171 is free, correcting imap
> imap claims in-use inode 172 is free, correcting imap
> imap claims in-use inode 173 is free, correcting imap
> imap claims in-use inode 174 is free, correcting imap
> imap claims in-use inode 175 is free, correcting imap
> imap claims in-use inode 176 is free, correcting imap
> imap claims in-use inode 177 is free, correcting imap
> imap claims in-use inode 178 is free, correcting imap
> imap claims in-use inode 179 is free, correcting imap
> imap claims in-use inode 180 is free, correcting imap
> imap claims in-use inode 181 is free, correcting imap
> imap claims in-use inode 182 is free, correcting imap
> imap claims in-use inode 183 is free, correcting imap
> imap claims in-use inode 184 is free, correcting imap
> imap claims in-use inode 185 is free, correcting imap
> imap claims in-use inode 186 is free, correcting imap
> imap claims in-use inode 187 is free, correcting imap
> imap claims in-use inode 188 is free, correcting imap
> imap claims in-use inode 189 is free, correcting imap
> imap claims in-use inode 190 is free, correcting imap
> imap claims in-use inode 191 is free, correcting imap
> - agno = 1
> - agno = 2
> - agno = 3
> data fork in ino 12583049 claims free block 786501
> - agno = 4
> - agno = 5
> - agno = 6
> - agno = 7
> - process newly discovered inodes...
> imap claims in-use inode 26209 is free, correcting imap
> imap claims in-use inode 26210 is free, correcting imap
> imap claims in-use inode 26211 is free, correcting imap
> imap claims in-use inode 26212 is free, correcting imap
> imap claims in-use inode 26213 is free, correcting imap
> imap claims in-use inode 26214 is free, correcting imap
>
> [ Snipped a _LOT_ of similar lines referring to different inodes ]
>
> imap claims in-use inode 656542 is free, correcting imap
> imap claims in-use inode 656543 is free, correcting imap
> avl_insert: Warning! duplicate range [0xa1d20,0xa1d60)
>
> fatal error -- xfs_repair: duplicate inode range
>
>
>
> Any idea what could have caused this? I don't think it's a hardware
> problem as all other partitions (mixed ext2 and XFS) are still working
> fine and this problem appeared _exactly_ after i switched to a SMP
> system.
>
> For now i switched to another HDD and FS (ext2/ext3).
> Is there still hope to get my data back? (No i don't have a backup,
> but already learned my lesson ;-( )
>
> If you need more info's just let me know!
>
> Bye, Stefan
>
> --
> The things that interest people most are usually none of their business.
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|