Jump to content

Stuck on Starting..... after new disk added


jouyang

Recommended Posts

Hi All,

 

My unRaid 4.5.3 seems to stuck at Starting.... after adding a new disk.  I'm only getting "Starting..." from the command area. Also, all the drives have "Mounting" status. Here's a copy of the Log. Should I just do a reboot or is there a better to restart it?

 

BTW, anyone know what is this bug? Nov 16 06:48:44 Tower kernel: BUG: unable to handle kernel paging request at f8bfa000

 

TIA,

~joy

 

 

 

 

 

Nov 16 06:25:47 Tower emhttp: ... clearing 95% complete

Nov 16 06:30:18 Tower emhttp: ... clearing 96% complete

Nov 16 06:34:49 Tower emhttp: ... clearing 97% complete

Nov 16 06:39:21 Tower emhttp: ... clearing 98% complete

Nov 16 06:43:59 Tower emhttp: ... clearing 99% complete

Nov 16 06:48:41 Tower emhttp: ... clearing 100% complete

Nov 16 06:48:41 Tower emhttp: ... syncing

Nov 16 06:48:42 Tower kernel: mdcmd (23): start PROTECTED_EXPANSION

Nov 16 06:48:42 Tower kernel: unraid: allocating 84780K for 1280 stripes (16 disks)

Nov 16 06:48:42 Tower kernel: md1: running, size: 1953514552 blocks

Nov 16 06:48:42 Tower kernel: md2: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: md3: running, size: 1953514552 blocks

Nov 16 06:48:42 Tower kernel: md8: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: md9: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: md10: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: md11: running, size: 1953514552 blocks

Nov 16 06:48:42 Tower kernel: md12: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: md13: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: md15: running, size: 976762552 blocks

Nov 16 06:48:42 Tower kernel: mdcmd (25): spindown 0

Nov 16 06:48:43 Tower kernel: mdcmd (26): spindown 1

Nov 16 06:48:44 Tower kernel: mdcmd (28): spindown 2

Nov 16 06:48:44 Tower kernel: BUG: unable to handle kernel paging request at f8bfa000

Nov 16 06:48:44 Tower kernel: IP: [<f8bf08c4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Nov 16 06:48:44 Tower kernel: *pdpt = 0000000001443001 *pde = 0000000036e07067 *pte = 0000000000000000

Nov 16 06:48:44 Tower kernel: Oops: 0000 [#1] SMP

Nov 16 06:48:44 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host9/target9:0:1/9:0:1:0/block/sdh/stat

Nov 16 06:48:44 Tower kernel: Modules linked in: md_mod xor ata_piix sata_mv r8169 [last unloaded: md_mod]

Nov 16 06:48:44 Tower kernel:

Nov 16 06:48:44 Tower kernel: Pid: 25747, comm: emhttp Not tainted (2.6.32.9-unRAID #1) C2SEA

Nov 16 06:48:44 Tower kernel: EIP: 0060:[<f8bf08c4>] EFLAGS: 00210202 CPU: 2

Nov 16 06:48:44 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Nov 16 06:48:44 Tower kernel: EAX: c4703f38 EBX: fffff01c ECX: 3fffef6f EDX: fffff01c

Nov 16 06:48:44 Tower kernel: ESI: f8bfa000 EDI: f3752260 EBP: c4703f04 ESP: c4703ef4

Nov 16 06:48:44 Tower kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Nov 16 06:48:44 Tower kernel: Process emhttp (pid: 25747, ti=c4702000 task=f74b5ef0 task.ti=c4702000)

Nov 16 06:48:44 Tower kernel: Stack:

Nov 16 06:48:44 Tower kernel:  c4703f38 f8bf0883 00000000 f374f000 c4703f4c c109d56d 00000400 c4703f3c

Nov 16 06:48:44 Tower kernel: <0> 00000000 00000400 00000000 00000400 b78ce000 f75afde0 00000000 f75afde0

Nov 16 06:48:44 Tower kernel: <0> 00000400 f374f000 00000001 f75afde0 c109d462 fffffffb c4703f70 c1099eea

Nov 16 06:48:44 Tower kernel: Call Trace:

Nov 16 06:48:44 Tower kernel:  [<f8bf0883>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Nov 16 06:48:44 Tower kernel:  [<c109d56d>] ? proc_file_read+0x10b/0x22d

Nov 16 06:48:44 Tower kernel:  [<c109d462>] ? proc_file_read+0x0/0x22d

Nov 16 06:48:44 Tower kernel:  [<c1099eea>] ? proc_reg_read+0x56/0x6a

Nov 16 06:48:44 Tower kernel:  [<c1099e94>] ? proc_reg_read+0x0/0x6a

Nov 16 06:48:44 Tower kernel:  [<c106cb60>] ? vfs_read+0x8a/0x114

Nov 16 06:48:44 Tower kernel:  [<c106cef7>] ? sys_read+0x3b/0x60

Nov 16 06:48:44 Tower kernel:  [<c1002935>] ? syscall_call+0x7/0xb

Nov 16 06:48:44 Tower kernel: Code: 55 f0 e8 da 27 54 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 a0 5d bf 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

Nov 16 06:48:44 Tower kernel: EIP: [<f8bf08c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c4703ef4

Nov 16 06:48:44 Tower kernel: CR2: 00000000f8bfa000

Nov 16 06:48:44 Tower kernel: ---[ end trace 6f54d6e1b0c18df8 ]---

Nov 16 06:48:45 Tower kernel: mdcmd (29): spindown 3

Nov 16 06:48:46 Tower kernel: mdcmd (30): spindown 8

Nov 16 06:48:47 Tower kernel: mdcmd (31): spindown 9

Nov 16 06:48:49 Tower kernel: mdcmd (32): spindown 10

Nov 16 06:48:49 Tower kernel: mdcmd (33): spindown 11

Nov 16 06:48:50 Tower kernel: mdcmd (34): spindown 12

Nov 16 06:48:51 Tower kernel: mdcmd (35): spindown 13

Nov 16 06:48:52 Tower kernel: mdcmd (36): spindown 15

Nov 16 22:29:13 Tower login[22060]: ROOT LOGIN  on `tty1'

Nov 16 22:35:32 Tower in.telnetd[26021]: connect from 192.168.1.111 (192.168.1.111)

Nov 16 22:35:38 Tower login[26022]: ROOT LOGIN  on `pts/0' from `192.168.1.111'

syslog2.txt

Link to comment

wow, one bug after another. The memory came back good but I hit the unRaid 4.5.3 all disks unformatted bug. Good thing I wasn't finger happy to click on the Format button to add the new disk. Anyway, I think I should upgrade to 4.7. Does anyone know if there's any major bug on 4.7 that I can read about?

 

thanks,

~joy

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...