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:
pgp00025.pgp
Description: PGP signature
