On Mon, 31 Oct 2005, Dominik Kubla wrote: > On Monday 31 October 2005 11:42, maximilian attems wrote: > > On Sat, 29 Oct 2005, Dominik Kubla wrote: > > > The created initramfs drops into a shell because /dev/md0 can not be > > > mounted. This is a regression from version 0.30. <snipp> > Additional infos: > > $ cat /etc/fstab > # > # /etc/fstab: static file system information. > # > # <file system> <mount point> <type> <options> <dump> <pass> > proc /proc proc defaults 0 0 > /dev/md0 / ext3 defaults,errors=remount-ro 0 1 > /dev/md1 none swap sw 0 0 > /dev/md2 /home ext3 defaults 0 2 > /dev/hdc4 /scratch ext3 defaults 0 2 > /dev/hdb /media/cdrom0 udf,iso9660 ro,user,noauto 0 0 > /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0 > tmpfs /tmp tmpfs mode=1777,size=2G 0 0
hmm i had suspected a more "esoteric" setup. tested it myself with latest initramfs-tools on raid root. > $ df -k > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/md0 15377744 3755052 10841540 26% / > /dev/md2 19283236 14418876 4864360 75% /home > /dev/hdc4 39376392 1769000 35607168 5% /scratch > tmpfs 2097152 72 2097080 1% /tmp > tmpfs 648296 0 648296 0% /dev/shm > tmpfs 10240 144 10096 2% /dev > > If you need any more info, please let me know ... yes can you put the initramfs archive somewhere online where i can take a look at it. how did you generate it? does regenerating the initramfs image help: update-initramfs -u -t -k 2.6.14-1-686 assuming you use the linux-image-2.6-686 from unstable? thanks for your feedback, as 0.30 worked for you i assume a missing module due to the lvm and md split out. hope we can nail that down soon. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
