boxtor

I think some sites lists the old specs. They released a newer version of this case. The old version can be seen here. http://www.xtremesystems.org/forums/showthread.php?202201-For-those-of-you-that-have-the-norco-RPC-4020-case-(WARNING-lots-of-images)

I'm surprised you went with the 4020. It lists supporting SATA I and II drives for the drive cages. I'm not sure if it matters.

Does this happen every time you do a parity check? It doesn't happen every time, but I do get a couple parity errors almost every time. It's been rare that I get 0 errors after running a parity check. Something is wrong with your server. Power or RAM would be my first concerns. When was the last time you ran a 24 hour memtest? My strangest problems have always been power supply related. The last time I ran a 24 hour memtest was about a year ago when I assembled the server. The 4 DIMMs are also getting old (~5 years IIRC). I should run a memtest. The power supply was new and kept under low load (~40W total power consumption for my server and it frequently enters hibernate).

SMART reports aren't related to parity, they are 2 very different things. While it's possible that a drive issue or a power issue could cause both, it would be rather coincidental to see both a SMART issue and a parity error at the same time. In addition (and not everyone will agree!), if you get parity errors, the odds are extremely high that it was NOT a data drive, but the parity drive that was wrong. It always has been that way, and even though both drive capacities and platter densities are increasing, I believe it will still be that way for some time to come. We do keep talking about bitrot and other causes, but by far, in my opinion, the main reason for a parity correction is an interrupted write. Data was written, but the parity write was interrupted, by power outage or crash or ... (so the data is correct, parity is not). User error is another (rare) possibility (writing to the drive in a way that is not parity protected), but again the data is correct, the parity is not. I do believe that bit rot is more than just a theoretical thing, but try looking for actual reports of proven bit rot among us. I'm sure they exist, but it is still very rare. If the coming dual parity implementation does happen to indicate the specific drive that has wrong bits, I am expecting it to indicate that it's one of the parity drives over 99% of the time, perhaps over 99.9% of the time. But that's just my opinion. And that's why I have never bothered with a non-correcting parity check, but I know not every one agrees. And I know I shouldn't touch off that discussion all over again! It sounded like the feature would support pin pointing which drive had the incorrect bits. It's good to know that the parity drives usually contain the wrong bit instead of the data drives.

Does this happen every time you do a parity check? It doesn't happen every time, but I do get a couple parity errors almost every time. It's been rare that I get 0 errors after running a parity check.

HUGE news guys, great momentum happening with unRAID. Thought, should this really be a 6.x point release? Why not 7.0 to help would be beta testers clearly know this is a completely new idea and beta. We'll give that some thought, we can then make it a paid upgrade as well. Or make it a Pro only feature! In my opinion, dual parity is not really that necessary. There have been very few times when two disks have failed at the same time or even during a rebuilt. And I would bet that most of those were in systems where the sysop has not been watching things and performing periodic parity checks. In those cases, dual parity would probably not prevented an issue because no action would be taken until after a third disk had failed. The biggest advantage to dual parity is that the exact disk with the issue can be quickly determined provided there is only a single failure point. If I can use dual parity to tell me which disk is problematic, I'd like to use it in the Plus version. It's annoying when I get 3 parity errors per parity check and the SMART reports for the drives indicate all is well.

I installed unmenu when I started using unRAID in an early 6.0 beta and it installed and worked fine. Now I don't really see a point to keeping it due to the new webGUI. How do I go about uninstalling unmenu?

I am using unRAID 6.0.1. The SMART status icon on my dashboard for my cache drive is a green thumbs up. However, it has the tool tip text "reallocated sectors". The SMART attributes don't list reallocated sectors. Does this tool tip text mean something else in this case or would this be an error? My device is an SSD (CORSAIR CMFSSD-128GBG2D). # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 9 Power On Hours 0x0032 092 092 000 Old age Always - 38514 12 Power Cycle Count 0x0032 099 099 000 Old age Always - 369 175 Program Fail Count Chip 0x0032 100 100 010 Old age Always - 0 176 Erase Fail Count Chip 0x0032 100 100 010 Old age Always - 0 177 Wear Leveling Count 0x0013 081 081 017 Pre-fail Always - 1123 178 Used Rsvd Blk Cnt Chip 0x0013 093 093 010 Pre-fail Always - 4 179 Used Rsvd Blk Cnt Tot 0x0013 099 099 010 Pre-fail Always - 19 180 Unused Rsvd Blk Cnt Tot 0x0013 099 099 010 Pre-fail Always - 3821 181 Program Fail Cnt Total 0x0032 100 100 010 Old age Always - 0 182 Erase Fail Count Total 0x0032 100 100 010 Old age Always - 0 183 Runtime Bad Block 0x0013 100 100 010 Pre-fail Always - 0 187 Reported Uncorrect 0x0032 100 100 000 Old age Always - 0 195 Hardware ECC Recovered 0x001a 200 200 000 Old age Always - 0 198 Offline Uncorrectable 0x0030 100 100 000 Old age Offline - 0 199 UDMA CRC Error Count 0x003e 253 253 000 Old age Always - 0 232 Available Reservd Space 0x0013 093 093 010 Pre-fail Always - 56 233 Media Wearout Indicator 0x0032 099 099 000 Old age Always - 20495166

Wouldn't you have to upgrade the parity drive first since it has to be greater than or equal the largest data drive?

Good to see you got it going OK. Do you think I should add more columns or are you using the NOTES as for everything else? I use the notes column for my purchase place, I haven't thought of any other info I really need at the moment. The only other thing I did think of was a interface tab, so I can put in which driver controller the drive is connected to. May really help troubleshooting if problems arise. A massive innovation would be the ability to customise the server layout more with some sort of block based building. I have sixteen drive bays in my system At the top a horizontal 5.25" Drive bay to 3.5" hot swappable bay Then all my other drives are vertical with three, 5 in 3 hot swappable bays. The ability to define that would be epic but I can see how that would be tricky. Maybe a USB port section so you can allocate which USB drive is plugged in where. But these are all just ideas.... There was a addin for Windows Home Server v1.0 Called WHS Disk Management. It supported custom case layouts. Users created wire lists for many different cases. Using the addon was clunky, but it was a cool concept.

I'm not sure if this would qualify as a defect. A docker image filename I used in 6.0-b12 is not valid in RC2. I upgraded from 6.0b12 to rc2. The docker file I used in b12 was /mnt/user/AppData/docker.img When attempting to recreate the docker image, neither the delete commands nor create commands did anything. When I tried copying in the same directory into the docker image text field (I logged in via SSH and copied the directory name into the clipboard), I saw the red text error message "Error: cannot specify user share (instead use cache, disk1, disk2, etc)." indicating something was wrong. After I changed the docker image to /mnt/cache/AppData/docker.img, everything worked fine. It would be nice if the Apply button would also trigger that error message to be displayed instead of silently doing nothing.

I use that board with a AMD 5350 for my pfSense firewall. Booting from USB is straight forward in the BIOS. The biggest problems I've had with it are 1) sleep has problems. I used PartedMagic on it (before the pfSense installation) to secure erase some SSDs. When I forced it go to sleep to unfreeze the drives, it wouldn't come back on. 2) Either the board or CPU had quality problems. I ended up RMA'ing it twice before I got a working combination that worked with both banks of RAM populated (8G total)

Has anyone created a docker container for unRAID for any version control system (svn, mercurial, RCS, etc...)?

I would like to see support for some encrypted container support in unRAID. Perhaps it could be added as a plugin or Dockerized application. Reason for wanting it: It would be nice to to have a simple way to create a single encrypted container of files in order to use a remote back up. The way I'd envision using this is 1) mount my container 2) update the files in the container (perhaps using rsync) 3) unmount the container 4) Backup the encrypted container to a remote site such as Dropbox

There is a Chinese brand with the same chipset that sells on ebay for about $100 for a 4 port card. I have a 2 port and 4 port version and they work well. I'm not sure how well they work in unRAID.

I installed the 64 bit Plex plug in using the plugin manager last night. It worked fine on unRAID 6.0b10.

Thanks for the help. I performed option 2 using rsync to migrate files. It was easier than I thought. Once I moved all data off the other drives (including cache) and verified that data only existed on drive 3 (removing the old folders on disk 1 made this easier to verify) all it required was stopping the array and then reformatting the drives. It seems like the migration part could be automated. Windows Home Server v1 had a similar feature where you could select to remove a drive and it would ensure that the files existed on a different disk. In this case I'm stopping short of removing the disk and allowing it to be reformatted.

I have 2 ReiserFS drives I would like to convert to XFS. At the moment I have 4x 4TB drives Drive File System Has data 1 Parity N/A 2 ReiserFS Yes 3 ReiserFS No 4 XFS No I would like to convert drive 3 (no data). To do this, do I 1.) Stop the array 2.) Switch the file system 3.) Start the array and format the disk Should I do a parity check before doing this conversion? Note: all 4GB of my really important data is backed up to a memory stick

I didn't go strictly low power, but power was a definite concern. Since this is my first unRAID build, I didn't know what to expect for performance or if I would end up using many plug ins. I went with a Core i3-4370 (54W TDP) and an Asus GRYPHON Z97 motherboard. I wish the motherboard had more than 6 SATA ports, but I'll add a HBA card later. The Apcups plug shows a load of 43.25W on my UPS. My server has 4x 4TB drives( all 4 spun up with one of them being pre-cleared) and a SSD cache drive, and a couple extra fans. The UPS also has a 2 routers and a switch running off it. While power was a concern, I also didn't want extremely poor performance. (The performance shock of going from a server with a RAID 5 array of 8x 2TB drives on a RocketRaid card in a server with an Core2 i7-920 (~550 MB/sec sequential reads) to a much lower power Mediasonic 4x 2TB drives in a USB3 RAID enclosure (~200 MB/sec sequential reads and dog slow writes) made performance something I wasn't going to neglect again).

What about disabling Avahi?

Parity: ST4000DM000 (4TB Seagate) drive Data: 2x WDC_WD40EZRX (4TB WDC) drives Last checked on Thu 28 Aug 2014 11:26:38 AM EDT EDT (today), finding 1 errors. > Duration: 9 hours, 33 minutes, 22 seconds. Average speed: 116.3 MB/sec