ptcadoc

It worked !! Many thanks for the help

Thanks !!

Meanwhile, can I ask another stupid question? Do recurrent "rebuild" events shorten the life of the hard drive? I'm referring (I guess) to repeated long writes to the disk as (as far as I understand) the rebuild process involves the entire drive to be rewritten from the backup copy (parity). This is the second time this has happened.

Noted, thank you so much. Will keep you folks posted

Thank you for the reply. It's "rebuilding" right now (at 49%) - I'm guessing I should wait and see, let it complete (if it does) then change the power cable? Or interrupt the process now? Thank you

Thank you that's great to know. Here's what happened 1 . What I then did was stop the array then make Disk 3 "unassigned" → restart the array then STOP again and went back to Disk 3 and reassigned it to the disk that was there. See image The system gave out a few error messages (which I believe are expected) and the "rebuild" started. Then pretty soon a series of error messages flashed and the "rebuild" was PAUSED I stopped the array again and then went to Disk 3 and that disk was no longer there Then I turned the array off, powered down, changed the SATA port to a different one and rebooted. Turned the array off and behold, that missing disk was back. Reassigned it to Disk 3, turned array on and got some confirmatory messages (see below) I took another set of diagnostics (attached). Now the array "rebuild" restarted and so far has been running for the last 4 hours What is going on? Is my SATA card bad? We can be sure that the disk is not dying right? Really REALLY appreciate the input and help klingon-diagnostics-20210623-1552.zip

Dear Smart People OK I went out and bought new SATA cable for the drive that seemed to be on holiday. Did a shut down, replaced the cable and then turned it on. Got this message immediately (see below) and then, as suggested, ran a second diagnostic run (attached). The drive is still 'disabled'. Will be grateful for suggestions klingon-diagnostics-20210623-1519.zip

OK thank you - will do and report back. Thank you very much for the input guys

OK thank you so you're suggesting the same thing - power down, reseat the cables and see what happens?

Thank you. Will wait for other inputs and if nothing else is posted, do as you suggested.

Thank you so much for replying. What do you suggest I do? Pull out the cables and reconnect? Thanks in advance

Hi smart folks I'm a dumb medical professional, requesting you people's help! Unraid 6.9.2 Set up: Seagate 6 TB drive X 3 + WD 4 TB x 1 + a cache SSD. One 6TB drive is the parity drive. The drive disabled is "Disk3" the most recent drive that I added to the server. Woke up this morning and one 6TB drive is "disabled" and in "emulation mode". I can read files that are on that drive but I'm assuming "emulation mode" means it's because of the parity drive. I don't know enough about any of this so please bear with my ignorance. I looked around some of the posts and here's what I did The disk "error log" is posted below. The diagnostics is also posted below. This happened once before months ago and at that time I inadvertently rebooted the system BEFORE collecting the diagnostics file but this time didn't do so (thanks to you guys reminding me). At that time basically the "parity backup" kicked in and the disk was reconstructed and we could never figure out why this happened. What do I do now? Is the disk gone bad? This is a fairly NEW drive so I'm going to be pissed if it's a disk hardware error Many thanks in advance! klingon-diagnostics-20210620-0924.zip

Got it. I'm impressed (from an uninformed person's perspective) with Unraid. Previously I had a FreeNAS server and had nothing but problems including a failed disk rebuild after a drive failed and repeated glitches so I finally switched around 6 months ago. With Unraid, a glitch happened and got rectified easily, although only after I sought help as I didn't know how to go about it. Thanks again

I see, thank you makes sense now For my own learning/understanding, how long can this "emulated mode" have continued? In other words, could I have continued to "write" to Disk3 for quite a while and if so, at what point would have things finally broken down?

So let me see if I understood correctly This still could have been a cable / connection issue? But then when I undid the SATA cable and replugged it in, the drive still remained "disabled" doesn't that suggest the cable was NOT the isssue? Do I have ways to prevent this from happening again? Thank you

So after 15 hours of "rebuilding" it's all good !!!!!!!! Disk3 is back online and I got these messages I'd like to thank everyone for their suggestions especially @trurl I really really appreciate the time you took out to reply Moving forward, can I pick your brains on 1. Why this might have happened (it seems, if I understand correctly) this wasn't a hard drive hardware issue 2. More importantly, how to prevent it from happening again? Thank you

OK, that's very helpful to know. Thank you so much for the help so far. It says the rebuild will take 11 hours will post how it goes and if there are any hiccups.

Thank you. I followed the steps and as soon as I made the drive unassigned this error popped up. I continued and now have it doing a "rebuild". Is this error message suggesting a drive failure? Thank you immensely for the help One other question - while this rebuild is happening I should refrain from using Plex or writing anything to the server (or is it OK to do so)?

Thank you. I looked at the article you referred to Quick question regarding the steps: 1. Stop array 2. Unassign disabled disk 3. Start array so the missing disk is registered Does "unassign disabled disk" mean change disk3 to "no device" as shown in the picture? Thank you

Hi - thank you for the reply Yes I'm realizing I should have gotten diagnostics before rebooting I guess the instinct to "turn it off and on" got the better of me I have everything backed up. I guess my next (stupid) question is what are the exact steps to do the rebuild? Can you provide an "idiot's guide"? Thank you in advance

Thank you for replying. Please see attached. klingon-diagnostics-20210303-2231.zip

I'm a medical professional, requesting your smart people's help! Unraid 6.8.3 Set up: Seagate 6 TB drive X 3 + WD 4 TB x 1 + a cache SSD. One 6TB drive is the parity drive. The drive disabled is "Disk3" the most recent drive that I added to the server All of a sudden, one 6TB drive is "disabled" and in "emulation mode". I can read files that are on that drive but I'm assuming "emulation mode" means it's because of the parity drive. I I don't know enough about any of this so please bear with my ignorance. I looked around some of the posts and here's what I did 1. Rebooted a couple of times from the GUI - no change 2. Undid the SATA cable and reconnected. Used a different SATA cable . No difference 3. I downloaded the SMART file for that drive and it's attached here - from what I can glean it says PASSED 4. Going through some of the posts here there was a suggestion to follow the steps outlined here https://wiki.unraid.net/UnRAID_6/Storage_Management#Checking_a_File_System 5. So I went into "maintenance mode" clicked on the Drive in question, then Check button to run the file system check. Copied the info I got onto a text document it's attached I have no idea what to do now - please help. Is the drive gone bad ?? Thank you in advance klingon-smart-20210303-2130.zip filecheck.txt

Thanks for the reply. Appdata and system shares are on cache. Don't know where Plex is transcoding (naïve here ...... how may I find that out?). Don't have DVR with Plex. Many thanks in advance.

Does Plex constitute as a docker that writes directly to the array?

Bump