Pro-289

Ok, to be clear, the array is started and the drive is being emulated but not accessible. I have the drive Unassigned Mounted and recovering the data. Once the data is recovered, would the correct procedure be to unmount the drive, Format the unmountable drive, stop the array, assign it back to the disabled slot and then start the array? Would the array try to rebuild the missing drive? I just don't want to do it in the wrong order and have the array start the rebuild process again which won't work.

Okay, after removing the drive from my array again, I noticed my Unassigned Devices plugin showed the filesystem as ReiserFS, which is was/is. So I set it to Read-Only and share the drive and mounted it outside of the array, and all my missing data is there in the drive share. I'm in the process of extracting the data to an external drive. So now what are my options after I get all my data off the drive? The emulated drive didn't work after unassigning it as I think the array is still trying to access the drive as XFS. When I had the array stopped, I don't think it gave me the option to change it back to ReiserFS, as it was grayed out. How can I remove that drive from the system entirely without parity trying to rebuild it, and then copy the data back into the array? If that would be a better route to go after getting the data backed up.

I've upgraded the OS to 7.2.2 the other day. It warned me about 4 resierfs drives for future support. I was trying to upgrade my file system from reiserfs to xfs. I was successful with 2 out of 4 drives. But on the 3rd I wasn't paying attention and while I stopped the array in phase 1 where I should have selected the drive to Empty, I skipped to selecting the new OS on the drive. I realized what I did before I started the array, so I selected the device in the slot as None as if I was going to replace the drive and started the array. It said it was being Emulated. So I stopped the array selected the same drive and started it and then it stated it was rebuilding the drive and completed after about 13 hours. But I get the unmountable error on the drive. I stopped it and started it, but the same issue. It does still show the filesystem as XFS and not the original ReiserFS. What steps can I do at this point to hopefully recover that drive/data? Could I unmount, emulate the drive, then change it back to reiserfs and rebuild again?

Just wanted to say thanks, it worked great. Easy to follow instructions! Ever since ProFTP took a crap, my buddy wasn't able to log in. I did a bunch of drive maintenance and upgrades while I was at it. It's like a new server. :)

Have you tried testing the RAM yet? That would be a good start. At the initial boot menu, select the RAM test instead of the default loading of unraid os. I know bad memory can create all kinds of random problems in an os. A windows pc can crash many different ways with unstable RAM.

I believe I've recently had an EMI issue myself. I had a bad power supply that was arcing voltage inside, probably due to a bad capacitor. You can hear the voltage noise from 20 feet away. I think it was getting inside everything on my system. Tried changing out cables, reseating everything and moving cables around. Misc drives being flagged with CRC errors, and even one drive being disabled. Just to be extra safe after I replaced the power supply and all cables, I went a little unconventional and also put snap-on ferrite beads around all SATA cables and the main trucks of my power cable splitters. Thirty dollars of what the heck why not, and so far so good with no CRC errors on 10 hard drives and one SSD cache drive. Would have probably been fine with just a new power supply. It would have been interesting to keep the bad power supply while adding ferrite beads.

I just did an update from 6.9.2 to 6.10.3. I use a custom banner. The first thing I noticed after the upgrade was the solid color overlay on the top-right that used to be translucent and was covering a good portion of my banner. I found the option to put it back to almost how it was before by selecting "Show banner background color fade:" option to No. But I'm still left with a huge circle and down arrow. When I click it it states "Enhance your experience with My Servers". I click it and then select "No thanks", but it still stays on the screen. How do I get rid of that advertisement on my banner bar?

Yup, worked like a champ. Got my 4TB as parity now without risking issues during the 15 hour rebuild. Maybe when I get another 4TB, I'll set that as Parity 1 then remove Parity 2 for optimum performance. Thanks for the help.

So what happens afterwards when I remove Parity 1? Will I get warnings about the drive missing, which of course I should? How do I then make the array happy to keep using Parity 2 without Parity 1? I've heard of "new config" before, but not sure how that works.

I have a 3TB parity drive and some 3TB and 2TB data drives. I bought a 4TB drive that I now want to upgrade the 3TB parity. I just had some ultra dma crc issues with a few drives after moving around cables. One went disabled during a write I presume. I had a faulty/arcing power supply which I replaced. Changed out all my cables. Put some ferrite beads over my sata cables for the hell of it. I rebuilt that disabled drive and everything on it seems okay without error. I know I could disable the 3TB parity, assign the new 4TB as parity and rebuild it. But during that 12hr rebuild time frame if I have an issue with a data drive then I'm not protected from getting my array out of wack. Seems the easiest way if possible would be to install a new parity drive and have it copy from old to new in offline mode. Pull the old drive and start the array with out any rebuild, then run a parity check for good measure. When you do Dual Parity drives, are both drives exactly the same as each other? So could I add my 4TB as Parity 2 and have it rebuild onto that. Then remove my 1st 3TB parity and drop back down to a 1 parity drive array without rebuilding again?

I ran a preclear script years back on some 2TB and 3TB drives I've added. Glad I did. Found one that had issues during the write/read/verify. Afterwards I ran a SMART test in my windows machine and verified the drop in health. I RMA'd that sucker just a few days after receiving it. The replacement passed and I've been error free since, but have never had an error on any drive. I have nine drives now since I started with a couple a decade ago. I plan on getting a 4TB and replace my 3TB parity drive to accommodate more 4TB drives. Currently I have a mix of 2TBs and 3TBs. Sometime later I'll get another 4TB to swap with my aging 2TBs. But I've always loved that preclear process to verify my purchase.

I just installed this in v6.7.2. The file access seems to work after I press Refresh the file I had played showed up. But, I have 5 out 8 disks that spin up every time I open the Share folder in Windows 7. I even tried with thumbnails disabled. And I have Dynamix Cache Dirs installed. After the 5 disks spined up I noticed my total reads went up by 12. Why the heck are my drives spinning and reading just opening the share?

8GB, the max my 2010 motherboard can handle. I don't use many plugins or dockers, but I really do need way more than that. My Dynamix Cache Directories seems to max out my RAM and my drives still spin every time I open the mapped drives. Tried wiping the plugin and reinstalling with stock and altered settings, still spins up. How come this isn't built directly into the source code of UnRaid.

guinea pig Using an old release may not be all that bad. An old release is just a previous new release. Sometimes updating to the latest and greatest causes the guinea pig effect. [cough]Windows 10[cough]