June 27, 201016 yr I'm having a lot of problems adding more drives to my 4.5.3 unraid setup. Everytime i do so the server eventually crashes at some point before completion. This happens regardless of the drive used, i have tried 3 different drives from 2 different manufacturers, all of which pass their smartctl test. This happens with me adding drives directly from the server web interface, but I also encounter crashes if i run the preclear_disk.sh script. The hardware is pretty similar to the UK recommended hardware from the wiki (CPU: 2.7 GHz AMD Sempron 140, Motherboard: Biostar TA785GE, 2Gb Memory). The current working array is made up of a 2tb parity drive, and 2tb disks1 and 2, and has been working without any issues or errors. Unfortunately due to it crashing each time I cannot get any information from the syslog, but the last time I tried to add a 1.5Tb drive I left it logged in via telnet and got some information back. Jun 26 06:09:36 unRAID emhttp: ... clearing 1% complete Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: Process kblockd/0 (pid: 116, ti=f759a000 task=f7581810 task.ti=f759a000) Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: Stack: Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: Call Trace: Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: Code: 8b 41 04 55 89 e5 89 42 04 89 10 5d 89 09 89 49 04 c3 55 31 d2 89 e5 53 89 c3 8b 40 0c 8b 40 04 8b 08 39 c1 74 1d 8b 11 8b 41 04 <89> 42 04 89 10 89 ca 89 d8 89 09 89 49 04 e8 a2 84 ff ff ba 01 Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: EIP: [<c1128d4a>] noop_dispatch+0x19/0x36 SS:ESP 0068:f759bed8 Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: CR2: 0000000000000004 Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:14.1/ide0/0.0/block/hda/stat Message from syslogd@unRAID at Sun Jun 27 06:21:19 2010 ... unRAID kernel: Oops: 0002 [#1] SMP As you can see it was running for over 24 hours on that attempt, I'm not sure how far it progressed but the last time that i checked at around 6hrs before the crash it was around 70% complete on the clear. I have run the memtest utility and it is reporting no errors, and I am now at a bit of a loss as to how to proceed. Any suggestions would be much appreciated.
June 27, 201016 yr If you can capture more the log that would be helpful. From a telnet session type: tail -f /var/log/syslog Then when crash happens, select/copy/paste the window contents. Memtest does not always find all memory problems. If you have 2 sticks of RAM, remove one of them & see if crash still occurs. If so, put it back and remove the other one, repeat test. Another test is to use a different controller port. What is the exact model number of your power supply?
June 27, 201016 yr Author Thanks for the response. Power supply is also the one mentioned in the wiki (Power Supply: Corsair CX-400 400W). Trying again with tail, will see if it reports anything more conclusive. I have tried using different sata ports on the motherboard and different sata cables but that doesn't seem to make much difference. I have a single 2Gb memory stick in atm, but i may have another stick around that i can test with.
June 27, 201016 yr Author Just as an update to my previous message, tried to add a drive from the web interface and it crashed again, received the following output from the syslog with tail: Jun 27 21:45:55 unRAID emhttp: ... clearing 48% complete Jun 27 22:02:02 unRAID emhttp: ... clearing 49% complete Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: Process kblockd/0 (pid: 116, ti=f759a000 task=f7581810 task.ti=f759a000) Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: Stack: Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: Call Trace: Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: Code: 00 00 00 29 00 00 00 c0 92 26 f7 a0 45 96 c4 e3 3c fb 55 00 00 00 00 00 02 00 00 00 d6 02 c8 00 32 02 f7 a5 83 08 c1 00 00 00 00 <28> 93 26 f7 28 93 26 f7 00 00 00 00 00 00 00 00 40 93 26 f7 00 Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: EIP: [<f7269328>] 0xf7269328 SS:ESP 0068:f759befc Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: CR2: 00000000f7269328 Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:14.1/ide0/0.0/block/hda/stat Message from syslogd@unRAID at Sun Jun 27 22:06:13 2010 ... unRAID kernel: Oops: 0011 [#1] SMP Jun 27 22:06:13 unRAID kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0) Jun 27 22:06:13 unRAID kernel: BUG: unable to handle kernel paging request at f7269328 Jun 27 22:06:13 unRAID kernel: IP: [<f7269328>] 0xf7269328 Jun 27 22:06:13 unRAID kernel: *pdpt = 0000000001443001 *pde = 80000000372001e3 Jun 27 22:06:13 unRAID kernel: Oops: 0011 [#1] SMP Jun 27 22:06:13 unRAID kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:14.1/ide0/0.0/block/hda/stat Jun 27 22:06:13 unRAID kernel: Modules linked in: md_mod xor ide_gd_mod atiixp ahci r8169 Jun 27 22:06:13 unRAID kernel: Jun 27 22:06:13 unRAID kernel: Pid: 116, comm: kblockd/0 Not tainted (2.6.32.9-unRAID #1) TA785GE 128M Jun 27 22:06:13 unRAID kernel: EIP: 0060:[<f7269328>] EFLAGS: 00010286 CPU: 0 Jun 27 22:06:13 unRAID kernel: EIP is at 0xf7269328 Jun 27 22:06:13 unRAID kernel: EAX: f74fb000 EBX: f74fb000 ECX: f7269328 EDX: d547f190 Jun 27 22:06:13 unRAID kernel: ESI: f7574e00 EDI: 00000000 EBP: f759bf68 ESP: f759befc Jun 27 22:06:13 unRAID kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Jun 27 22:06:13 unRAID kernel: Process kblockd/0 (pid: 116, ti=f759a000 task=f7581810 task.ti=f759a000) Jun 27 22:06:13 unRAID kernel: Stack: Jun 27 22:06:13 unRAID kernel: c119d317 5607163f 00000000 f7574ff8 c40bbf60 f75ecd20 d547f190 c13ca774 Jun 27 22:06:13 unRAID kernel: <0> c143e240 f7581810 f759bf88 c129b664 c13ca6e0c10284de c143e240 c143e240 Jun 27 22:06:13 unRAID kernel: <0> c143ae78 f7581810 f7581998 c5805240 00000000c42b8e00 c40bbf60 c11213c5 Jun 27 22:06:13 unRAID kernel: Call Trace: Jun 27 22:06:13 unRAID kernel: [<c119d317>] ? do_ide_request+0x33d/0x4c3 Jun 27 22:06:13 unRAID kernel: [<c129b664>] ? schedule+0x691/0x72f Jun 27 22:06:13 unRAID kernel: [<c10284de>] ? irq_exit+0x29/0x2b Jun 27 22:06:13 unRAID kernel: [<c11213c5>] ? blk_unplug_work+0x0/0x10 Jun 27 22:06:13 unRAID kernel: [<c11213c5>] ? blk_unplug_work+0x0/0x10 Jun 27 22:06:13 unRAID kernel: [<c1122ef8>] ? __generic_unplug_device+0x26/0x29 Jun 27 22:06:13 unRAID kernel: [<c11231be>] ? generic_unplug_device+0x21/0x2d Jun 27 22:06:13 unRAID kernel: [<c11213d3>] ? blk_unplug_work+0xe/0x10 Jun 27 22:06:13 unRAID kernel: [<c10314cd>] ? worker_thread+0xeb/0x15f Jun 27 22:06:13 unRAID kernel: [<c10338a5>] ? autoremove_wake_function+0x0/0x30 Jun 27 22:06:13 unRAID kernel: [<c10313e2>] ? worker_thread+0x0/0x15f Jun 27 22:06:13 unRAID kernel: [<c10337f1>] ? kthread+0x61/0x68 Jun 27 22:06:13 unRAID kernel: [<c1033790>] ? kthread+0x0/0x68 Jun 27 22:06:13 unRAID kernel: [<c100339f>] ? kernel_thread_helper+0x7/0x1a Jun 27 22:06:13 unRAID kernel: Code: 00 00 00 29 00 00 00 c0 92 26 f7 a0 45 96 c 4 e3 3c fb 55 00 00 00 00 00 02 00 00 00 d6 02 c8 00 32 02 f7 a5 83 08 c1 00 00 00 00 <28> 93 26 f7 28 93 26 f7 00 00 00 00 00 00 00 00 40 93 26 f7 00 Jun 27 22:06:13 unRAID kernel: EIP: [<f7269328>] 0xf7269328 SS:ESP 0068:f759befc Jun 27 22:06:13 unRAID kernel: CR2: 00000000f7269328 Jun 27 22:06:13 unRAID kernel: ---[ end trace 4e769d4327dbdd4a ]--- Will try and replace the memory tomorrow and see if it makes any difference.
June 27, 201016 yr The kernel process that flushes data blocks to disk is getting a fault reported by the low level disk driver - never seen this one before. Something to try is disable the on-board IDE port in the bios as well as disable the sound chip in the bios if possible.
Archived
This topic is now archived and is closed to further replies.