TheMantis

After upgrade to beta 14 from beta 12 I'm getting a missing disk after every reboot. The same thing happened with beta 13. The syslog seems (it's all Swahili to me) to indicate that when booting the max disk limit is getting reached before the last disk is mounted. If I move the original missing disk to a different SATA port then that disk will be found and a different disk will be missing (disks detected in different sequence/order?). Changing back to beta 12 brings the missing disk back immediately. Syslog attached. syslog_beta_14.zip

Thanks Joe. I'll contact Tom once I get home from work today.

Yesterday I had to rebuild a failed drive. Nothing unusual happened during this process, everything worked as it was supposed to. Now 50% of my drives are showing as unformatted (no blue dots though). The syslog is showing all sorts of REISERFS warnings like this: REISERFS warning (device md22): sh-2021 reiserfs_fill_super: can not find reiserfs on md22 Jul 23 06:40:47 Tower emhttp: shcmd (117): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md23 /mnt/disk23 |& logger Jul 23 06:40:47 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md23, Jul 23 06:40:47 Tower logger: missing codepage or helper program, or other error Jul 23 06:40:47 Tower logger: In some cases useful info is found in syslog - try Jul 23 06:40:47 Tower logger: dmesg | tail or so I've followed the instructions on this page: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems and am told that no superblock is found and to run with the --rebuild-sb option. Obviously this is pretty drastic so I'm waiting on some advice. I also checked the USB drive and found all sorts of errors and missing files. Using a backup I made that good again but the situation remains the same on the server. I've got no idea what happened or how to fix it. At this stage I've done nothing other than a reiserfsck check (it wouldn't run) on a drive and repair the USB drive. log.zip

I'm having some trouble installing unMENU. I've followed the installation instructions and have unziped the install file into /boot/unmenu. When I then attempt to run the installer nothing downloads and after a few minutes I get the following: "Unable to download release list from http://unraid-unmenu.googlecode/svn/trunk/release_list" I'm currently running an older version of SimpleFeatures because I couldn't get the latest version of that to install either. I do have an internet connection on the server as I can ping various addresses with success. UnRaid version is the latest ver 5RC. What the heck am I doing wrong?

The trick, of course, is to be very well versed in those customs rules you noted. When we lived in Europe, my mother-in-law had Sears send some Christmas gifts to our local address (a mistake since we had an APO address that would have totally bypassed customs). Sears did NOT handle the shipment correctly -- there's a box on the customs form noting "Gift, of no commercial value" that's supposed to be checked for gifts. The result: For a box containing ~ $200 worth of gifts, it cost us about $170 in customs fees. If that box had been checked, it would have cost nothing. [The even-more-frustrating part of that whole episode was the Sears had charged my mother-in-law a $25 "customs handling fee", which they said was for their "expertise" in handling overseas shipments.] That episode was ~ 20 years ago, but I definitely learned a lesson about being sure you KNOW the rules when making overseas shipments !! Never underestimate the stubbornness of bureaucracy. The NZ threshold is only $400 but go one cent past it and you can kiss goodbye to nearly $100. I take it that you have an association with the US military, I've been lucky enough to have an APO address in the past - very worthwhile.

Now that there are a couple of freight forwarding operations functioning in the US I find I hardly buy anything locally anymore. Apart from most of my 2TB drives almost all of my system has been brought from Amazon or other US based online stores. As I'm sure your finding, the problem in NZ is twofold; firstly the range of products is severely limited, secondly, what you can get is often very expensive. The only thing to watch is keeping under the customs import threshold, do that and you'll save enough money to get bigger and better components. So far I've had nothing brought from overseas fail.

Currently I've got around 1000 Blu Ray ISOs, 200 DVDs, photos, backups, TV series, and just general data.

Yes they are. On the PSU side are 2 x 6 sata power cables (16AWG cable), on the main side is 1 x 4 sata power cable (18AWG) and 2 x bog standard Corsair IDE power cables. I hate the IDE cables with a passion and will probably make some custom cables one day. Bear in mind the only custom cables I've ever made are on this PSU and the previous Corsair HX650 PSU. To build those custom power rails, did you follow one of the basic how-to videos on youtube? I'm fortunate enough to be an electrical engineer so I already had the necessary basic skills and tools. I did have to source the components and crimp tool from various international sources as they just weren't economically available in New Zealand.

Yes they are. On the PSU side are 2 x 6 sata power cables (16AWG cable), on the main side is 1 x 4 sata power cable (18AWG) and 2 x bog standard Corsair IDE power cables. I hate the IDE cables with a passion and will probably make some custom cables one day. Bear in mind the only custom cables I've ever made are on this PSU and the previous Corsair HX650 PSU.

Around 22 hours, I don't think I've done a full parity check since I added the 4TB drives over the last few weeks. The parity checks are running pretty slow since I added the AOC-SAS2LP-MV8 card though. Parity checks used to run at 75-80MB/s, now I'm lucky to get 55MB/s. I used to run more drives off the motherboard before I got the AOC-SAS2LP-MV8 so maybe I'm saturating the PCI-E bus during a parity check. Disk rebuilds are running at the same 55MB/s. Once the 2TB drives are finished the speed moves up to close to 95-100MB/s.

Amount of storage in this system: 54TB Case: Caselabs M8 PSU: Corsair AX850 Motherboard: Supermicro X8SIL CPU: Intel i3-550 RAM: 2x2GB Micron 1333Mhz DDR3 Controller Cards: 2 x Supermicro AOC-SASLP-MV8, 1 x Supermicro AOC-SAS2LP-MV8 Hard Drives: 3 x Seagate ST4000DM000, 2 x Seagate ST3000DM001, 4 x Seagate T32000542AS, 2 x Seagate ST2000DM001, 1 x Seagate ST2000DL003, 9 x Western Digital WDC WD20EARS, 2 x Western Digital WDC WD20EARX, 2 x Western Digital WDC WD30EFRX Primary use is storage of media. Secondary use is storage of backups for other computers.

Thanks for your help gents. I followed your instructions and everything is working great now. Parity is upgraded and I'm now adding the old parity drive back in to the array.

I do have a copy of the entire USB stick fortunately. I'll copy the required file/s back and see how it goes. I take it that the vast majority of parity is actually good but the entire parity disk is compromised due to the errors from Disk 19 corrupting the parity calculations. The parity sync has finished and Disk 19 is now red-balled. On reboot it isn't even detected so either it's knackered or I need to check the sata/power cables. Incidently, I did install a new AOC-SAS2LP-MV8 last night and this is one of the disks that I had my greasy little fingers all over. Thanks for your advice.

I'm in the process of upgrading the parity drive in my system and one of the data drives (#19) started performing the click of death and after about 5 minutes dropped out of the array. Once it had dropped out numerous errors were reported. The parity sync was running at around 49.7% which given the size of the failed drive (2TB) and the free space on it implies that it was not actually reading any data from that drive. The parity sync is now happily continuing. A full parity check (with error correction) was done four days ago with no errors. Will I be able to replace the failed drive once the parity sync is finished, or will I need to put the old parity drive back in then replace the failed drive before upgrading the parity drive again? As the attached image shows, the failed drive hasn't red-balled. I'm not particularly worried - just curious really.

And a system log : 5_0_beta6_log.pdf

I also have a number of disks indicated as being wrong. I suspect that they all have HPA's. Everything is working great in 4.7. It's no big drama at the moment. Here's a screen capture: