candre23

Maybe I'm blind, but I can't find a list of new/upgraded features for 6.0 anywhere in the wiki or forums. I've been on 5.0 final since it came out, and while I probably won't upgrade to 6.0 until it's stable, I'd like to know what's new and improved. I see some mentions about a new plugin handling scheme and a new file system, but I don't know what they are or how they're different from what I have now. I can't even find a definitive answer to whether or not 6.0 supports multiple parity disks. Can anybody point me to a feature list, preferably with some explanation of what those features actually do? Thanks.

These are "archival" drives, so they're intended to be written to infrequently. That's fine for disks under unRAID - except the parity disk. What's not entirely clear is whether you're not supposed to use these drives in a frequent-write scenario because they're slow, or because they can become unreliable. I have a suspicion it's the latter. I'm just not sure how tracks will hold up when other tracks that partially overlap them are being constantly re-written. Much as I would love swapping out some of my 2TB drives for these reasonably-priced 8TB monsters, I'm going to hold off until somebody really breaks one in for a while to see if it holds up.

This may be a very noobish question, but how does typing //tower in on any machine on the local network resolve to the unraid server? I would like to do something similar with a raspberry pi based web service.

It hasn't failed since moving to final, though that was only a couple hours ago. If it locks up again, I will.

WebUI/unmenu crapped out again during parity check. Since the array is as healthy as it's going to get at this point, I upgraded to 5.0 final. Running parity again with fingers crossed.

Rebuild completed this time. All looks good. Running a parity check. If no problems crop up, I'll upgrade to final. Thanks for the help, guys.

I have unmenu installed now. When the default UI crashed, I tried unmenu, but that wasn't working either.

Momentary press did nothing, so I did a hard power-down. I'm going to give it another chance to do a rebuild as-is before I try upgrading. The upgrade instructions advise to only do an upgrade with a healthy array, and mine's not healthy at the moment. If it craps out again, then I'll take the chance with an upgrade to final.

Taken this morning: mdResync=2930266532 mdResyncCorr=1 mdResyncPos=1891383836 mdResyncDt=157913 mdResyncDb=1689656 After more than two days, I think it's safe to assume the parity sync is never going to complete. What is the safest way to shut it down?

I believe I found the pertinent section of the mdcmd output. Unfortunately, it doesn't seem to be doing anything. Here's what I had at 8:30 this morning: mdResync=2930266532 mdResyncCorr=1 mdResyncPos=1891383836 mdResyncDt=66053 mdResyncDb=1689656 And here's what I had at 7:30 this evening: mdResync=2930266532 mdResyncCorr=1 mdResyncPos=1891383836 mdResyncDt=107229 mdResyncDb=1689656 I'm guessing mdResync is the total parity size (3TB is what I have) and Pos is the current position (1.8TB sounds about where it crapped out). If this is correct, the Pos hasn't moved in nearly 12 hours. The only thing incrementing is Dt, and I'm not sure what that is. If it was working, it should definitely be done by now. I've attached the full output taken just now, in case that helps. Any suggestions? status.txt

Unfortunately, my drive cages don't have activity lights. Any other way to tell?

Running 5 beta 12. I had a drive crap out a few days ago. I got a new drive, ran a triple preclear on it (no errors), added it to the array, and started the rebuild process. Old drive was 2TB, new one is 3TB. The last time I checked up on it, it had been running for about 7 hours and was at ~60% done. Just checked again and the webUI is no longer responsive. I can still get in through the terminal. Is there any way to either re-initialize the webUI or check on the progress of the rebuild through the command line? I don't dare reboot until the rebuild is done - if it's even still rebuilding.

Parity repair finished. The disks are full of files, but I have so many that I really couldn't say if anything specifically is missing. At the very least, it's mostly all there. Thank you so much for your help. I'm extremely grateful to be back up and running again.

Here's the --check output for both drives. All good? fixed3.txt

MD7 seemed to work. Started the array and all drives are present and accounted for. Are there any further actions I need to take before re-synching parity, or am I good to go? fixed2.txt

By the time I got home, the disks had finished doing whatever it is they were doing, and had unmounted. What's next, doing a rebuild of disk 7?

The disk did mount, and did appear to contain data. However, when I went to stop the array, the system got stuck in a "retry unmounting disks" loop. I'm accessing the system remotely, so I can't physically power it down. Hopefully it won't hurt itself by trying to unmount for the next several hours.

Ran rebuild-tree. I wasn't sure if I had to use sdg or sdg1, so I used md6 as per the wiki. It looks like maybe it worked? Output of rebuild and --check attached. fixed.txt

Rebuilt specifying partition 1, then re-ran --check. Output attached. Still not looking good. rebuilt.txt

Got this: reiserfs_open: the reiserfs superblock cannot be found on /dev/sdg1. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb.

Done. I only did disk 6 (sdg) since that's the only one I borked up with the last step. Output attached. Awaiting further instructions. partition_fix.txt

Do you mean the unraid_partition_disk.sh script? Am I to use the -p option, or something else? Please be specific, as I obviously don't know what I'm doing.

Ran on disk 6 using answers in the thread. I wasn't sure if it worked or not, so as the program suggested, I ran it again with --check. It does not appear to have gone well. The post you linked continues on about something called spinrite. Is this something else I have to run? rebuild.txt

I was continuing to have trouble getting the machine to boot properly, so I replaced all the guts. Asrock H61M-DGS, celeron G1620, and 2GB of DDR3 RAM. During replacement I noticed a couple caps on the old board right next to the main power connector that were definitely puffy. Now it's booting up cleanly every time. Partition script output attached. partition_test.txt

Both drives say "MBR: 4K-aligned". dd output attached. dd.txt