Re: SS4000E Fan speed, LEDS and power button

["JF Straeten" <jfstraeten@scarlet.be>]

Re,

On Thu, Jul 19, 2012 at 03:49:51PM -0400, Chris Wilkinson wrote:

> So one way of proceeding would be to
> 
> delete all the existing partitions on the 4 HDs, leaving them all as free
> space. I see you have 3 partitions on each HD, so you created these 3
> partitions before creating the RAID sets. 

Yes.


> I think I need to add only 1 making 2 partitions on each HD, swap
> and the remaining free space

Yes. It's just a (good or bad) habit to create the / apart...


> create a new RAID1 adding the swap spaces from each HD. About 2x the
> RAM size seems to be the suggested size.

It's an old (and osbolete) advice, but... yes :-)


> So this is what I end up with (from the d-i terminal screen)
> 
> RAID1 device #0 - 510.6 MB Software RAID device
> #1           510.6 MB    f  swap        swap
>              53.8 kB        unusable
> RAID5 device #1 - 1.5 TB Software RAID device
> #1           1.5 TB      f  ext3        /
>              512.0 B        unusable
> SCSI1 (0,0,0) (sda) - 500.1 GB ATA WDC WD5000AAKS-0
> >     #5  logical  499.6 GB    K  raid
> >     #1  primary  510.7 MB    K  raid
> SCSI2 (0,0,0) (sdb) - 500.1 GB ATA WDC WD5000AAKS-0
> >     #5  logical  499.6 GB    K  raid
> >     #1  primary  510.7 MB    K  raid
> SCSI3 (0,0,0) (sdc) - 500.1 GB ATA WDC WD5000AAKS-0   
> >     #5  logical  499.6 GB    K  raid
> >     #1  primary  510.7 MB    K  raid
> SCSI4 (0,0,0) (sdd) - 500.1 GB ATA WDC WD5000AAKS-2
> >     #5  logical  499.6 GB    K  raid
> >     #1  primary  510.7 MB    K  raid


It seems good to me (you have no need for logical partitions, but it
won't hurt either).

 
> After saving/committing this setup, d-i next creates ext3 FS on the RAID5
>       "Creating ext3 file system for / in partition #1 of RAID5 device
> #1..."
> 
> Install proceeds without error, writes flash, requests reboot.

Good.


[...]

> [    1.740000] Freeing init memory: 112K
> Loading, please wait...
> /scripts/init-top/udev: line 17: udevd: not found

You have already a probleme with udev here. Should try to (re)install
it.


> Begin: Loading essential drivers ... /init: line 205: modprobe: not found
> /init: line 205: modprobe: not found
> /init: line 205: modprobe: not found

Huu ? modprobe not found ? It's strange, since modprobe is a vital
command with a modular kernel...

Try also to (re)install it.



> done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
> done.
> error sending message: Connection refused
> udevadm[45]: error sending message: Connection refused
> 
> Begin: Waiting for root file system ... done.
> Gave up waiting for root device.  Common problems:
>  - Boot args (cat /proc/cmdline)
>    - Check rootdelay= (did the system wait long enough?)
>    - Check root= (did the system wait for the right device?)
>  - Missing modules (cat /proc/modules; ls /dev)
> /init: line 5: modprobe: not found
> /init: line 5: modprobe: not found
> ALERT!  /dev/disk/by-uuid/65707e43-d5a8-4c1a-ac5a-937d8078a606 does not
> exist.  Dropping
>  to a shell!
 
> 
> BusyBox v1.17.1 (Debian 1:1.17.1-8) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> /bin/sh: can't access tty; job control turned off
> (initramfs)
> 
> Problems are (see log)
> No root device found
> initramfs is junk
> 
> Hangs at this point :(

Hangs ? Not really hanged, I suppose ?

You should be able to play with busybox, right ?


Could you restart d-i and try to purge and reinstall the kernel ?

You are using debian stock kernel, right ?

It will re-generate the initrd, which I suspect lacks some essential
modules...

If you have flashed an old initrd without raid support, for example,
or without ext3 support in it, it's not surprising that the kernel
can't find the root device without support to deal with it...

By redoing it, you should finish with an inirtd specially crafted with
the modules you need to boot.


(NB: It exists also the mkinitramfs command to redo just the initrd.
Feel free to try it, but you will need to take a shell in the context
of d-i, which is perhaps a bit involved for now.)


Hih,

-- 

JFS.