fitbrit

Thank you! I missed this post earlier. I'll go over it again in a minute, but it makes sense. Good idea to format the drives when empty, before replacing them. I was going to to use Midnight Commander to do the file transfers. Not sure about rsync - never used it. I will not use TeraCopy because of all the Windows timeout issues.

Thanks for the link and input.

I just upgraded to v6. I take it form this thread that running a mixed FS array is okay? Would it be ok to do the following: Replace a 2 TB in my large array (22 data disks) with a 5 TB drive. Then move the data from another 2 TB drive onto the 3 TB of free space of the 5 TB drive. Remove the 2 TB drive from the array. Preclear another 5 TB drive. Format it with XFS and add to the array. Move all the data from the 5TB Reiser to the 5TB XFS Remove the Reiser 5TB from the array Preclear the Reiser 5TB Format that 5TB as XFS and add to array. Now I can start to migrate data from my 2,3 and 4 TB drives by repeating cycles of the above and adding new 4 and 5 TB drives as needed - to expand the array and migrate slowly to XFS. As my disks go beyond 98% full, I get a lot of failed transfers to the array, with network device no longer available etc. I cannot wait to find a solution to that and I hope XFS will be it.

Yes: A few characters before the HTTP No colon after the HTTP Superfluous " at end of url

I'm in Canada, and got the HGST from Newegg.ca. Thanks for the tip and comments Gary and everyone else.

Thanks. I'll take a look at the HGST NAS one then.

I figured that a purple drive might be good for parity, since any write to the unraid server is also causes a write to parity too. So, it should be the most active of disks int he system overall. I currently have a 4TB black as parity, but am thinking of upgrading to 6 TB (or more?). Any thoughts?

All I see is a 4th gen i3, decent mobo and 4 Gb RAM for $200, which is indeed quite nice.

I'll be interested in the 4TB drives when available.

It's finally back by itself. That was a long time, and I'm pretty certain that didn't use to happen in previous versions.

It's been about an hour since I pushed the START button on the web interface to upgrade a 2 TB drive to a 4TB one. However, since then I cannot reconnect to the server via browser. The server is found, I see the 'waiting for [iP address]' message in Chrome, but then eventually the connection fails. I can connect via telnet, but other than using preclear_disk.sh or midnight commander, I'm not too good with the cli. Is this normal? Is my disk being rebuilt? Do I need to reboot and start again? I seem to recall this happening before, but not for this long. And I might even be wrong about it happening before. Any help appreciated. I'm running either the last 5.0 RC or 5.03.

Did you think that NewEgg had finally got the much sought after delays in stock, and were finally shipping them?

Thanks c3 and garycase. I guess I'll get black drives for the same cost instead.

Seagate 4TB hybrid/SSD drives are currently on sale for $200. Can unraid use these, and/or take advantage of the hybrid feature? My guess is no for me since mine's only a media storage device, and parity writes, for example, will not be accessing the same data often to take advantage of the SSD Cache. http://www.ncix.ca/products/?sku=91259&vpn=ST4000DX001&manufacture=Seagate&promoid=1029

Fantastic pricing. Almost wish I had a Tam's server.

Thank you everybody.

Thanks! I will try to find the right search terms.

I can't find my drive mounting screws for the remaining two bays of my 4224. If anyone has spares they could ship me for reasonable cost, or recommend somewhere online that has them, I would be most grateful.

I'm not sure whether to start another thread or not, but the problems continue. Brief summary: I replaced a 2 TB drive with a precleared 4 TB drive. The 4 TB drive gave a write error in the first few seconds of the data rebuild. I replaced it with new a 3 TB drive while I wait for the RMA. Unraid will not let me rebuild the 2 TB of data onto the 3 TB drive because it is replacing a 4TB drive. Essentially I'm replacing a 2TB drive with a 3 TB, but that momentary introduction of the faulty 4 TB drive has screwed things up. Fortunately I backed up all the files of the original 2 TB drive onto an NTFS volume beforehand. What's the best way to proceed now? Options: 1) Uninstall the 3 TB drive, tell unraid to rewrite parity with remaining drives, preclear 3 TB, add it to the array, and then copy the 2TB's data back to it across the network from the NTFS drive. 2) Wait for RMA'd 4 TB drive, which could be 2 weeks, leaving the other drives unprotected. Don't really want to do this, as my risk taking has a bad track record. 3) Reinstall the 2 Tb drive (which has a suspect ReiserFS), force unRaid to accept the new configuration. Rebuild parity, fix the ReiserFS of the 2 TB drive, and then replace one of my 1.5 TB drives with the 3 TB drive. I am not sure whether unraid may have written to the 'missing' disk 10 (originally the 2 TB drive) since it was removed. I doubt it because the virtual drive is being recreated from parity, and should therefore have writes disabled (because the ReiserFS was corrupt on the original disk at the time of its removal.) 4) Something else. I'm leaning towards 1. It'll have my other drives protected sooner, won't require me to run a reiserfsck on the original 2 TB drive, and gives me two copies of the missing data - one on the removed 2 TB disk 10, and one on the NTFS volume. Any recommendations appreciated.

No - the write error applied to the new drive. A corrupt file system does not cause a write error - it simply gets faithfully copied - and the resulting disk also has a corrupt file system that will need a run of something like reiserfsck to fix it. Correct. This write error has nothing to do with the corrupt file system. You're confusing the various layers of the protocol stack. This error occurred at the physical layer. The file system is a higher level abstraction. Thanks very much, both of you. Unfortunately I don't have another 4 TB drive to replace it with, so I will use a 3 TB one. The drive I was originally replacing was a 2 TB one. Then repair the fs, and then RMA the 4 TB drive. I'd sworn off Seagates a long time ago, but decided to give this one a go. So far my best success has been with WD blacks and anything Samsung/Hitachi/Toshiba (except for the Samsung firmware fiasco a while back). I'm sure all drives have their issues, and I've just been unlucky with Seagates and WD Greens.

I precleared the 4 TB drive and worryingly, the drive showed close to the threshold values for a few of the parameters, but was otherwise ok. I assigned the drive and statred to rebuild the data onto it. Unfortunately there was a write error right off the bat and the drive redballed. Upon thinking about it, it made sense if the corrupt file system is being copied onto the drive to start with, there will be a write error from the beginning. I guess this is what Joe L was trying to warn me about. I've since copied the missing drive's data using parity info to a 2TB NTFS drive on my PC. My thoughts on how to proceed are: To remove the missing disk 10 altogether from the array. Rebuild parity with missing drive. Preclear a drive and add it to the array. Copy the data from the missing drive (from NTFS backup) to the new drive. Then for the other read-only drive in the array: Copy all the data to an off array drive on my PC. Try to fix the ReiserFS on the drive. If all is well and no data is lost - hurrah! If there are problems, but the filesystem is fixed, I'll just copy all the data back onto the drive form the backup, or at least the files that were lost during the fixing of the ResierFS.

Thanks very much! I am currently preclearing the drive (5% post read right now). This info will be useful in the (near) future.

Thanks. I could try preclearing, but I was hoping to have to avoid almost a week of preclearing and rebuilding data (I think it'll take about 5 days to do all that for a 4 TB drive in my system). I don't think I have simple features turned on, and I don't know how to go back to stock unraid. Is there a way to disable the added packages without uninstalling them?

My parity drive is 4TB, and I am running a 3 TB drive as well in the arr. No issues. Thanks for the suggestion.

Re-constructing a corrupted file-system onto a new disk will result in a new larger disk with an equally corrupted file-system. Your intention is great, but your method wrong. Fix the file-system corruption first, then upgrade the disk. Thanks, JoeL. I am thinking that since: The drive is installed physically, The drive it replaces was about 98% full... That I should do it this way around: Build the data onto the new drive. Fix the filesystem. That way, I'll have a back up on the original drive of the files, in case fixing the filesytem results in some kind of disaster. What do you think? I am happy to take your advice and replace the original drive first if you think that would be a better and safer way to do things.