[H-GEN] VFS: Can't find ext3 filesystem on dev ide1(22,1)

Jason Parker-Burlingham jasonp at panix.com
Sun Aug 7 01:44:10 EDT 2005


On Sun, Aug 07, 2005 at 09:16:37AM +1000, Geoff Shang wrote:
> Jason Parker-Burlingham wrote:
> >Do you get this error from all your partitions?  Sounds like the magic
> >is hosed---there's a string of bytes at the start of the filesystem that
> >identify it as such and not as something else.
> On the two Linux partitions, yes.  The middle one is swap, so I don't have 
> any way to verify that (that I know of anyway).

Under normal circumstances there's no point trying to rescue swap or
even preserve it across reboots, but it can be handy as a location to,
say, install a rescue system you can boot.

> >I wonder if a good first step might not be making sure you have a valid
> >partition table, because if that's not right then your mount command
> >won't read the right blocks, well get confused and bail in exactly the
> >manner you describe.
> 
> That's what I thought, but the table I posted at least looks to be the 
> right one.  The ratios all seem correct.  Is there any way I can check for 
> sure?  At least the entry for the first one should be right, as it starts 
> at the beginning of the disk.

I'm not sure how you might go about verifying the partition table.  I
think there are programs out there which will scan a disk for partitions
and work out what the partition table must have looked like.  There
might also be an option to fdisk to give you more information.

> >You seem to have a rescue system; what does file -s say is in the
> >special device you're trying to mount?
> 
> data:/home/geoff# file -s /dev/hdc1
> /dev/hdc1: symbolic link to ide/host0/bus1/target0/lun0/part1
> data:/home/geoff# file -s /dev/ide/host0/bus1/target0/lun0/part1
> /dev/ide/host0/bus1/target0/lun0/part1: data
> 
> This would seem to confirm your theory.

It would.  I really hope you have not run fsck on this.  I still think
that the filesystem signature is corrupt, which probably does not bode
well for the data, or that the filesystem is very corrupt and just needs
a check run on an alternative superblock---Rob's advice on this is
correct.

I wonder if dd'ing the partition to /dev/null will highlight any disk
errors and help you rule in or out disk corruption?

Cheers,
-- 
Jason Parker-Burlingham
<jasonp at panix.com>
(Watch this space)




More information about the General mailing list