MikeyJeff

Hi JorgeB - the array minus the 2 inaccessible disks (due to the SATA connectivity card) plus the other disk that for some reason went into error state is now fully operational back in Green status with a rebuilt parity which is great - I will need to keep an eye on it over the next few weeks just to see why some of the disk connectivity was a little dodgy for no real rhyme or reason. What I wanted to ask you is that now my Windows network mapped drives are a little out of whack at the moment. I'd like to remap them whereby Z:\ is mapped to the entire share, Y: was mapped to disk1; X: was mapped to disk2 and so on but when I go into the \\TOWER it doesn't show those disks anymore, just the Share - is this because I need to go into each disk where it is disk"x" where each x represents a number of the disk and "Export" that as well? i.e. this screen: I imagine it defaults back to "no" if I have changed my configuration. Will that restore that visibility on my Windows network? Thank you again for your support - you've been most helpful and patient! Cheers, Mike.

Thanks JorgeB - since then, the drive became "Red balled" with the red X indicating the drive was in an error state which is extremely strange. This is the diagnostics prior to me removing the disk from my main array, and putting it into my "trial array" where it loaded perfectly with no issue - very strange. Diagnostics are attached. Restarting my main array minus that disk and it has started perfectly, I created a new configuration, it has started to rebuild parity minus the disk6 in error state, and I can access all my shares and the content as normal - it must have been the "errored disk" that caused me to be unable to read my content in those shares. Keen to hear what you think about why that disk is in error state when putting it into the temporary array, it works and reads perfectly. Thanks for your guidance here, hopefully post this parity rebuild my new "slimmed down" array will be stable going forward. Cheers, Mike. bargetower-diagnostics-20230403-1729.zip

Thanks JorgeB - that was the solution - I would never have guessed if you hadn't told me, so thank you! I managed to fire up a temporary array - pulled all the data off those two disks (as suspected, nothing was wrong with the data on the drives). What I have done since is fire up the main array with two fewer drives, indicated that it is a new configuration - all disks were recognised and naturally it needs to rebuild the parity disk which it started doing. One of the disks is "erroring" yet is in green status and I have never had an issue with that disk and I don't know why. When it finishes parity I will remove the disk to the temp array and check its contents as I don't believe there is anything wrong with it. My question to you though is that my old Shares are visible via my Windows PC but there is no content within those shares. Do I need to reset the Share in order to see the files or is there some other reason why the Share is visible on the network, but has no content in it. (When I do a view of each disk I can see all the files so there is definitely content readable on all the disks). - It could be related to the erroring on the disk - what do you think? Thanks for all your help, I feel I'm making progress!

I have managed to use a secondary PC just to ensure my data is safe on those two disks that I couldn't access, and of course, successfully have added them to this temporary array (perhaps I shouldn't have done that, but ultimately I just want to get the data off them now) - I didn't have enough RAM available immediately so couldn't install the Community Application software (ugh, yet another problem I didn't anticipate) - I can now see those two disks in this temporary array with no problem and all the data is safe, but I am struggling to be able to see that content in my Windows Explorer so I can start sifting through what I'd like to keep what what I'm happy to get rid of: Is this what "Unassigned Devices" will help me do? I will get some additional RAM and go that pathway but is there a very simple way to ensure a PC connected to the same network can then slowly copy off content via Windows Explorer? When I go to "TOWER" on my network in Windows Explorer on another PC connected to the same network (It sees the Device), it doesn't show anything within that folder - so I clearly need to point it to those two disks just like on my proper array. Thanks in advance.

Hi JorgeB - I really appreciate your help with this - in trying to work this situation out, (trying other PCI-E slots for the card for example) - I've now just lost another disk - Disk5 is now "missing" - that is connected directly to the Motherboard via a SATA connector - I haven't touched any of those connectors - just the two troublesome ones. What is possibly happening here - is this motherboard dying? I've never seen anything like it. Diagnostics attached - any advice appreciated!! Thanks in advance. Mike. bargetower-diagnostics-20230330-2006.zip

Is there an easier way to connect those drives that I currently can't fit into the array - get the data off them or do they have to be mounted into Unraid in order to be visible to the operating system and therefore accessing via an SMB / Windows Explorer type share?

I will try that - I also have another motherboard not being used and may consider that (but it's a big job). The other thing I alluded to above is - is it possible to mount the system under new config - clear some space, disconnect two drives, attach the two that currently can't be connected simultaneously, copy their data over, retain only 8 disks, then rebuild parity - or is there a better way to accomplish that task? I don't know if there is a way to connect just those two disks to another PC, copy the data over, then rebuild parity on the revised array minus two disks going forward.

So strange the MB would suddenly stop reading this controller when everything else seems to be fine (and so suddenly with no system change) but I do have my media center PC running Windows 11. I guess I’d plug in the card assuming I have a spare PCI port, connect the HDD via SATA and I’d check to see if disk manger can see the disk even if it can’t read the file system - is that what you’re thinking?

Thanks for your reply. I tried a different one as per my original post but it’s essentially the same type of product. PCI-E to SATA except this only has 2 ports which is all I need. I just cannot understand why it is not being read by the system or recognised anymore. I have tried several PCI ports too. I can’t imagine the motherboard is damaged - it hasn’t moved nor been exposed to power surges or anything like that. What should I do? A last resort would be to I guess clear some space on the remaining drives (losing my parity in the process) - reconnect the two drives - copy their content over to the others and have 2 fewer drives then rebuild parity? Can that be done or is there a better way of getting the data off those drives if for some crazy reason I can’t access the total number of drives anymore. Thoughts? thanks again.

Thanks JorgeB - appreciate your quick reply. The issue I have is that this original controller has been in exactly that PCI-E slot for 10 years with no issue and all of a sudden it stopped being detected. I bought a new one as I indicated, put it into not only the same PCI-E slot but chose 3 other PCI-E slots (1, 4 and 8 channel) and it is not detected either. Do you have any thoughts what might be causing this? There are no BIOS changes, updates, no firmware changes, no nothing. It just powered it down on Thursday, powered it up on Friday as I do frequently, and bang - two drives missing! Thanks for all your help. Cheers, Mike.

Hi guys, Needing some advice from the "brain's trust" for an issue that has emerged with no warning. I have an Unraid array running 6.11.5 which has a total of 10 drives, 1 parity, 9 data. This configuration has been working smoothly for ~10 years now without a hitch. A few days ago with no rhyme or reason, upon booting the array I noticed two disks missing - naturally the system doesn't mount the disks because the config has "changed": Tried a shut down, restart didn't resolve the issue, tried to mount the array, didn't work either, so then went to examining the cables - both power cables seem fine, then I noticed that the two specific drives are the only ones that are connected using a PCI Express to SATA port replicator (the rest are connected to the motherboard directly), so started turning my attention to this. The Port Replicator I'm using is a Highpoint Rocket 640L: HighPoint Rocket 640L Lite Version 4-Port PCI-Express 2.0 x4 SATA 6Gb/ – DirectNine - Australia I've had it for 10 years and it's worked perfectly for all this time. So I tried to connect the "offending" two disks to the motherboard directly by uncoupling 2 other drives just to see if there are any issues with the power cable, the SATA cables or the disks. Sure enough, they are recognised by the system immediately. Deducing that for some reason the PCI-Express port replicator is failing, I've then gone and bought a new one (not the same model): Buy Startech PEXESAT322I 2 Port PCI Express Controller Card | KVM Hubs & Controllers | Scorptec Computers I've then gone and connected the new port replicator to the two hard disks, restarted the array and unfortunately, no luck. I cannot understand why the system is all of a sudden not recognising these two disks given I'm convinced there's nothing wrong with them as when they are connected to the motherboard directly, they work and prior to Friday just gone (25th March 2023!) this configuration has worked flawlessly with no issues for 10 years. I was wondering if anyone can shed some light on what might be going on here and whether there's some change that has potentially occurred in the operating system that is causing this that I'm not aware of. I regularly update the Unraid software and I believe it is uptodate or at least very close to. To assist matters I have attached the diagnostics file that I ran last night with this configuration. I notice in the log that it indicates that "slot 8 and 9 are missing" but I cannot understand why this is the case. To confirm I have tried the following in the interests of narrowing down the fault: - Tried different SATA cables - no success - Tried different PCI Express slots for the SATA card - no success - Tried a different (brand new) SATA card - no success (in 3 different slots) - Tried connecting the hard disk to the motherboard directly (works - implying the data and power cables are fine) - Checked the BIOS - ACHI mode is activated and I can't see anything preventing ports from working - but again, this has worked for years and I've made no changed to the BIOS. Very keen if someone can shed light on this. The fallback plan for which I'd also like guidance is that if this simply fails to work, I perhaps need to connect those two "offending" drives up, disconnect two others, restart with new configuration (obviously invalidating my parity) copy their contents over to the array with free space available, remove the "offending" hard disks, reconnect all the ones to the motherboard only (I will have 2 fewer disks) and then rebuild the parity drive - I'm wondering if that's the workaround if the two disks connected to the SATA replicator simply fail to work. I'm not worried about losing data - I know the disks are fine, so if I have to rebuild parity if all else fails, I'm not concerned. Welcome thoughts folks - I'm scratching my head on this one. Cheers, Mike. bargetower-diagnostics-20230327-2120.zip

Hi folks, wanted some assistance with being able to access content on my unRAID array from an iPad/iPhone style device using software such as VLC which, via its Network function will enable you to connect to an SMB type protocol connection. For what it's worth, VLC accurately detects my unRAID server on the network, however doesn't seem to accept any of my credentials and I am coming to the conclusion that I need to configure or provide different permissions/security settings on the SMB connection on unRAID for VLC to be able to access it correctly. VLC asks for the following information: Server name: (Should be simply the name of my unRAID server Port: (Unsure what this needs to be, so at the moment have left it blank but perhaps its 80 or 443?) username: (I'm using 'root' as the default username of my unRAID server) password: (I don't have a password so just leaving it empty) Workgroup: (Sets the default for WORKGROUP so have left it alone at the moment) The wheel "Spins" without ever connecting so clearly I'm doing something not quite right. I have looked at the unRAID option to establish an SMB Share but it asks for a Server name, and I would have thought the Server name would be my unRAID array name, but perhaps that option does something entirely different. This function used to work seamlessly on my old unRAID 4.7 server but there's clearly a bit more sophistication in this version (I'm running 6.8.3) so thought I'd ask to see what I might need to do to get this working. Best wishes and thanks in advance! Cheers Mike

Just on this, I have the Array in this current status: Am I now in a position to remove "sdg" (Disk5) from the array physically - replace it with the new 6TB WD Red hard disk that I have just purchased and it will then pre-clear, etc. format the disk as XFS, and I can then assign it to the array as new disk5 rather than try to rebuild old disk5 from the parity image? Thanks again! Mike.

Hi guys - I have tried to undertake the method above, and have followed those instructions to the letter, but it doesn't seem to be taking the disk out of service, it keeps wanting the missing disk. Just for clarity, I used these steps: 1) Stopped the Array 2) Selected "New Config" 3) Preserved Current Assignments (All) 4) Clicked "Yes I want to do this" and pressed "Done" 5) Took Disk5 out of service by unselecting it in my assignment and it then becomes "missing disk" 6) Brought the array back on line. It simply says "Missing disk - please replace disk" - I'm clearly not doing something correctly here. I have a brand new 6TB disk that I want to pre-clear and replace Disk 5 with (but Disk 5 has nothing on it so don't want to rebuild it, and wish it to be in the XFS file system, not RFS), but it seems to want the old disk. Perhaps there is a better way to get the desired outcome - Disk5 2TB RFS to be replaced with a 6TB XFS disk. Welcome the brains trust on this! best wishes and thanks, Mike.

Okay makes sense, re: drive attachment. The only thing I'm not sure about is why I would need to go and "New Config" and "Preserve Current Assignments" first when I haven't made any changes to the array (yet), apart from stopping it. Wouldn't I only need to unassign the disk or does forcing New Config prior to making any drive modifications perform an important preparatory task pre-unassigning the disk? Thanks so much for your quick responses - much appreciated!

Thanks so much for that! Just so I'm clear - do I physically disconnect the disk prior to undertaking the above procedure - I can't seem to see when I'd physically disconnect/remove the drive in the above. Cheers! Mike

Thanks for that - makes sense. So essentially my procedure would be to: 1) Stop my array 2) Unassign "disk5" as "no device" (I can't remember what happens after I click this!) 3) Go into "New Config" 4) Preserve current assignments (All) 5) Start array which will rebuild parity?? I just want to make sure I'm doing the right thing in the right order as the rest of the array is working perfectly and I'd hate to make a mistake! Once the new config is operating well with parity rebuilt, I will purchase a brand new disk, insert it into the array, have it pre-clear, format as XFS, and be up and running but feel I should remove this disk that is becoming problematic before replacing with a new disk. Let me know if my procedure is right here! Thanks again, Mike.

Hi folks, I have a similar question regarding replacement of an incumbent disk. I have detected SMART errors (only a few, but it is an old disk) on my "disk5" which is a 2TB WDC Green disk from years ago. Rather than take a chance that the disk is failing, I think it makes sense to replace this disk with a nice 6TB WDC Red brand new drive. What is the best procedure to accomplishing this? From what I can gather, given I have taken all the data off this 'disk5' as a precaution, do I simply unassign this disk, allow unRAID to trust the new configuration (would it still need to build parity given the drive is empty?) - then remove the disk, add the new one, and allow it to be pre-cleared, formatted to XFS and then it be active in the array? The reason I don't want to simply replace the old drive with a new one is the old drive is 'reiserfs' and I don't want it to rebuild an empty drive with a legacy file system - unless that's not what happens given the disks are of different sizes. If there is another way to effect this outcome - i.e. take the empty drive out of service, put the new drive in, have it preclear and format XFS and enter service, let me know! Best wishes and thanks in advance! Cheers, Mike

Hi folks - thanks for your assistance with the above - turns out after replacing the SATA cable, checking the power cable, that the hard disk just died. As soon as I put another hard disk in, the array recognised it immediately. To that end, the replacement drive is another WDC 2TB drive that was taken out of service upon getting a new 6TB WDC Red NAS drive recently, so this one is sufficing for now, but I'd like the brain's trust view on whether this drive is of good condition or not. The SMART report passes according to the UnRAID operating system, however the re-allocated sector count bothers me. It is only "3" and isn't increasing however I wanted to know if there's anything else amiss with this drive and should consider replacing it, or whether keeping it and simply keeping an eye on SMART IDs 5, 187, 197, 198, 199 would be appropriate. Thanks again folks, SMART report attached for the replacement drive. Cheers, Mike bargetower-smart-20200218-0837.zip

Thanks for that! I did use three completely separate SATA cables (two of which have never been used, one has been used but works correctly). - so convinced the cables are fine. I do think testing a different SATA port makes sense. Just a quick check on that front - if I swap out a SATA cable that is currently connected to one of my other disks and try this one (just to see if the disk is indeed dead) - will that cause my array to ruin itself or when I simply plug the working disk (to test the port/cable) back again will the array simply resume its current state okay. Reason I ask is I don't want to inadvertently cause another issue by testing this one. Put another way, if I unplug "Disk 4" with Disk 5 currently failing, and have the SATA cable that I know works into Disk 5, and then Disk 5 then works again, will the array become problematic because now Disk 4 has been recorded as "Not Connected" or will my array be okay, I then reconnect the cables the way they were, deduce the disk is now dead and replace the disk. Just being super conservative, appreciate your advice! Cheers Mike

Hi guys, thanks for the above - I have tried 3 different SATA cables (all have never been used) connecting into that particular disk and interesting, it is now showing under the unRAID array as "Not Installed" - see new diagnostics attached. It used to be just taken out of service, but now is showing as not being even detected. This has not occurred to me before. I'm trying to figure out if the hard disk has just "died" or whether the power cable is problematic, however this singular SATA-style power cable from the motherboard has two "ends" to it - one going into one of the other hard disks at the end of the cable, and the one going into this hard disk is "half way" down the cable - I'm sure you know what I'm describing which suggests to me the cable itself must be okay (or perhaps that's not right). Is it more than likely the hard disk has just "died" - I just didn't think that this is how a hard disk would behave. I have another hard disk that I took out of service in my unRAID array and is sitting on a shelf - is it worth plugging this one in (the data on it is old and could simply be overwritten) and seeing if it is the hard disk that is problematic in lieu of replacing it with a new drive, or is there something more sinister going on here? I can't believe that the PCI card I have plugged into my motherboard (for more SATA slots) has only this particular port that isn't functioning without the others being problematic, so would welcome insight as to what might be going on here. It does sound on the face of it that the hard disk has completely failed but am not ruling out power either. Best wishes, Mike. bargetower-diagnostics-20200212-1657.zip

Hi guys - apologies to return back here with the same scenario again, but after doing an extended SMART test, discovering the drive had no errors, checked the cables, etc. and then rebuilt the drive from parity, and having no issues for the last few weeks, the same disk has red-balled again (red X these days). The array has been off for the last few days, but turning it on has disabled Disk 5 and hopefully UnRAID's decision to deactivate Disk 5 is captured properly by my diagnostic file. I have attached it here - I would appreciate thoughts on what could be going on with this disk as extensively testing it revealed no issues, but if it is ultimately the cause for these issues, I'm happy to just replace it with a brand new one - unless of course it happens to be the cables, but they look absolutely fine to the naked eye, but again would welcome feedback. Thanks in advance. Cheers Mike. bargetower-diagnostics-20200209-2126.zip

Hi there - thanks for the quick reply. No real reason why my Plugins aren't uptodate, I rarely use them, and have just updated them so they are the latest version. I do however keep track of my Unraid version, and it seems to suggest this is the latest version when I pressed the little "i" icon next to the version - this is how I have updated it in the past, however having forced an Operating System check, I notice as you suggest that v6.8.1 is available, so will update that now - thanks for the tip. Appreciate the suggestion on the drive in terms of its age - I will do a full Extended SMART test before contemplating restoring to that, but will also look at purchasing a replacement disk. None of the other drives show any SMART errors. Quick question for you - if I was to replace that 2TB drive with a 6TB drive (my parity array is 6TB) - will it happily rebuild that drive to a larger capacity drive, or does the replacement disk have to be the same size as what it is replacing? Thanks for your help. Cheers, Mike.

Hi there - thanks so much for your swift reply. The full ZIP is attached below. Welcome any insight in terms of next steps. Let me know if you need anything else. Best wishes, Mike. bargetower-diagnostics-20200120-1512.zip

Hi folks - I have a similar scenario. I have been running this Unraid array for years and notwithstanding a few new hard disks replacing some older ones, have had no issues with this array until today when one of my drives has become "red-balled" - or "Red X". I have undertaken a Smart Diagnostic Report and it doesn't appear to have any issues with the key stats of "Red Read Error rate" and "reallocated sector". Before rebuilding the drive from my parity (which is valid) I wanted to see if someone who is more knowledgeable about reading these SMART reports can check this drive to see whether it is indeed developing issues and should be replaced, or whether it is reasonably safe to rebuild to the same disk. SMART report attached. Thanks in advance. Best wishes Mike. WDC_WD20EARX-00PASB0_WD-WCAZAD181918-20200120-1457.txt