Re: Unable to mount root & Problems with Woody

Re: Unable to mount root & Problems with Woody

[Lewis Shobbrook]

I've have noted something that some of you may find interest in.  I have
tried fruitlessly to get raid1 working in with Debian woody on a 2.4.18
kernel using raidtools2.  I tried countless different means to copy the
root filesystem onto the raid filesystem.  The best I managed to achieve
was about half a file system. All attempts to mount lilo using lilo -r
/mnt/md0 device resulted in failure because nodes in the dev directory
would never copy onto the mdX filesystem. Out of frustration I updated
to the debian testing distro recreated both /dev/md0 and it's
filesystem,  and all works like a charm.  The raidtools versions are
both 0.90.200109 for woody and Testing, so the source of the woody woes
must lay a little deeper, perhaps the raidtools dependencies weren't as
compatible with woody or mke2fs is somehow different. Anyway hope this
info helps someone.

RE; Unable to mount -- Appologies ! I think the mounting trouble with
...

EXT2-fs: md(9.0): couldn't mount because of unsupported optional
features (fff80000).
cramfs: wrong magic
Md: swapper(pid 1) used obsolete MD ioctl, upgrade your software to use
new ictls. 
Kernel Panic. 

... was likely fstab pointing to /dev/hda1 with lilo.ocnf root=/dev/md0.

Cheers,

Lewis

Re: Unable to mount root & Problems with Woody

[Jan-Benedict Glaw]

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

On Fri, 2003-02-21 21:15:23 +1100, Lewis Shobbrook <lshobbrook@fasttrack.net.au>
wrote in message <84BB6E1F4E011742AFB186D469FDEA9A015BDD@fastterminal.fasttrack.net.au>:

> /mnt/md0 device resulted in failure because nodes in the dev directory
> would never copy onto the mdX filesystem. Out of frustration I updated

Then you did the copy wrong. Use tar for it, one source partition at a
time. Like this:

(let /usr be on it's own partition)

	cd /usr
	tar cpf - --numeric-owner --one-file-system | \
		(cd /mnt/new/usr && tar xpf - --numeric-owner; ) 

> filesystem,  and all works like a charm.  The raidtools versions are
> both 0.90.200109 for woody and Testing, so the source of the woody woes
> must lay a little deeper, perhaps the raidtools dependencies weren't as
> compatible with woody or mke2fs is somehow different. Anyway hope this
> info helps someone.

With a bit of luck, newer fileutils managed to get the device nodes
right whilst you've not given appropriate parameters to 'cp'?!

> RE; Unable to mount -- Appologies ! I think the mounting trouble with
> ...
> 
> EXT2-fs: md(9.0): couldn't mount because of unsupported optional
> features (fff80000).

Seems you try to mount an unclean ext3 filesystem with ext2 drivers...

> cramfs: wrong magic
> Md: swapper(pid 1) used obsolete MD ioctl, upgrade your software to use
> new ictls. 
> Kernel Panic. 
> 
> ... was likely fstab pointing to /dev/hda1 with lilo.ocnf root=/dev/md0.

That seems to be an ext2 <-> ext3 problem...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur
    fuer einen Freien Staat voll Freier Bürger" | im Internet!
   Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Unable to mount root & Problems with Woody

[Gordon Henderson]

On Fri, 21 Feb 2003, Lewis Shobbrook wrote:

> I've have noted something that some of you may find interest in.  I have
> tried fruitlessly to get raid1 working in with Debian woody on a 2.4.18
> kernel using raidtools2.  I tried countless different means to copy the
> root filesystem onto the raid filesystem.  The best I managed to achieve
> was about half a file system. All attempts to mount lilo using lilo -r
> /mnt/md0 device resulted in failure because nodes in the dev directory
> would never copy onto the mdX filesystem.

I've built several boxes to boot off raid1 using Debian woody. Eg:

drogon @ agate: df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md0              235M   18M  205M   8% /
/dev/md1              1.9G  905M  920M  50% /usr
/dev/md2               35G   12G   21G  34% /var
drogon @ agate: uname -a
Linux agate 2.4.20 #1 Wed Jan 29 12:07:57 GMT 2003 i686 unknown
drogon @ agate: cat /etc/issue
Debian GNU/\s 3.0 \n \l


Theres a good howto on it all at

  http://www.tldp.org/HOWTO/Software-RAID-HOWTO-4.html#ss4.11

The trick to doing the copy is to use cpio (or something else that
preserves device nodes rather than try to crete files out of them)

Gordon

Re: Unable to mount root & Problems with Woody

[Ross Vandegrift]

On Fri, Feb 21, 2003 at 10:24:25AM +0000, Gordon Henderson wrote:
> I've built several boxes to boot off raid1 using Debian woody. Eg:

Same here, using custom compiled kernels.  Have you ever managed to get
a system up and booting off of raid1 with a Debian-supplied kernel?  I'm
not one for that whole initrd thing, so I'm kinda lost.

-- 
Ross Vandegrift
ross@willow.seitz.com

A Pope has a Water Cannon.                               It is a Water Cannon.
He fires Holy-Water from it.                        It is a Holy-Water Cannon.
He Blesses it.                                 It is a Holy Holy-Water Cannon.
He Blesses the Hell out of it.          It is a Wholly Holy Holy-Water Cannon.
He has it pierced.                It is a Holey Wholly Holy Holy-Water Cannon.
He makes it official.       It is a Canon Holey Wholly Holy Holy-Water Cannon.
Batman and Robin arrive.                                       He shoots them.

Re: Unable to mount root & Problems with Woody

[Gordon Henderson]

On Fri, 21 Feb 2003, Ross Vandegrift wrote:

> On Fri, Feb 21, 2003 at 10:24:25AM +0000, Gordon Henderson wrote:
> > I've built several boxes to boot off raid1 using Debian woody. Eg:
>
> Same here, using custom compiled kernels.  Have you ever managed to get
> a system up and booting off of raid1 with a Debian-supplied kernel?  I'm
> not one for that whole initrd thing, so I'm kinda lost.

No, but I've never tried. I always build a custom kernel with everything
for that particular hardware configuration statically compiled in as soon
as I can and run without modules. (except laptops and the pcmcia stuff,
but they are hardly going to be running raid, anyway!)

I use the Debian install process to get a bare-minimal system installed,
(99% of the time I'm building a server rather than a workstation, so I
don't want X, etc.) with a packaged kernel (which makes sure I get the
right stuff to build a kernel), but then get a stock kernel off kernel.org
and use that rather than the packaged one... If nothing else, a kernel
compilation is a good, if crude test of the system, memory, disk, etc. and
is useful if it's a new system you've just built from scratch...

Gordon