RE: SS4000E Fan speed, LEDS and power button

["Chris Wilkinson" <kinsham@verizon.net>]

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. I think I need to add only 1
making 2 partitions on each HD, swap and the remaining free space

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

create a new RAID5 adding the remaining free spaces from each HD

use the RAID5 as an ext3 FS, mounted at /, bootable no

Use the RAID1 as a swap

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

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.

So far so good.



The system is going down NOW!ystem...
x
Sent SIGKILL to all processes
x
Requesting system
rebootqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
                        [12830.530000] Restarting system.
+No network interfaces found

EM-438/EM-7220 ver.AG0 2006-05-23
== Executing boot script in 1.000 seconds - enter ^C to abort
RedBoot> fis load ramdisk.gz
RedBoot> fis load zImage
RedBoot> exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000"
-r 0x01800000 -w 5
About to start execution at 0xa0008000 - abort with ^C within 5 seconds
Using base address 0x01008000 and length 0x00132fa8
Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.32-5-iop32x (Debian 2.6.32-45)
(dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Sun May 6
07:47:32 UTC 2012
[    0.000000] CPU: XScale-80219 [69052e30] revision 0 (ARMv5TE),
cr=0000397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Lanner EM7210
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total
pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 rw root=/dev/ram
mem=256M@0xa0000000
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072
bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 251776KB available (3084K code, 444K data, 112K init,
0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:32
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
[    0.220000] Security Framework initialized
[    0.220000] SELinux:  Disabled at boot.
[    0.220000] Mount-cache hash table entries: 512
[    0.220000] Initializing cgroup subsys ns
[    0.220000] Initializing cgroup subsys cpuacct
[    0.220000] Initializing cgroup subsys devices
[    0.220000] Initializing cgroup subsys freezer
[    0.220000] Initializing cgroup subsys net_cls
[    0.220000] CPU: Testing write buffer coherency: ok
[    0.220000] devtmpfs: initialized
[    0.220000] regulator: core version 0.5
[    0.220000] NET: Registered protocol family 16
[    0.220000] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    0.220000] pci 0000:00:01.0: PME# disabled
[    0.220000] pci 0000:00:05.0: PME# supported from D0 D1 D2 D3hot
[    0.220000] pci 0000:00:05.0: PME# disabled
[    0.220000] pci 0000:00:05.1: PME# supported from D0 D1 D2 D3hot
[    0.220000] pci 0000:00:05.1: PME# disabled
[    0.220000] pci 0000:00:05.2: PME# supported from D0 D1 D2 D3hot
[    0.220000] pci 0000:00:05.2: PME# disabled
[    0.220000] PCI: bus0: Fast back to back transfers disabled
[    0.230000] bio: create slab <bio-0> at 0
[    0.230000] vgaarb: loaded
[    0.240000] NET: Registered protocol family 2
[    0.240000] IP route cache hash table entries: 2048 (order: 1, 8192
bytes)
[    0.240000] TCP established hash table entries: 8192 (order: 4, 65536
bytes)
[    0.250000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.250000] TCP: Hash tables configured (established 8192 bind 8192)
[    0.250000] TCP reno registered
[    0.250000] NET: Registered protocol family 1
[    0.250000] Unpacking initramfs...
[    0.990000] Initramfs unpacking failed: junk in compressed archive
[    0.990000] Freeing initrd memory: 4096K
[    0.990000] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.990000] audit: initializing netlink socket (disabled)
[    0.990000] type=2000 audit(0.990:1): initialized
[    1.000000] VFS: Disk quotas dquot_6.5.2
[    1.000000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.000000] msgmni has been set to 500
[    1.000000] alg: No test for stdrng (krng)
[    1.010000] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[    1.010000] io scheduler noop registered
[    1.010000] io scheduler anticipatory registered
[    1.010000] io scheduler deadline registered
[    1.010000] io scheduler cfq registered (default)
[    1.020000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.020000] serial8250.0: ttyS0 at MMIO 0xfe800000 (irq = 28) is a 16550A
[    1.370000] console [ttyS0] enabled
[    1.370000] physmap platform flash device: 02000000 at f0000000
[    1.380000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
[    1.380000]  Intel/Sharp Extended Query Table at 0x0031
[    1.390000]  Intel/Sharp Extended Query Table at 0x0031
[    1.390000] Using buffer write method
[    1.400000] cfi_cmdset_0001: Erase suspend on write enabled
[    1.400000] Searching for RedBoot partition table in physmap-flash.0 at
offset 0x7e0000
[    1.540000] 10 RedBoot partitions found on MTD device physmap-flash.0
[    1.540000] Creating 10 MTD partitions on "physmap-flash.0":
[    1.550000] 0x000000000000-0x000000040000 : "RedBoot"
[    1.560000] 0x000000040000-0x000000240000 : "zImage"
[    1.560000] 0x000000240000-0x000000640000 : "ramdisk.gz"
[    1.570000] 0x000000640000-0x000000700000 : "wmdata"
[    1.570000] 0x000000700000-0x000000740000 : "rammode"
[    1.580000] 0x000000740000-0x000000760000 : "naskey"
[    1.590000] 0x000000760000-0x0000007a0000 : "log"
[    1.590000] 0x0000007a0000-0x0000007c0000 : "vendor"
[    1.600000] 0x0000007c0000-0x0000007c1000 : "RedBoot config"
[    1.610000] mtd: partition "RedBoot config" doesn't end on an erase block
-- force read-only
[    1.620000] 0x0000007e0000-0x000000800000 : "FIS directory"
[    1.620000] mice: PS/2 mouse device common for all mice
[    1.630000] i2c /dev entries driver
[    1.640000] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
[    1.640000] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
[    1.650000] i2c i2c-0: failed,FF11,11,05
[    1.680000] iop-adma iop-adma.0: Intel(R) IOP: ( cpy intr )
[    1.700000] iop-adma iop-adma.1: Intel(R) IOP: ( cpy intr )
[    1.700000] TCP cubic registered
[    1.710000] NET: Registered protocol family 17
[    1.710000] XScale DSP coprocessor detected.
[    1.720000] registered taskstats version 1
[    1.720000] rtc-rs5c372 0-0032: setting system clock to 2012-07-19
19:35:53 UTC (1342726553)
[    1.730000] Initalizing network drop monitor service
[    1.740000] Freeing init memory: 112K
Loading, please wait...
/scripts/init-top/udev: line 17: udevd: not found
Begin: Loading essential drivers ... /init: line 205: modprobe: not found
/init: line 205: modprobe: not found
/init: line 205: modprobe: not found
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 :(

CW

-----Original Message-----
From: JF Straeten [mailto:jfstraeten@scarlet.be] 
Sent: Thursday, July 19, 2012 12:25 PM
To: debian-arm@lists.debian.org
Subject: Re: SS4000E Fan speed, LEDS and power button


Chris,


On Thu, Jul 19, 2012 at 09:49:53AM -0400, Chris Wilkinson wrote:

> Sorry for all the questions.

Well, it's what mailing lists are for :-)

 
> Should I create a swap partition on one disk prior to assembling
> RAID [...]

It depends on what you want.

If you want your swap on RAID, then no : you'll make the swap on the
assembled RAID set, like for other RAID sets.

But if you don't want RAID for swap, then you can create a swap
partition on any disk in the nas, even one on each disk if you want
(tough it's not usefull : you simply don't need (big) swap).

I take the swap on RAID approach because the disks where all the same
size (and so must be the RAID slices) and it was simpler.


> [...] , does it matter which disk it's on?

It also depends...

In the swap on RAID school, you will have a slice of each disk used by
the swap RAID set. 

(Optimization ninjas will probably say here that the place of swap on
the disk itself matters, which is true in theory, but in practice, and
considering the low speed and/or usage of the box, these
considerations have little interest, if any...)


If the swap is apart, in theory it probably matters, but in practice I
think it will not make any difference where swap is. It's even
possible that the kernel will not use the swap at all. (Mine doesn't
swap a lot at all, if it does...)

 
> You said to make all to make all RAID slices the same size, [...]

(Yes, but obviously, all the same size **in a given RAID set**. You
can of course have RAID sets of different sizes, which is the case in
the output from yesterday.)


> [...] so the swap size would have to be allocated to a partition on
> all disks?

Yes, it's one of the possibilies. You'll probably find usefull
informations on RAID in the Debian installation manual if not already
read.

To summarize, take a look at this table :

lothar:~# sfdisk -l /dev/sd[a-d]

Disk /dev/sda: 38913 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting
from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sda1          0+    303     304-   2441848+  fd  Linux raid autodetect
/dev/sda2        304     365      62     498015   fd  Linux raid autodetect
/dev/sda3        366   38912   38547  309628777+  fd  Linux raid autodetect

Disk /dev/sdb: 38913 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting
from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdb1          0+    303     304-   2441848+  fd  Linux raid autodetect
/dev/sdb2        304     365      62     498015   fd  Linux raid autodetect
/dev/sdb3        366   38912   38547  309628777+  fd  Linux raid autodetect

Disk /dev/sdc: 38913 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting
from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdc1          0+    303     304-   2441848+  fd  Linux raid autodetect
/dev/sdc2        304     365      62     498015   fd  Linux raid autodetect
/dev/sdc3        366   38912   38547  309628777+  fd  Linux raid autodetect

Disk /dev/sdd: 38913 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting
from 0

   Device Boot Start     End   #cyls    #blocks   Id  System
/dev/sdd1          0+    303     304-   2441848+  fd  Linux raid autodetect
/dev/sdd2        304     365      62     498015   fd  Linux raid autodetect
/dev/sdd3        366   38912   38547  309628777+  fd  Linux raid autodetect



You see 4 disks of 320 GB each.

They are partionned exactly the same.

Next, I take each three groups of four same partitions on each disk to
assemble the RAID sets :

/dev/sd[a-d]1 make together /dev/md0 in RAID 1, mounted on /
/dev/sd[a-d]2 make together /dev/md1 in RAID1, formated as swap
/dev/sd[a-d]3 make together /dev/md2, in RAID5 mounted as /srv

 
> Where does the boot sector go? Does that need a partition?

I don't think so. Theses boxes are curiosa which doesn't boot from
hard disk, but from an embeded flash memory on the MB.

So, d-i will probably write the boot sectors on each disk of the RAID
set mounted as /, through the RAID device (/dev/md0 in my case), but
unusefully since the nas will not use hard disk to boot...

(I'm not absolulety sure, but I don't see either where the hard disks
are involved in the boot process...)

Hih,

-- 

JFS.


-- 
To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Archive: 20120719162514.GA22642@jones.jfs.dt">http://lists.debian.org/20120719162514.GA22642@jones.jfs.dt