Dephcon

Mem: 3942540k total

technically a 64bit version of unraid would have fixed this issue as tom suspected. I'm glad people aren't going to have to wait for that. I agree that 5.0final should limit the ram to 4GB for everyone.

Oh don't worry, I'm going to be all over it.... though at the time same time the wife is happy that the "tv" works again. I wonder if I can monitor the syslog with nagios/cmk...

I agree. Tom, I know you're not an update whore, but a bi-weekly status update would be very welcome. Even if all it says is "still grinding away on the ________ bug/issue" I'm not affect by this issue but i think moving to a 64bit kernel is probably a good thing to do. Either way might as well push 5.0 out and shut everyone up and then us bleeding edge types (read: awesome) can help you test 5.1 x64

I just upgraded to RC10 so I guess I'll leave it at that for now. If the issue re-surfaces I'll start a new thread. Thanks for everyone's help.

Couldn't hurt to run another parity check with RC10 and you'll want to pre-clear the 3TB 3 times to ensure it's good. As i remember to upgrade the parity disk you just turn off the array, power down, swap the drives then boot back up. It'll whine that the parity disk is missing and just select the new one and rebuild parity onto the new drive.

http://lime-technology.com/wiki/index.php/Console#To_cleanly_Stop_the_array_from_the_command_line I've used this many times on some of the older RCs when I lost webui/telnet

were you not able to manually stop the array from CLI?

Update: All the disks checked out fine with zero errors and I ran memtest for 6 hours without issue. I updated the BIOS on my motherboard (was quite old), reset all the settings to default, then disabled all the stuff I don't need (audio,serial, firewire, etc). I installed my LSI 3081E-R and I now have disks 1-4 on the MV8, disks 5-8 on the LSI and disk9, cache and parity on the on-board controller. One thing that may have been an issue was I had the server on the carpet (not plush at all) with a bottom mount PSU, I noticed the exhaust air was "warm" so now it's on my desk. So I'm going to do a parity check and hopefully if nothing bad happens I will be rebuilding disk 8 as I RMA'd because I didn't like the seek noise it made. I already have the advance ship disk from WD pre-cleared and I need to ship disk 8 back ASAP so I don't get charged $150. Hopefully if I have another failure it will be limited to the MV8... I'm also planning to rebuild either 3, 4 or 6 onto a new 3TD Red and then copy the data on the other two to other disks. They're 1.5TB seagates that I've had forever and are on multiple RMA... I think one is the original purchased drive. Actually disk 8 was just recently rebuilt from a 4th 1.5 seagate that was on it's 3rd re-certified replacement. I've just had enough with these awful drives.

Sounds good. I ran an 8 hour memtest when I build this system, but shit happens I guess. I have a brand new HX650 Pro PSU that I can try if the memtest comes back ok. I also flashed my LSI 3081E-R to IT firmware this afternoon so I can also try with half the drives on that and half on my MV8 if need be, apparently they're similar in performance (the LSI might be slightly better). I'll report back with my findings tomorrow.

It's currently doing a parity check due to the hand shutdown. Shall I let it continue or just cancel and move onto memetest and checking the disks' file systems? Thanks,

Just flashed my LSI SAS3083 card to the latest IT firmware.

Works fine on my test box.

My only beef with those supermicro cards is they only have 2 PCIe 8x slots. This sucks if you want multiple SAS2 HBAs and maybe a PCIe ssd or something crazy.

intel. here's an example of one of their pci-e cards: http://www.ncix.com/products/?sku=37926&vpn=EXPI9301CTBLK&manufacture=Intel

Update: When I woke up the webgui service and my telnet connections were down. Plugged the monitor in and the console was spamming this style of message (i think so, it was too fast to read): an 12 00:22:25 Vault13 kernel: REISERFS error (device md7): vs-13070 red trying to find stat data of [2429 2467 0x0 SD] Jan 12 00:22:25 Vault13 kernel: REISERFS error (device md7): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [2429 2467 0x0 SD] I had to do a hard shutdown I have an untested and unverified LSI SAS3081E-R collecting dust that I coudl flash to IT mode. Could it be that my MV8 is bad? Would moving half of the drives from the MV8 to this LSI be safe and possibly very informative? Should I stay at RC8a until this is resolved?

Intel PCI-E NICs are pretty cheap

It's a seasonic built "XFX 750W PRO750W XXX Edition Single Rail". My UPS is an APC back-ups RS 1500, not sure how it conditions the power. Our power isn't as "dirty" as i may have let on, but it's an apartment and we get the occasional blip.

Looks like the issue has occurred again... good thing the drives i'm currently pre-clearing are on the onboard sata ports. Syslog attached, drives 2-7,9 are connected to the MV8 the rest are on onboard. Thanks. syslog2.zip

Hey guys, So I've been running unraid for a couple years now on a i3 540 and it's been great. Recently I've been messing around with linux (ubuntu server) using VMware Workstation on my desktop (3570K). I want to set up databases and monitoring apps, etc but windows update restarts, overclocking instability and just messing around makes my desktop a poor location to host these. I want to build a new server to host ESXi 5.1, and possibly migrate my unraid server into a VM as well. On paper the new AMD FX-8350s look pretty sweet for a single socket solution...but in practice I know AMD has a lower IPC than Intel. Also gigabyte 990FXA-DS7 has some nice features including 2x16pci2.0, 2x8pcie2.0 and 6 SATA3 ports that support vmdirectpath. Any thoughts or suggestions on the intel side? Thanks!

When the lease time expires the server still does a DHCP request to your router to negotiate for a new address. It's not aware that your router is configured to always assign the same address. Setting a static IP for a server is always a good idea

I'm in the second run of pre-clearing a drive I have on advanced RMA from WD. I'll be upgrading once the 3rd run completes.

Well I told myself if it did it again I would remove all my add-ons and play ball, and it did at 8:30 this morning. Any objections to me keeping my apc and screen plugins on? We have dirty power and the UPS is a must and screen is handy as I need to pre-clear a couple drive I got an advanced RMA on.

I should also add that this is not the first time this has happened, I usually just stop the array and reboot to fix it as it interrupts the wife's TV time after work so quick fixes keep everyone sane. This has probably happened 4-6 times since I've been on rc8a.

Hello, I noticed this message in my telnet session when I got home from work: Message from syslogd@Vault13 at Sun Jan 6 17:29:54 2013 ... Vault13 kernel: Disabling IRQ #16 All the drives connected to my MV8 are green, spun up, but not reporting temps. I cannot open/copy any files from the drive shares on those disks. I'm running rc8a and my syslog is attached. Thanks. syslog.zip