[Cooker] YAIR (28/03/2001 - first attempt!)
System is: Athlon 800 MHz, Mainboard Asus A7V/133 Mem: 256 MB, Dual Hard-Disk for software-raid (!) Installation: via network.img from a local-mirror INSTALLATIONS 1. When giving data for "non-anonymous" ftp login, passwd IS shown! 2. Still cannot DISABLE THAT SUPERMOUNT PLE 3. Tried to install / on raid1, still KERNEL PANIC: That's what I read from []: [] Loading module /lib/raid1.o raid1 personality registered EXT2-fs: Unable to read superblock Kernel Panic: VFS: Unable to mount root fs on 09:00 End of mmy first installation :( -- Nothing's as simple as it seems... [root@monster root]# echo "hello world" [root@monster root]# Segmentation fault (core dumped) [root@monster root]# Kernel Panic! - System is halted... power down
Re: [Cooker] YAIR (28/03/2001 - first attempt!)
Claudio (sekko) [EMAIL PROTECTED] writes: System is: Athlon 800 MHz, Mainboard Asus A7V/133 Mem: 256 MB, Dual Hard-Disk for software-raid (!) Installation: via network.img from a local-mirror INSTALLATIONS 1. When giving data for "non-anonymous" ftp login, passwd IS shown! Yes. I thought it was not worth the effort to make special case code just for hiding the password. You'll be doing the install only one time; and anyway the password will be here as an environment variable during all installation :-). [...] 3. Tried to install / on raid1, still KERNEL PANIC: Yes, raid-on-/ with 2.4 is currently not supported. You can use 2.2 for that if you really need it. I don't know yet if we'll have raid-on-/ with 2.4 with LM-8.0. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] YAIR (28/03/2001 - first attempt!)
On Wednesday 28 March 2001 12:36, you wrote: 1. When giving data for "non-anonymous" ftp login, passwd IS shown! Yes. I thought it was not worth the effort to make special case code just for hiding the password. You'll be doing the install only one time; and anyway the password will be here as an environment variable during all installation :-). OK, that's fine. Good explanation ;o) Tried to install / on raid1, still KERNEL PANIC: Yes, raid-on-/ with 2.4 is currently not supported. You can use 2.2 for that if you really need it. I don't know yet if we'll have raid-on-/ with 2.4 with LM-8.0. That's TERRIBLE :( 2.4 should have a great improvement for raid support, it perfectly boots from raid, so... I do not understand that choice. Anyway, if I am the only one who's using raid among Mandrakians... I'll be patient and build my raid by hand SIG :((( Claudio -- Nothing's as simple as it seems... [root@monster root]# echo "hello world" [root@monster root]# Segmentation fault (core dumped) [root@monster root]# Kernel Panic! - System is halted... power down
Re: [Cooker] YAIR (28/03/2001 - first attempt!)
Claudio (sekko) [EMAIL PROTECTED] writes: [...] Yes, raid-on-/ with 2.4 is currently not supported. You can use 2.2 for that if you really need it. I don't know yet if we'll have raid-on-/ with 2.4 with LM-8.0. That's TERRIBLE :( 2.4 should have a great improvement for raid support, it perfectly boots from raid, so... I do not understand that choice. Anyway, if I am the only one who's using raid among Mandrakians... I'll be patient and build my raid by hand SIG :((( It's not raid, it's raid-on-/. It's not a "choice". Actually to mount the /, the kernel has to have a valid device. "Building" a Raid device involves assigning one or more RAID hd partitions to it. With 2.2, we have a patch that enables kernel autodetection of RAID hd partitions and assignments. It's not in 2.4. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] YAIR (28/03/2001 - first attempt!)
On Wednesday 28 March 2001 14:51, you wrote: Claudio (sekko) [EMAIL PROTECTED] writes: [...] Yes, raid-on-/ with 2.4 is currently not supported. You can use 2.2 for that if you really need it. I don't know yet if we'll have raid-on-/ with 2.4 with LM-8.0. That's TERRIBLE :( 2.4 should have a great improvement for raid support, it perfectly boots from raid, so... I do not understand that choice. Anyway, if I am the only one who's using raid among Mandrakians... I'll be patient and build my raid by hand SIG :((( It's not raid, it's raid-on-/. It's not a "choice". Actually to mount the /, the kernel has to have a valid device. "Building" a Raid device involves assigning one or more RAID hd partitions to it. And why is it working for me? ... # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=y CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y CONFIG_MD_RAID5=y CONFIG_BLK_DEV_LVM=m ... md0 IS / partitions are marked 0xfd (linux raid autodetect) My custom kernel build from kernel-source-2.4.2-20mdk is working! With 2.2, we have a patch that enables kernel autodetection of RAID hd partitions and assignments. It's not in 2.4.
Re: [Cooker] YAIR (28/03/2001 - first attempt!)
And why is it working for me? No idea :-). [...] CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=y CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y CONFIG_MD_RAID5=y CONFIG_BLK_DEV_LVM=m ... md0 IS / partitions are marked 0xfd (linux raid autodetect) My custom kernel build from kernel-source-2.4.2-20mdk is working! Exactly what I mean... My home computer booted perfecly with a "recompiled" 2.4.0-5mdksmp and that options signed "y"... I guess it's just a kernel-configuration's pb! ;| Maybe it can be the fact that it's in modules or plain inside kernel... Can you try that: boot your kernel with our rescue, and then, try to manually mount /dev/md0 (copying or mknoding md0) somewhere, to confirm? -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Claudio (sekko) sorcla@tiscalinet.it] Re: [Cooker] YAIR (28/03/2001 - first attempt!)
And why is it working for me? No idea :-). [...] CONFIG_MD=y CONFIG_BLK_DEV_MD=y CONFIG_MD_LINEAR=y CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y CONFIG_MD_RAID5=y CONFIG_BLK_DEV_LVM=m ... md0 IS / partitions are marked 0xfd (linux raid autodetect) My custom kernel build from kernel-source-2.4.2-20mdk is working! Exactly what I mean... My home computer booted perfecly with a "recompiled" 2.4.0-5mdksmp and that options signed "y"... I guess it's just a kernel-configuration's pb! ;| Maybe it can be the fact that it's in modules or plain inside kernel... Can you try that: boot your kernel with our rescue, and then, try to manually mount /dev/md0 (copying or mknoding md0) somewhere, to confirm? -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
