[ILUG] Second Drive Partition Mounting

[Declan Moriarty]

Recently, Somebody Somewhere wrote these words
> On 23/03/06, Declan Moriarty <junk_mail at iol.ie> wrote:
> 
> > I would ask has the kernel got ide built-in? Presuming not, let's
> > make sure it knows what to do by running depmod (humour me) and
> done that, not sure what to look for
> 
> > putting a line in modprobe.conf.
> ubuntu doesnt appear to use this, directly at least. I'll check
> further and see what i can find that may mimic this

Probably a short path. Every system needs depmod.

Try /sbin/depmod, or install module init tools

> 
> >
> > I would like to see a 2 on the pass - I know it shouldn't matter,
> > but who knows?
> ok, added that, interesting results.
> 
> i get this message :
> 
> ====
> ...
> * Checking all filesystems
> fsck.ext3: No such file or dir while trying to oped /dev/hda2
> /dev/hda2:
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains and ext2
> filesystem(and not swap or ufs or something else), then the superblock
> is corrupt, and you might want to try running e2fsck with an alternate
> superblock :
>        e2fsck -b 8193 device
> 
> * fsck failed, please repair manually.
> ====

Now we're getting somewhere! It takes real intelligence to wreck someone's
pc from a distance  :-)).
> 
> Then I can enter the root pw to 'repair', or hit control-D to continue the boot.
> 
> If I do the latter, it mounts the drive !!!!!!!!!!!
> 
> Now, am I reading this right, I assume that the second part of the
> message is due to the first part, "No such file or dir while trying to
> oped /dev/hda2", and there's nothing wrong with the disk.
> 
> e2fsck shows no problem with the disk after the boot.
> 
> Q : how does one find the where the alternate superblocks are ?

man e2fsck under the -b option reccomends mke2fsck -n

> 
> Would anybody like to offer a reason/guess why it won't mount
> normally, but will after failing the pass2 ?
>
> 
GUESS: It failed to load a module, (No such file or directory) 
then failed to read the disk because of that. Ignore that message.
Modules can be loaded from several places. You may run this down
to a typo.

get into your logs. I bet there'll be a hint there now.

-- 

	With best Regards,


	Declan Moriarty.