February 18, 200818 yr Good afternoon all, I am still making progress towards having a full fledge unRAID server, but I need your help once again. For some reason, my on-board NICs are not working properly. One NIC is working when I first boot the server, but during the first large data transfer, it seems to hang and requires me to completely reboot the server. The other NIC does not work at all, but I figured this was a limitation of unRAID. I have an Intel Pro/1000 that I would like to try/use. If I place the card in the server, disable the on-board NICs and try to use the Intel NIC, unRAID use it. From the boot log, it looks like it sees the card, but it still tries to acquire an IP address from the on-board (eth0) NIC. So two questions - Can I try to use the other on-board NIC ? How can I do that ? How do I tell unRAID to use the Intel NIC, not not use eth0 ? Ideally, I would like to use both on-board NICs, but I gather that's not possible. I am using 4.2.1 on a DFI LanParty RDX-200 motherboard. The on-board NICs are a Marvell 88E8053 on the PCI Express bus and a Marvell 88E8001 on the PCI bus. (BTW, Is there one of the on-board NIC that's better to use than the other ?) Thank you in advance for you help !
February 18, 200818 yr From a performance standpoint, it is generally always better to keep the NIC off the PCI bus, unless you have no drives using the PCI bus. If it is not working though, you don't have a choice. I believe I recall someone else having problems with their BIOS not properly disabling the individual onboard NIC's. Have you checked for a BIOS update? If the first NIC were disabled correctly, then unRAID should normally use the other, as it is now the first it finds. I believe both Marvell chips are common, and supported by unRAID.
February 18, 200818 yr Author From a performance standpoint, it is generally always better to keep the NIC off the PCI bus, unless you have no drives using the PCI bus. If it is not working though, you don't have a choice. I believe I recall someone else having problems with their BIOS not properly disabling the individual onboard NIC's. Have you checked for a BIOS update? If the first NIC were disabled correctly, then unRAID should normally use the other, as it is now the first it finds. I believe both Marvell chips are common, and supported by unRAID. Thanks for your reply. Do you know how I could determine which on-board NIC is being used (PCI or PCI-X), and how I could force unRAID to use one or the other ? All I can see in the BIOS is a setting to enable or disable the on-board NIC under the PCI options.
February 18, 200818 yr Author And here is my syslog with the on-board NICs enabled. Shortly after copying that syslog to the flash, I tried to copy a large file set to the server which "crashed" the server, requiring a reboot. The last line of the on-screen log was something to the effect of "Kernel Panic - not syncing: Fatal exception in interupt" The preceding line mentioned "... sky2.status... " Does that help ? Thanks again.
February 18, 200818 yr That is an unhappy computer. You've not only got NIC problems, you have hard disk problems, and I suspect the Seagate 320GB is responsible for the crashes, not the network problems. SMART does not appear to be working on it, and that could be because the drive is defective, or a bad cable, or bad controller, or wrong driver for the controller. You could try changing the cable, and switch the connection to another controller, but you may also need to pull that drive and try another. The kernel is definitely seeing all 3 NIC's without a problem, and assigning eth0 (using sky2 driver) to the Marvell NIC on the PCI bus, eth1 (using e1000 driver) to the Intel Pro on the PCI bus, and when turned on is assigning eth2 (using skge driver) to the Marvell NIC on an unknown bus. unRAID is trying to use the eth0 NIC every time. I can't tell for sure which one you had the cable hooked to, but it appears to be correctly connected to eth0 when you had indicated you enabled the onboard NIC's, but is not connected to eth0 when you disabled the NIC's. Your BIOS really should have 2 options for enabling/disabling the NIC's, one for each. The eth0 NIC is definitely not being disabled, so you cannot use the other or the Intel, without someone else more Linux knowledgeable than me showing you how to use eth1 or eth2.
February 19, 200818 yr Author That is an unhappy computer. You've not only got NIC problems, you have hard disk problems, and I suspect the Seagate 320GB is responsible for the crashes, not the network problems. SMART does not appear to be working on it, and that could be because the drive is defective, or a bad cable, or bad controller, or wrong driver for the controller. You could try changing the cable, and switch the connection to another controller, but you may also need to pull that drive and try another. How could it be unhappy ? It's not doing any of the heavy lifting yet ... I am the one who should be unhappy !!! <grin> Thanks for taking the time. I don't think it's the drive, but I'll try changing the cable, switching the SATA controller that the drive is on. Unfortunately, I can't change the driver, right ? unRAID does support the Sillicon Image Sil 3114, doesn't it ? As for the drive itself, I have a bunch of those sitting and serving me well. I do however remember having problems with them using a SMART monitoring utility in Windows XP. If I recall correctly, Seagate doesn't use standard SMART parameters, and therefore the drive shows a bunch or "poor" values but the drive is fine. Is that what the log is reporting ? (I really got to beef up my Linux knowledge ... ) The kernel is definitely seeing all 3 NIC's without a problem, and assigning eth0 (using sky2 driver) to the Marvell NIC on the PCI bus, eth1 (using e1000 driver) to the Intel Pro on the PCI bus, and when turned on is assigning eth2 (using skge driver) to the Marvell NIC on an unknown bus. unRAID is trying to use the eth0 NIC every time. I can't tell for sure which one you had the cable hooked to, but it appears to be correctly connected to eth0 when you had indicated you enabled the onboard NIC's, but is not connected to eth0 when you disabled the NIC's. Your BIOS really should have 2 options for enabling/disabling the NIC's, one for each. The eth0 NIC is definitely not being disabled, so you cannot use the other or the Intel, without someone else more Linux knowledgeable than me showing you how to use eth1 or eth2. I really want to see if I can use the Intel NIC. I really suspect that's the problems (I know, I know .... I have a hard head). Here's why - one of the crashes I had listed something about "...sky2..." in the line before the fatal exception line. I couldn't find an updated BIOS for the board, so I am stuck with that. I really, really appreciate the time you've taken. I am sure we can figure something out. Thanks.
February 19, 200818 yr Author OK, a couple more attempts - here is my syslog with a different SATA cable.
February 19, 200818 yr Author Here is the syslog once I changed both the cable and the controller of the disk. Help !!!!!!
February 19, 200818 yr Author Well, a quick update - tried different cables, plugging the drive into the other controller (the board has two) to no avail. Exact same problem, same symptoms. I don't have a different drive, but I guess that's the next step. Of course, I would love to hear you might have as suggestions. Thanks all.
February 19, 200818 yr You moved it from the ata3 interface to the ata8 interface (internal device interfaces), but the errors are exactly the same. So that seems to eliminate the controller and cable, leaving the drive as the faulty component. Seagates may have their SMART eccentricities, but they do work fine, and are probably the favored drive by many unRAID users. Your particular drive though appears to have a defective SMART system. I can see no alternative to replacing it. I know you don't want to accept that the drive could be bad, but look at each of the syslogs you have sent. The last 1/3 to 1/2 of the syslog is primarily errors (and the error handling) from that drive. Your network connection looks fine. And the 3114 is a very common chipset, used by many here, uses the sata_sil driver I believe. The drive is not a total loss. I use a damaged drive with destroyed SMART system in a WinXP system, with SMART disabled in the BIOS setup, works fine.
February 19, 200818 yr Author No, I'm not completely closed minded. I went through all that with a single purpose - find a solution to my problem. Another drive it is ! I truly appreciate the time you have taken to help me. I will report back once I have had a chance to pick up a drive and try that. Thanks again.
February 19, 200818 yr Author OK, one step forward, two steps back ... I'm sorry to report I am back here for your help again. I have purchased a new drive (A nice and shinny 750 Gb Seagate ...because one can't make the trip for less than 500 or 750 Gb nowadays), replaced the faulty 320 Gb drive in the server. Reset the drive info and formatted the new drive. I then tried my first transfer and got the same problem. The transfer initially progressed properly for a minute or two and then stalled again, requiring me to reboot the server. So, while I had some drive problems, it appears not to be related to my transfer problem. I still suspect a NIC problem and would love to try using the Intel Pro/1000 NIC but can't get it to work. I have attached my syslog from the latest boot with the new drive. I would appreciate any help.
February 19, 200818 yr Author More from my syslog before the last crash - Feb 19 15:32:16 MediaStore kernel: [ 119.802701] ReiserFS: md1: journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Feb 19 15:32:16 MediaStore kernel: [ 119.803343] ReiserFS: md1: checking transaction log (md1) Feb 19 15:32:17 MediaStore kernel: [ 119.861182] ReiserFS: md1: replayed 1 transactions in 0 seconds Feb 19 15:32:17 MediaStore kernel: [ 119.911165] ReiserFS: md1: Using r5 hash to sort names Feb 19 15:32:17 MediaStore kernel: [ 119.971159] can't shrink filesystem on-line Feb 19 15:32:17 MediaStore emhttp[827]: shcmd (11): killall -HUP smbd Feb 19 15:33:55 MediaStore kernel: [ 217.881387] spurious 8259A interrupt: IRQ7. Feb 19 15:34:56 MediaStore in.telnetd[882]: connect from 192.168.2.67 (192.168.2.67) Feb 19 15:35:00 MediaStore login[883]: ROOT LOGIN on `pts/0' from `192.168.2.67' Feb 19 15:35:41 MediaStore kernel: [ 324.831222] usb 1-2: USB disconnect, address 2 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.379689] Oops: 0000 [#1] Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380051] CPU: 0 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380052] EIP: 0060:[<c015ca58>] Not tainted VLI Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380054] EFLAGS: 00010212 (2.6.22.5 #9) Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380383] EIP is at writeback_inodes+0x16/0x64 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380496] eax: fb352270 ebx: fb352200 ecx: dffbc670 edx: 00000000 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380612] esi: dffbc63c edi: de3cff64 ebp: 00000000 esp: de3cff4c Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380729] ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380844] Process pdflush (pid: 85, ti=de3ce000 task=de3695b0 task.ti=de3ce000) Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.380961] Stack: 00012bbf de3cffc0 00000bbd c0133c4c 00012b29 c0110907 00000000 00000000 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.381208] de3cff5c 00000400 00000000 00000000 00000000 00000000 00000000 00000025 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.381455] 00000000 de3cffc0 de3cffb4 fffffffc c01344df c038f8a0 00000000 c013455d Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.381702] Call Trace: Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.381910] [<c0133c4c>] wb_kupdate+0x6f/0xcd Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382025] [<c0110907>] set_load_weight+0x5c/0x72 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382143] [<c01344df>] __pdflush+0xaf/0x12d Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382258] [<c013455d>] pdflush+0x0/0x27 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382373] [<c0134580>] pdflush+0x23/0x27 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382487] [<c0133bdd>] wb_kupdate+0x0/0xcd Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382602] [<c0121291>] kthread+0x33/0x54 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382716] [<c012125e>] kthread+0x0/0x54 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382829] [<c0103cfb>] kernel_thread_helper+0x7/0x10 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.382946] ======================= Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.383054] Code: 54 24 08 83 7a 0c 00 0f 8f 53 fe ff ff 83 c4 0c 5b 5e 5f 5d c3 57 89 c7 56 53 8b 1d b0 29 34 c0 81 fb ac 29 34 c0 74 4d 8d 43 70 <39> 43 70 75 08 8d 43 78 39 43 78 74 32 ff 43 54 8d 73 3c 89 f0 Message from syslogd@MediaStore at Tue Feb 19 15:49:29 2008 ... MediaStore kernel: [ 1152.383634] EIP: [<c015ca58>] writeback_inodes+0x16/0x64 SS:ESP 0068:de3cff4c Feb 19 15:49:29 MediaStore kernel: [ 1152.379250] BUG: unable to handle kernel paging request at virtual address fb352270 Feb 19 15:49:29 MediaStore kernel: [ 1152.379472] printing eip: Feb 19 15:49:29 MediaStore kernel: [ 1152.379579] c015ca58 Feb 19 15:49:29 MediaStore kernel: [ 1152.379581] *pde = 00000000 Feb 19 15:49:29 MediaStore kernel: [ 1152.379689] Oops: 0000 [#1] Feb 19 15:49:29 MediaStore kernel: [ 1152.379796] Modules linked in: md_mod fuse skge e1000 sky2 atiixp ide_core sata_sil libata Feb 19 15:49:29 MediaStore kernel: [ 1152.380051] CPU: 0 Feb 19 15:49:29 MediaStore kernel: [ 1152.380052] EIP: 0060:[<c015ca58>] Not tainted VLI Feb 19 15:49:29 MediaStore kernel: [ 1152.380054] EFLAGS: 00010212 (2.6.22.5 #9) Feb 19 15:49:29 MediaStore kernel: [ 1152.380383] EIP is at writeback_inodes+0x16/0x64 Feb 19 15:49:29 MediaStore kernel: [ 1152.380496] eax: fb352270 ebx: fb352200 ecx: dffbc670 edx: 00000000 Feb 19 15:49:29 MediaStore kernel: [ 1152.380612] esi: dffbc63c edi: de3cff64 ebp: 00000000 esp: de3cff4c Feb 19 15:49:29 MediaStore kernel: [ 1152.380729] ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 Feb 19 15:49:29 MediaStore kernel: [ 1152.380844] Process pdflush (pid: 85, ti=de3ce000 task=de3695b0 task.ti=de3ce000) Feb 19 15:49:29 MediaStore kernel: [ 1152.380961] Stack: 00012bbf de3cffc0 00000bbd c0133c4c 00012b29 c0110907 00000000 00000000 Feb 19 15:49:29 MediaStore kernel: [ 1152.381208] de3cff5c 00000400 00000000 00000000 00000000 00000000 00000000 00000025 Feb 19 15:49:29 MediaStore kernel: [ 1152.381455] 00000000 de3cffc0 de3cffb4 fffffffc c01344df c038f8a0 00000000 c013455d Feb 19 15:49:29 MediaStore kernel: [ 1152.381702] Call Trace: Feb 19 15:49:29 MediaStore kernel: [ 1152.381910] [<c0133c4c>] wb_kupdate+0x6f/0xcd Feb 19 15:49:29 MediaStore kernel: [ 1152.382025] [<c0110907>] set_load_weight+0x5c/0x72 Feb 19 15:49:29 MediaStore kernel: [ 1152.382143] [<c01344df>] __pdflush+0xaf/0x12d Feb 19 15:49:29 MediaStore kernel: [ 1152.382258] [<c013455d>] pdflush+0x0/0x27 Feb 19 15:49:29 MediaStore kernel: [ 1152.382373] [<c0134580>] pdflush+0x23/0x27 Feb 19 15:49:29 MediaStore kernel: [ 1152.382487] [<c0133bdd>] wb_kupdate+0x0/0xcd Feb 19 15:49:29 MediaStore kernel: [ 1152.382602] [<c0121291>] kthread+0x33/0x54 Feb 19 15:49:29 MediaStore kernel: [ 1152.382716] [<c012125e>] kthread+0x0/0x54 Feb 19 15:49:29 MediaStore kernel: [ 1152.382829] [<c0103cfb>] kernel_thread_helper+0x7/0x10 Feb 19 15:49:29 MediaStore kernel: [ 1152.382946] ======================= Feb 19 15:49:29 MediaStore kernel: [ 1152.383054] Code: 54 24 08 83 7a 0c 00 0f 8f 53 fe ff ff 83 c4 0c 5b 5e 5f 5d c3 57 89 c7 56 53 8b 1d b0 29 34 c0 81 fb ac 29 34 c0 74 4d 8d 43 70 <39> 43 70 75 08 8d 43 78 39 43 78 74 32 ff 43 54 8d 73 3c 89 f0 Feb 19 15:49:29 MediaStore kernel: [ 1152.383634] EIP: [<c015ca58>] writeback_inodes+0x16/0x64 SS:ESP 0068:de3cff4c Hopefully this will help find a solution. Thanks.
February 20, 200818 yr Doesn't look good. It's not pointing fingers at anything I recognize, just looks like an internal error, a kernel crash. The syslog you attached is almost perfect, no significant problems with the drive, and no problems at all with the network. The 'Oops' occurs after it. I decided to look up your motherboard, and discovered it has an ATI Radeon Xpress 200 CrossFire northbridge and an ATI SB450 southbridge chipset. I am not sure that we have any reports of Linux compatibility with those chipsets, so that makes me wonder if the problem may be motherboard compatibility. Hopefully someone else has a similar board and can vouch for it. I seem to recall someone else recently asking about a board with similar chipsets, and I could not find any positive Linux reports concerning it. Looking back through your syslog, I see problems with ACPI, a BIOS bug message, and a spurious interrupt message, which are not that uncommon, but are definitely not confidence building as to compatibility with the Linux 2.6 kernel. One thing you can do is test your memory, thoroughly. If it turns out to be an incompatible motherboard/chipset, then that *could* account for an incompatibility with the drive SMART system. I would hang onto that original drive, and try it in another machine, first to see if it works well, then to see if you can read SMART values from it with a tool like SpeedFan. The last line of the on-screen log was something to the effect of "Kernel Panic - not syncing: Fatal exception in interupt" The preceding line mentioned "... sky2.status... " Apart from an instance in one syslog where it appeared the network cable was not attached, to the eth0/sky2 port, this quote from an earlier crash is the only evidence that I have seen that might make me suspicious of a network problem. You may be right that it's the fault of one of the NIC's, but there has been nothing visible to me to raise suspicion, apart from the proximity of the sky2 message to the kernel panic message. And unfortunately, I can't conclude anything from this either. Syslog messages are contributed asynchronously by the various components, and are often intermingled. In this case, we know that the kernel is in big trouble, in the process of crashing, and therefore the sky2 driver may very well have been adversely affected, and reporting a spurious problem because of the kernel crash. Disclaimer: I have absolutely no ties to your hardware vendors, I really am not trying to get you to buy more!
February 20, 200818 yr Author Disclaimer: I have absolutely no ties to your hardware vendors, I really am not trying to get you to buy more! Are you sure .... I do now have a beautiful Seagate 750 Gb drive waiting for a good home. Thanks, I really appreciate it. Now, what I would really wish for is - LimeTech to drop by and voice his ideas/suggestions/concerns Some one with a suggestion to select the eth1 or eth2 NIC to figure this out a little more Another user with the same board or similar chipset to sort this out for me I'll see on the world wide "InterWeb" if I can't find out any information on using that chipset with Linux to see if that enlighten me. I'll also see if I can find a simillar board that I can use my socket 939 processors with. (I sadly have to of these boards). I can't tell you enough how much I appreciate your help. I might have to add you to my Christmas card list
February 20, 200818 yr Author I am still trying ... Here is an the the tail -f of the syslog while I was doing a large file transfer - Feb 19 23:48:07 MediaStore kernel: [ 450.758321] sector=1446365168 i=0 00000000 01000000 00000000 0 Feb 19 23:48:07 MediaStore kernel: [ 450.758326] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:07 MediaStore kernel: [ 450.798369] sector=1446369168 i=0 00000000 01000000 00000000 0 Feb 19 23:48:07 MediaStore kernel: [ 450.798374] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:07 MediaStore kernel: [ 450.838322] sector=1446373264 i=0 00000000 01000000 00000000 0 Feb 19 23:48:07 MediaStore kernel: [ 450.838327] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:07 MediaStore kernel: [ 450.878345] sector=1446377360 i=0 00000000 01000000 00000000 0 Feb 19 23:48:07 MediaStore kernel: [ 450.878350] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:08 MediaStore kernel: [ 451.908007] sector=1446381456 i=0 00000000 01000000 00000000 0 Feb 19 23:48:08 MediaStore kernel: [ 451.908012] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:08 MediaStore kernel: [ 451.948129] sector=1446385552 i=0 00000000 01000000 00000000 0 Feb 19 23:48:08 MediaStore kernel: [ 451.948134] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:08 MediaStore kernel: [ 451.988122] sector=1446389648 i=0 00000000 01000000 00000000 0 Feb 19 23:48:08 MediaStore kernel: [ 451.988128] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:08 MediaStore kernel: [ 452.028612] sector=1446393744 i=0 00000000 01000000 00000000 0 Feb 19 23:48:08 MediaStore kernel: [ 452.028617] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:08 MediaStore kernel: [ 452.068610] sector=1446397840 i=0 00000000 01000000 00000000 0 Feb 19 23:48:08 MediaStore kernel: [ 452.068616] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.108682] sector=1446401936 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.108687] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.148632] sector=1446406032 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.148638] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.188112] sector=1446410128 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.188117] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.248090] sector=1446414224 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.248095] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.288148] sector=1446418224 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.288153] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.328136] sector=1446422320 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.328141] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:09 MediaStore kernel: [ 452.368144] sector=1446426416 i=0 00000000 01000000 00000000 0 Feb 19 23:48:09 MediaStore kernel: [ 452.368149] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.407700] sector=1446430512 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.407705] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.447828] sector=1446434512 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.447832] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.487818] sector=1446438608 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.487823] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.528037] sector=1446442704 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.528042] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.568155] sector=1446446800 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.568160] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.608496] sector=1446450896 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.608501] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.648281] sector=1446454992 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.648286] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.688558] sector=1446459088 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.688563] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.747769] sector=1446463184 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.747774] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.787832] sector=1446467184 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.787837] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.827817] sector=1446471280 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.827822] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:10 MediaStore kernel: [ 453.873546] sector=1446475376 i=0 00000000 01000000 00000000 0 Feb 19 23:48:10 MediaStore kernel: [ 453.873551] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:11 MediaStore kernel: [ 454.917479] sector=1446479472 i=0 00000000 01000000 00000000 0 Feb 19 23:48:11 MediaStore kernel: [ 454.917485] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:11 MediaStore kernel: [ 454.957568] sector=1446483560 i=0 00000000 01000000 00000000 0 Feb 19 23:48:11 MediaStore kernel: [ 454.957573] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:11 MediaStore kernel: [ 454.997593] sector=1446487656 i=0 00000000 01000000 00000000 0 Feb 19 23:48:11 MediaStore kernel: [ 454.997598] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:11 MediaStore kernel: [ 455.037586] sector=1446491752 i=0 00000000 01000000 00000000 0 Feb 19 23:48:11 MediaStore kernel: [ 455.037591] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.077765] sector=1446495848 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.077770] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.117966] sector=1446499944 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.117971] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.157763] sector=1446504040 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.157768] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.192301] sector=1446508136 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.192306] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.237580] sector=1446512240 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.237585] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.277568] sector=1446516232 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.277573] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.317550] sector=1446520328 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.317555] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:12 MediaStore kernel: [ 455.367538] sector=1446524424 i=0 00000000 01000000 00000000 0 Feb 19 23:48:12 MediaStore kernel: [ 455.367543] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.417153] sector=1446528520 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.417159] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.457262] sector=1446532512 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.457267] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.497276] sector=1446536608 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.497281] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.537452] sector=1446540704 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.537458] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.577618] sector=1446544800 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.577623] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.617722] sector=1446548896 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.617727] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.657705] sector=1446552992 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.657710] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.697251] sector=1446557088 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.697255] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.757232] sector=1446561184 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.757236] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.797242] sector=1446565184 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.797247] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.837146] sector=1446569280 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.837151] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:13 MediaStore kernel: [ 456.877204] sector=1446573376 i=0 00000000 01000000 00000000 0 Feb 19 23:48:13 MediaStore kernel: [ 456.877209] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:14 MediaStore kernel: [ 457.916879] sector=1446577472 i=0 00000000 01000000 00000000 0 Feb 19 23:48:14 MediaStore kernel: [ 457.916884] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:14 MediaStore kernel: [ 457.956993] sector=1446581520 i=0 00000000 01000000 00000000 0 Feb 19 23:48:14 MediaStore kernel: [ 457.956997] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:14 MediaStore kernel: [ 457.996971] sector=1446585616 i=0 00000000 01000000 00000000 0 Feb 19 23:48:14 MediaStore kernel: [ 457.996976] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:14 MediaStore kernel: [ 458.037415] sector=1446589712 i=0 00000000 01000000 00000000 0 Feb 19 23:48:14 MediaStore kernel: [ 458.037420] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.077221] sector=1446593808 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.077226] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.117231] sector=1446597904 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.117236] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.157193] sector=1446602000 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.157198] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.196977] sector=1446606096 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.196981] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.245603] sector=1446610192 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.245609] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.287860] sector=1446614192 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.287865] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.327874] sector=1446618288 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.327879] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:15 MediaStore kernel: [ 458.367770] sector=1446622384 i=0 00000000 01000000 00000000 0 Feb 19 23:48:15 MediaStore kernel: [ 458.367775] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.393183] sector=1446626480 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.393189] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.437522] sector=1446630576 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.437527] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.477583] sector=1446634672 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.477588] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.517553] sector=1446638768 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.517558] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.558435] sector=1446642864 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.558440] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.598724] sector=1446646960 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.598729] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.638174] sector=1446651056 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.638179] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.678289] sector=1446655152 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.678295] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.735471] sector=1446659248 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.735477] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.777605] sector=1446663240 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.777610] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.817594] sector=1446667336 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.817599] md: bug in file drivers/md/unraid.c, line 300 Feb 19 23:48:16 MediaStore kernel: [ 459.857614] sector=1446671432 i=0 00000000 01000000 00000000 0 Feb 19 23:48:16 MediaStore kernel: [ 459.857619] md: bug in file drivers/md/unraid.c, line 300 Does that help ? I just kept the bottom of the log.
February 22, 200818 yr What is the history of this motherboard - that is, have you used it successfully in the past with Windows? Everything is pointing to bad h/w. What power supply? Did you try running memtest for a few passes?
Archived
This topic is now archived and is closed to further replies.