Harry Mangalam wrote:
> On Monday 23 February 2009, Eric Sandeen wrote:
>>> |<IPStorPartition|
>>> | version="3.0" s|
>>> |ize="595" owner=|
>>> |"NACS-SW-DIST" c|
>>> |hecksum="" signa|
>>> |ture="IpStOrDyNa|
>>> |MiCdIsK" dataSta|
>>> |rtAtSectorNo="16|
>> .... knowing the offsets of these might be helpful. But perhaps
>> you are simply not trying to mount the thing which actually has xfs
>> on it.
>>
>> I don't know what IPStore is. Perhaps your volume is encrypted?
>> Dunno... at any rate, doesn't seem at first glance like it's an xfs
>> problem, I'm afraid.
>>
>>> |firstSector="222|
>>> |72" lastSector="|
>>> |2928740095" owne|
>> I might look at sector 22272 (about 10MB in) and see if that looks
>> like xfs :)
>
> Good guess! :
> At 00AE0000 (11.4MB in) there's "XFSB" altho I can't make out much of
> the surrounding bytes...
>
> Is there a way to do anything with this info? Can it be dd'ed out to
> use to get the thing mounted?
try mount -o loop,offset=11403264 /dev/whatever /mnt/whatever
I'd probably also add ro,norecovery to the options as well so you don't
actually write anything to it at this point.
-Eric
>> Or maybe just put it back in the NAS box, now, assembled the same
>> way.
>
> This is just about my last gasp - I'll rec that they try this if
> nothing else comes to mind..
>> -Eric
>
>
>
|