Jump to content

cofin

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cofin

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. The option ROM is a setting in the motherboard BIOS. Depending on what mobo you have, it could be in different places. Just poke around and see if you see something like that. I don't think that it will make a huge difference though. You might want to try setting this at the shell and see if it makes a difference: sysctl vm.highmem_is_dirtyable=1 This made an impact in my performance.
  2. Sure, no problem at all. Here it is: http://lime-technology.com/forum/index.php?topic=12767.msg121131#msg121131
  3. Be sure to follow the flashing guides in the other forum. I was able to flash all 3 with the other bios in about 30 minutes.
  4. I bought mine used on ebay. They were extremely expensive new. I got 3 for less than that price you mentioned.
  5. I believe that the kernel support for these cards (or using multiples of these cards) is flaky. I swapped to 3 M1015 cards and all of my issues were instantly resolved. Faster writes and no parity rebuilding issues.
  6. I'm on the latest 5 rc (rc8a) and the output of 'which smbd' points to /usr/sbin/smbd. Perhaps I am missing something, but shouldn't the pgrep line be adjusted for the 5.* smbd? Linux 3.4.11-unRAID. root@SATURN:~# which smbd /usr/sbin/smbd
  7. Just to give an update on this: I disabled all option ROMs on PCI-X cards in the BIOS. Disabled all disk spindowns in unraid. And attempted parity build again. I've gotten further than ever, and it's been running for about 15 hours. If it all goes well, it should complete successfully in ~80 minutes.
  8. If you know what device his the swap partition, you would just swap the commands out to point to the correct device. If you'd like to make it dynamic, you would just grep your device out of the 'cat /proc/partitions' command you listed. You could use something like this in the swap_start piece (note that this hasn't been tested) if [ -d /dev/sdg ]; then # USB Swap drive is ready mkswap -f /dev/sdg swapon /dev/sdg fi in swap_stop, try something like this if [ -d /dev/sdg ]; then # USB drive exists swapoff /dev/sdg fi This assumes that your sdg drive is always that USB stick. It doesn't check to make sure that it is, so it could be dangerous. I am about to go on the road for a few hours, but when i get some back, I'll take a few minutes to see if we can make the script a bit more dynamic.
  9. I did that this morning. Reseated all add-on cards and SAS/power cables. Any other ideas?
  10. Thanks, for helping with this. I've attached the SMART report to my original posting.
  11. Here is a quick and dirty plugin that I wrap to enable/disable the swap file I have on my cache drive. Perhaps some of you guys will find it usually, but most importantly, perhaps we can improve upon it. It's pretty static right now... It creates (if the file doesn't already exists) a 16GB swap file on /mnt/cache, sets permissions, then mounts it. On shutdown, it automatically disables it. Comments and criticisms certainly appreciated. swapfile.plg.zip
  12. Sure thing, here are the current specs: I3 2100 Supermicro MBD-X9SCM-F-O 4 x KVR1333D3E9S/4G RAM 3 x AOC-SAS2LP-MV8 Corsair 750AX PSU 24 x Western Digital WD30EZRX Norco RPC-4224 Chassis All temps in the chassis are within normal range and all other drives appear to function normally.
  13. Hey all, Long time user and lurker here. I have had several unraid builds, and I finally decided to build a monster server with Norco 24 bay chassis. It is stacked out with 3TB drives and with the exception of parity, is functioning perfectly. I am on 5.0 rc8a, and I have tried multiple 3tb drives (I originally thought one of the 24 drives I purchased was bad) and I get the exact same number of errors (384) when attempting to sync to the parity disc. I've never had these types of issues in the past, so I'm a bit stumped on how to resolve. I am handy with the command line and use linux on a daily basis, so hopefully I'll be able to follow any suggestions. I've attached my syslog file, and any help would be greatly appreciated. EDIT: I reseated all SAS cables and swapped one of the SAS2LP cards into a free PCIX slot. Rebuilt parity in maintenance mode and it failed again at same spot. I've attached the output of the SMART report for the drive. EDIT: After disabling the PCI-E option ROMS and the drive spindowns, I was able to successfully sync parity. Hopefully this has resolved my isses. syslog.zip smartreport.txt