Upgraded from Basic to Pro today and had a problem adding new disks.  Starting from a working 2+1 array from Basic, I attempted to add 4 new disks.  The disks cleared successfully and the management console showed that they were being mounted, but that's as far as it got.  The drives were still unmounted and the array still down an hour after completing the clear.

 

Some basic info:

MB - GA-EP45-UD3P (8 on-board SATA ports)

RAM - 2 x 1GB DDR2 800

CPU - E3300

Working array was:

parity device:  pci-0000:00:1f.2-scsi-0:0:0:0 host5 (sdb) WDC_WD20EADS-00R6B0_WD-WCAVY1851994

disk1 device: pci-0000:00:1f.2-scsi-2:0:0:0 host7 (sdd) WDC_WD20EADS-14R6B0_WD-WCAVY2104960

disk2 device: pci-0000:00:1f.2-scsi-1:0:0:0 host6 (sdc) WDC_WD20EADS-14R6B0_WD-WCAVY2106866

 

New disks were 3 x 2TB WD Green + 1 x 1.5TB WD Green.

 

Here's the relevant section of the syslog showing that a bug was hit:

 

Feb 26 21:39:47 Tower emhttp: ... clearing 100% complete

Feb 26 21:39:47 Tower emhttp: ... syncing

Feb 26 21:39:58 Tower kernel: mdcmd (83): start PROTECTED_EXPANSION

Feb 26 21:39:58 Tower kernel: unraid: allocating 38700K for 1280 stripes (7 disks)

Feb 26 21:39:58 Tower kernel: md1: running, size: 1953514552 blocks

Feb 26 21:39:58 Tower kernel: md2: running, size: 1953513496 blocks

Feb 26 21:39:58 Tower kernel: md3: running, size: 1953514552 blocks

Feb 26 21:39:58 Tower kernel: md4: running, size: 1953514552 blocks

Feb 26 21:39:58 Tower kernel: md5: running, size: 1953514552 blocks

Feb 26 21:39:58 Tower kernel: md6: running, size: 1465138552 blocks

Feb 26 21:39:58 Tower kernel: mdcmd (85): spindown 3

Feb 26 21:39:59 Tower kernel: mdcmd (86): spindown 4

Feb 26 21:40:00 Tower kernel: mdcmd (88): spindown 5

Feb 26 21:40:00 Tower kernel: BUG: unable to handle kernel paging request at f8559000

Feb 26 21:40:00 Tower kernel: IP: [<f854e8c4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Feb 26 21:40:00 Tower kernel: *pdpt = 0000000001428001 *pde = 0000000002ee5067 *pte = 0000000000000000

Feb 26 21:40:00 Tower kernel: Oops: 0000 [#1] SMP

Feb 26 21:40:00 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host10/target10:0:0/10:0:0:0/block/sdg/stat

Feb 26 21:40:00 Tower kernel: Modules linked in: md_mod xor r8169 pata_jmicron jmicron ahci sata_sil24 [last unloaded: md_mod]

Feb 26 21:40:00 Tower kernel:

Feb 26 21:40:00 Tower kernel: Pid: 1605, comm: emhttp Not tainted (2.6.31.12-unRAID #1) EP45-UD3P

Feb 26 21:40:00 Tower kernel: EIP: 0060:[<f854e8c4>] EFLAGS: 00210202 CPU: 0

Feb 26 21:40:00 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Feb 26 21:40:00 Tower kernel: EAX: c3d1df38 EBX: fffffc1c ECX: 3ffff1b2 EDX: fffffc1c

Feb 26 21:40:00 Tower kernel: ESI: f8559000 EDI: cfd75554 EBP: c3d1df04 ESP: c3d1def4

Feb 26 21:40:00 Tower kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Feb 26 21:40:00 Tower kernel: Process emhttp (pid: 1605, ti=c3d1c000 task=c2f090e0 task.ti=c3d1c000)

Feb 26 21:40:00 Tower kernel: Stack:

Feb 26 21:40:00 Tower kernel:  c3d1df38 f854e883 00000000 cfd72000 c3d1df4c c10982ad 00000400 c3d1df3c

Feb 26 21:40:00 Tower kernel: <0> 00000000 00000400 00000000 00000400 b78c1000 c4361d80 00000000 c4361d80

Feb 26 21:40:00 Tower kernel: <0> 00000400 cfd72000 00000001 c4361d80 c10981a2 fffffffb c3d1df70 c1094c9e

Feb 26 21:40:00 Tower kernel: Call Trace:

Feb 26 21:40:00 Tower kernel:  [<f854e883>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Feb 26 21:40:00 Tower kernel:  [<c10982ad>] ? proc_file_read+0x10b/0x22d

Feb 26 21:40:00 Tower kernel:  [<c10981a2>] ? proc_file_read+0x0/0x22d

Feb 26 21:40:00 Tower kernel:  [<c1094c9e>] ? proc_reg_read+0x56/0x6a

Feb 26 21:40:00 Tower kernel:  [<c1094c48>] ? proc_reg_read+0x0/0x6a

Feb 26 21:40:00 Tower kernel:  [<c1068146>] ? vfs_read+0x8a/0x114

Feb 26 21:40:00 Tower kernel:  [<c10684dd>] ? sys_read+0x3b/0x60

Feb 26 21:40:00 Tower kernel:  [<c1002975>] ? syscall_call+0x7/0xb

Feb 26 21:40:00 Tower kernel: Code: 55 f0 e8 3a e6 bd c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 56 55 f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89

Feb 26 21:40:00 Tower kernel: EIP: [<f854e8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3d1def4

Feb 26 21:40:00 Tower kernel: CR2: 00000000f8559000

Feb 26 21:40:00 Tower kernel: ---[ end trace af9320abc3e831cb ]---

Feb 26 21:40:00 Tower kernel: mdcmd (89): spindown 6

Feb 26 22:37:51 Tower in.telnetd[1928]: connect from 192.168.1.10 (192.168.1.10)

Feb 26 22:37:55 Tower login[1929]: invalid password for `UNKNOWN'  on `pts/0' from `192.168.1.10'

Feb 26 22:37:57 Tower login[1929]: ROOT LOGIN  on `pts/0' from `192.168.1.10'

 

 

If you can, post the full syslog, then you can try re-booting the server.

 

Send support@lime-technology an e-mail pointing him to this post.

 

If the management web-page has stopped responding you can try re-starting it with

killall emhttp

/usr/local/sbin/emhttp &

 

Thanks.  I was able to get the 4 disks added by adding them two at a time instead of all 4 at once.  Probably hit a race condition or edge case somewhere the first time.