Chem13

Thanks for the help and advice....everything is ordered.

One other quick question...will I need any special cables to take advantage of the onboard SATA ports? Thanks.

Sorry I'm just now getting back to my computer...real life has been kicking me in the butt.... Thanks for the input and suggestions...I like the idea of the faster processor...I'm changing to it now. I've never run a board with IPMI....looking forward to it. Thanks again.

My old system took a lightning strike so I'm looking to upgrade and would like some advice please... I am looking to start using VMs and Dockers (just started using Dockers on my older system running 6.0 beta 14b) I'm running 13 2TB hard drives with a 2TB parity and a 2TB cache drive I have the NORCO 4220 case and a 750 watt power supply which was not damaged and I'm keeping in service Here is what I'm looking at upgrading to: 1. SUPERMICRO MBD-X10SL7-F-O uATX Server Motherboard LGA 1150 Intel C222 DDR3 1600 http://www.newegg.com/Product/Product.aspx?Item=N82E16813182821 2. Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1600 (PC3 12800) Server Memory Model CT2KIT102472BD160B http://www.newegg.com/Product/Product.aspx?Item=N82E16820148770 3. Intel Xeon E3-1231V3 Haswell 3.4GHz 8MB L3 Cache LGA 1150 80W BX80646E31231V3 Server Processor http://www.newegg.com/Product/Product.aspx?Item=N82E16819117316 I have older raid cards I was thinking of upgrading. I currently have two (2) IBM ServeRAID BR10 cards... Any suggestions on ServeRAID cards to use with this new motherboard? Thanks in advance for any suggestions or advice.

Sorry for the delay in responding...I got sent out of town and am just now getting back. --I replaced the SATA Cable --Trusted the Array --Everything is showing green and working fine --Going to rebuild parity next, and upgrade to new version of Unraid as well as install a new 2T WD drive Thanks again for all the help. Your comments and suggestions were dead on correct. The array is now back up and running showing all green. It's like having one of your kids get sick and watching them slowly get well. Next thing I plan to do (after another out of town trip) is rebuild parity and then install that extra 2TB WD EARS drive I bought in case drive 9 was bad. I have heard about the issues with the larger drives and I currently have Three (3) larger 2TB drives in my system now including the parity drive. They have been in place and working fine for over 8 months now (I didn't mess with the jumpers on the drives). I plan on updating to the new version of unraid and then install the last 2TB drive I have. I had not planned on messing with the existing 3 larger drives that seem to be working fine. If I"m doing this wrong please let me know. Otherwise this weekend I will do the upgrade when I get home. Thanks again for all the help getting me back up and running with no loss. It's kinda amazing how much you all were able to divine and diagnose from those syslogs. Have a good one and for all you up north...stay warm.

--Still showing a problem with Disk 9 --Shows Red Dot by name and on unmenu shows DISK_DSBL --Disk 6 now shows to be working fine --I can now access BOTH disks and all files seem to be there --Before I do anything else, I'm moving the files off disk 9 to a different disk --a new syslog is included here I got the card in from Newegg and installed and immediately it showed both disk again and the array booted up. Disk 6 shows all green and shows no problems now. Disk 9 still has the red dot and shows DISK_DSBL on unmenu. I have not run Reisfsdk because before doing anything else I am moving the files from disk 9 since its now readable. Tomorrow I plan to go replace the sata cable on disk 9 and move that drive to one of the open sata ports on the new card I just got from newegg and see if that fixes the problem. Thanks again for the help. No matter what else I find, I'm at least back to the point of being able to save my data before moving forward. Once this problem is fixed, I will move to the new version of unraid since I am still running four 2 TB drives which so far seem to be working with no issues. I will update tomorrow once I open up my system. It will take all nite and most of tomorrow to finish moving files off Disk 9. syslog-2011-01-25.txt

Just an update...I do think you are correct regarding a dead controller card. I ordered a replacement card off newegg with overnight delivery to arrive Tuesday. I live in a very small town that is proud of its 3 Walmarts. I spent the day looking for a replacement card with no luck. It was almost funny watching the look on the sales rep face when I asked if they carried an internal SATA II Controller card...they would walk around to the printers...then the video cards...before asking what the card is used for. Update on Tuesday. Thanks again for the help.

-Came home from work to find 2 drives showing unformatted -ran reisfsck –check to find it say hardware problem with unreadable sectors -reisfsck recommends replacing drives due to hardware problem -Drive 6 and 9 originally could be accessed with missing files, but now totally unaccessable -I have a Hatachi 2TB in closet and WD 2TB on order to replace the bad drives -Was reading the forums before doing anything and came across posts about problems with 2TB Drives -I’m still reading the threads on large drive issues and realized I need help to not make the problem worst. So my main question is how best should I proceed to replace these two damaged drives (disk 6 and disk 9) in my system? A long term question is how best to deal with the 2TB drives already in my system working just fine? Thanks in Advance. Any and all help is greatly appreciated. I don’t read the forums as much as I should, mainly because my system runs so smoothly. I had no idea there was an issue with some larger Hard Drives until now that I am having an issue. I came home from work Friday to find my server unresponsive. I powered down and restarted to find Drives 6 and 9 showing as unformatted. I used putty to telnet into my system and run reisfsck –check command which returned information that both drives had possible hardware problems with unreadable sectors. Disk 9 has a red dot by it and Disk 6 has a green dot by it on the disk status page. Now neither drive is loading when I restart the array. On unmenu Disk 9 has DISK_DSBL_NP and Disk 6 has DISK_NP_MISSING. Both disks are Samsung HD154UI 1.5 TB drives purchased and installed about 1 year ago. When I reboot the array will not start as it shows both drives as missing. I didn’t have a power outage as my main computer was still up and running when I got home and my server is on a UPS. I do find it unusual for 2 of the exact same model hard drives to fail at the same time, but for now that is what the data is showing. I have opened up the system and reseated all my drives and sata connections and reseated the memory and expansion cards. I also took the flash drive and scanned it for errors and found none. I am looking to buy one Western Digital 2TB (WE20EARS) drive and I already have one HITACHI HDS722020ALA330 / 0F10311 Deskstar 7K2000 2TB which I plan to use to to replace the 2 bad identified drives. I am running low on free disk space at this time, but I do have room to move the contents of the 2 bad drives to safe locations. However, at this time most of the files are not showing up on either drive to move. I will also include 2 syslogs. The first log was early in the problem when I was able to boot and still access some part of the bad 2 drives. The 2nd syslog is most current and shows that I can’t boot at all as both bad drives show as missing. Since I just became aware of an issue with some larger hard drives, I have not had a chance to read all the threads. I’m hoping for some suggestions on how best to proceed to avoid problems in the future. Below I have provided some information about my system and the drives: Supermicro MBD-C2SEE-O 775 Intel G43 Motherboard 4 Gig OCZ Memory Intel E5200 Wolfdale 2.5GHz Dual Core Processor 1 Thermalake 550W Powersupply 1Thermalake 650W Powersupply Parity – Hitachi HDS 72202 2TB Disk 1 – Hitachi HDS 721075KLA330 Disk 2 – Hitachi HDS 721075KLA330 Disk 3 – Hitachi HDS 72202 2TB Disk 4 – Hitachi HDS 721075KLA330 Disk 5 – Hitachi HDS 721075KLA330 Disk 6 -- Samsung HD154UI Disk 7 – Samsung HD 103SI Disk 8 – Seagate ST32000542AS 2TB Disk 9 -- Samsung HD154UI Disk 10 – Samsung HD753Lj Disk 11 – Samsung HD 103SI syslog-2011-01-22_last.txt

Thanks for all the help and advice! I just wanted to pop back on to say thank you. I appreciate all the people that take time out of their day to offer help and advice. As an update, I'm up and running and back to normal. My final issue, the drive that was showing as unformated...Bjp99 was dead on...I had mixed the parity and drive 1 up when I assigned them (they are identical drives and only differ by the last digit)...it looks all those years at Texas A&M were wasted. Thanks again.

Follow-up question please. -Tried a new flash drive in multiple USB ports without any success -installed new motherboard, CPU, and Memory -System now seems to boot fine -Parity showing as invalid (as expected) -Disk 1 showing as unformated (unexpected) -all other 8 disks seem fine and fully accessable One of the nine hard drives is now showing as unformatted that previously had no issues. Since the parity still shows as invalid, do I have any options other than to count the data as lost and reformat? I have tried rebooting several times. Would using the "clear statistics" button have any effect? would relocating the drive from disk 1 to a previously unused designation such as disk 10 have any effect? Just as an update, I obtained and set up a new flash drive with the help of Tom and that had no effect on the problems. So I ordered a the Supermicro motherboard, E5300 CPU, and 2 gig of memory. When I booted up I still got the parity invalid (as expected) but the disk 1 showing now as unformated. I just now installed the new hardware. I'm going to let it run all night to make sure there are no lock-ups or other problems. I have stopped the parity check until I investigate the unformated drive issue further. Thanks again for any advice.

I forgot to mention that I did go into the bios and change the DRAM settings to manual and used the voltage and other recommended settings as part of the earlier tests.

It looks like I'm going to have to use my AIG retention bonus and some of the goverment bailout money and buy a new motherboard, CPU, and memory. --I'm still unable to complete a memory test. It hangs up at almost the exact same spot each time both with the old memory and the newly purchased memory. 1. I have run chkdsk on the flash drive. If found and repaired errors. I then reloaded a fresh version of 4.4.2 along with a fresh memtest with no luck. 2. Since my system has two power supplies I tried each one indpendently with no success going on the assumption that both power supplies going bad at the same time was unlikely. 3. I disconnected all hard drives and ran just the motherboard and memory with no success. 4. As mentioned earlier, I purchased new memory and the memtest still freezes at the exact same spot..about 7% in. 5. The last thing i can try is my best friend has the same server, I was going to borrow his working flash drive and see if I can run a successful memtest with it. I did boot my main computer up with my flash drive and ran a complete and successful memtest on that computer to verify that the flash drive was capable of doing a memtest. Barring all that, it is looking like it is time to upgrade the motherboard. What motherboard would be recommened? The P5b-VM is discontinued at newegg. I have always been a fan of ASUS motherboards, but I was considering the one currently being used in Unraid systems...Supermicro C2SEE motherboard? I will prbably change out the remaining IDE drives when I do this also...get the pain over with all at once.

The parity test is still going fine at 42% as I get up and head to work...I will let it run. 1. I agree, the failed memory test was not a good sign. I don't overclock. I am using Corsair Valueselect 184-Pin DDR SDRAM DDR400 (PC3200) memory. The motherboard is set to "auto" for all the memory settings. Since the memory and the settings have worked without issue for a number of years, I tend to think that it may have just gone bad. let me switch the memory between slots and reseat each chip and try the memory test again. I can see the memory easily accounting for the random lock-ups, but would that explain the system running fine with all files accessable except an inablity to keep a valid parity? or am I back to the possiblity of mulitple issues? I will get the memory test working today one way or the other and update here again. Thanks for the help and advice.

To start, I want to say thanks for the help and suggestions. Here is what I have found so far: 1. Ran Smartctl on all drives and parity and didn't see any errors. The temperature was up a little, but that was because I had the case open and improper air flow. 2. The flash drive seems to be fine in that I can access it, read, and write to it without difficulty 3. The memtest won't complete. I originally got "invalid or corrupt kernel Image". I reloaded 4.42 onto the flash drive and ran the memtest. It hangs everytime about the same location. Pass: 7% Test: 21% Test: #3 [moving in version, 8-bit patterns] Testing: 0K-16M 1023 relocated Pattern: bfbfbfbf walltime: 0:01:21 Cash: 1023M RsvdMem: 864K MemMap: e820-Std Cache: on ECC: off Test: Std Pass: 0 Errors: 0 Ecc Errors: 4. I notice on reboots I get this message: remounting root file-system read-only mount: can't find /in/etc/fstab or /etc/mtab 5. I am still able to access the data on each of the 9 drives. If finds the drives after each reboot. However, each time it shows parity as invalid. I can run a parity check and it completes without issues and shows green for all drives. However, when I reboot, it comes back up with each drive accessable, but parity invalid. 6. I have attached each of some of the smartctl and a fresh syslog. Each smartctl showed similar information and each said "Pass". I am running a fresh parity check tonight and it will finish sometime around lunch. I will post if anything different happens. 7. I only had the system lock up one time in about 20 reboots and testing. That issue seems to have diminished in scope, however, there is no change regarding the parity issue.

SYMPTIONS: - System consistently shows parity invalid even after running successful parity check. - Random system lock-up requiring hard reboot. - Periodically will not show all drives present. Will list the drive and show “no device” DISCUSSION: - I can’t seem to tie the system lock-up to any one activity…they seems to happen more frequently during parity checks - Lock-up requires a hard reboot by powering off then back on - Even after a successful parity check, I get invalid parity on the next reboot. - I have check the file system on each drive and found no errors - Files on the drives appear to be unaffected and accessable Help Please: The lime sever has been the best investment I have made ever since my best friend told me about the system. This is the first problem I have had in many years of operation. My system: It is about 3-4 years old. Running software version 4.4.2 2 Thermalake 550 watt power supplies Asus P4P800 Deluxe Mother board Intel P4 2.4 GHz CPU with retail cooler 2 Gig Ram 1 Promise IDE card brand and model recommened on Lime site 1 Promise SATA card brand and model recommended on Lime site Coolmaster large tower case 10 hard drives ranging in size from 750 gigs to 400 gigs Parity: SAMSUNG HD753LJ Size: 750 Gig SATA Disk 1: Hitachi HDS721075KLA330 Size: 750 Gig SATA Disk 2: Hitachi HDS721075KLA330 Size: 750 Gig SATA Disk 3: ST3400633A 3NF1QWPN Size: 400 Gig IDE Disk 4: Hitachi HDS721075KLA330 Size: 750 gig SATA Disk 5: Hitachi HDS721075KLA330 Size: 750 gig SATA Disk 6: MAXTOR STM3500630A 5QG0JAF3 Size: 500 Gig IDE Disk 7: ST3400632A 5NF19PLB Size: 400 Gig IDE Disk 8: ST3500630AS Size: 500 Gig IDE Disk 9: HDS725050KLAT80 KRVA45ZAH9EZYF Size: 500 Gig IDE Note: The IDE drives are using round cables (I didn’t realize that was not recommended until I started researching my issues in the forums. I have been using those cables for 4 years without an issue until now. I am mentioning it now to be thorough and cover all possibilities I am in the process of changing out all the IDE drives. I started with 9 IDE drives and as funds become available, I replace them with SATA. I’m looking at a coupld of 1.5 or 2.0 TB drives as the next upgreade with one of them becoming the new parity and replacing the 400 Gig IDE (Disk 3) and moving the current parity to replace drive 7 (400 Gig IDE). Sympton: - System consistently shows parity invalid even after running successful parity check. - Random system lock-up requiring hard reboot. - Periodically will not show all drives present. Will list the drive and show “no device” Discussion: I suspect a hardware issue, possibly the promise controller card or one of the hard drives. The system randomly locks up and requires a hard reboot through the computer case power switch. All access through the GUI or by logging onto the system is blocked when this happens. I can’t seem to tie the lock-up to any particular activity. It happens when I’m moving files from one drive to another. It also happens when I’m just running a parity check. The lock up seems to happen more frequently when I’m running a parity check. At least for now, the files seem to be present and unaffected on the hard drives. I am still able to access them while the parity check is in progress or if I cancel the check and just examine the system while parity shows the red dot (invalid). When I do a hard reboot like this it will start up and immediately proceed into a parity check. Initially I was noticing that only some of the drives were showing on the GUI (drives 1-4) and the other drives showed as “no device”. I opened the system case and reseated all the drives and cables and controller cards and at least for the last 4 reboots this particular issue has disappeared. All drives are showing as present. I did notice that until I checked all the cards and cables, I was getting this error as the final command on the boot-up screen, “/dev/md*: no such file or directory”. After checking all the cables and cards, this error no longer is present and I’m not noticing any error messages on the boot-up screen, but am still having the lock-up and parity problems. With each hard reboot, it shows the party as being invalid and starts a parity check. I also am getting an invalid parity with I do a proper shut down through the GUI (stop all drives, and click reboot). I have let it run a full parity check (took about 8 hours) and got the green dot by the parity dive at the completion. I then did a normal reboot from the GUI and it came up with a red dot by the parity drive saying the parity was invalid. Sometimes I can run the parity check with no issues and sometimes the system totally freezes in the middle of the parity check requiring the hard reboot discussed above. I have check the file system on each of the 9 hard drives and it found no errors. I used: Samba stop Umount /dev/md1 Reiserfsck /dev/md1 Mount /dev/md1 /mnt/disk1 /usr/sbin/smbd –D /usr/sbin/nmbd -D There were no errors found and it didn’t ask me to run the –fix-fixable/dev/md1 or rebuild-tree.