Yivey_unraid

Has this release fixed the issues 6.12.6 had with Adaptec HBA cards? I’m still on 6.12.4 because of it.

Just like @itimpisays, do you mean to say that you changed the containers path mapping? Because what you describe sounds like it’s still mapped to /mnt/user.

Yes, that's correct! Maybe wrong wording on my count there. Seems as it wasn't the power cables anyway. Any take on this?

If you change from your custom Docker network to Host, do you get an IP then? I seem to remember that Plex's official container suggests running it with Host, but I'm not sure. I know other Docker images doesn't suggest it.

Backup, backup and backup. 😉 That way it's no problem if something happens.

Do you have the correct cable? There are different cables for connecting from motherboards SATA ports to a SAS-8087 backplane vs connecting SAS-8087 on an HBA card to SATA drives. They look the same, but only works one way. Example (no affiliation with these cables, nor have I tested them): SAS-8087 (host) to 4x SATA (target) 4x SATA (host) to SAS-8087 (target)

For me, the CPU ended up being faulty and Intel replaced it.

Just recapping what happened in the end. The last week it got so bad I couldn't boot anything at all, no Live-USBs or anything. So after months of trying to find the problem I finally couldn't narrow it down any more than to the MB or the CPU. Since I had so many errors that pointed to the CPU I decided to open a warranty ticket with Intel. They accepted after I presented my evidence of my problems and replaced my CPU with a new one. Very nice experience dealing with the support, and I'm glad I bought the boxed and not the trayed version of the CPU since the trayed had shorter warranty. At least for 11th gen, I think the warranty aren't differentiated in the newer generations. Now it runs good again. 👍

Thank you for your answers! It's 4-way splitters directly attached to the 6-pin output on the PSU. Original Seasonic cables. Not ideal, but not terrible either. Looks like it actually was the drive that was the problem. I think.. Restarted the server after moving the cabling around and still got multiple errors. See attached SMART report. Now, perhaps those CRC errors and Current Pending Sector errors might have been a result of the first initial problem, and now causing the drive to behave irrational. I don't know. At first it didn't show at all when connecting it over the HBA. Put it in an external USB enclosure and that made it show up but with no FS or possibility to mount. Added it back to the server and tried it with a SATA cable directly connected to the MB and that worked. Somewhat.. The drive wouldn't mount normally, and after googling the error messages from the syslog I tried mounting it RO in UD and that finally worked. Now I'm copying the 4-5TB data off the drive to an SSD. Figured that would still be faster than restoring from backup. (I really need to setup some cataloging system over what files are in what drive and keep that list somewhere, been on my mind for a long time and that would save so much time in the event of a failure.) It keeps coming more current pending sectors errors during file transfer as well. Will not re-deploy the drive again, if ever, until I've run multiple more tests. Maybe I should just call it DOA and return it. I have another of the same drive bought together with the failing one. A bit hesitant to deploy that now too. But that is also pre-cleared at least. Now, regarding the array. Would it be best now, since I've got no parity, to just not assign any drive to that spot and let it rebuild parity? Or doesn't that work since one device would be missing anyway and it would have no valid parity for it? Should I instead do a New Config again following the same steps as my first post and not assign any thing to Disk 6? In that case I can expand the array with the other HGST 10TB, after parity is rebuilt and then transfer the data from the SSD. Thoughts? HUH721010ALE601_2TGD77RD-20231209-0043.txt define7-diagnostics-20231209-0120.zip

I don’t really see what harm shutting down the server will do at this point, but I’d like someone more experienced to confirm. Any takers?

Have you mapped the container path to “/mnt“ instead of the default “/mnt/user”? If you haven’t done that you will only be able to see user shares and not disks.

'Evening folks! Been shuffling data around in the array to be able to shrink it and remove three 10+ years old HDDs. Following the tried and true "Remove Drives Then Rebuid Parity" method. Moved what I needed to keep elsewhere in the array, then cleared all the drives of data. Stopped the array Tools --> New Config --> Retain current configuration (All) --> Confirm yes Started the array without checking "Parity is already valid". It started rebuilding the parity After only a few minutes Disk 6 started spitting errors and it just kept rising until I paused the parity re-build after a couple of more minutes. The HGST drive is new in the array since a couple of days and was added as a replacement of a smaller fully functioning data drive. It is however a refurbished drive and newly bought, but dated 2017/2018. Passed pre-clear before I added it to the array. I suspect the SATA cable or power splitter is the culprit but can't be sure. It could be the SATA power splitter, although a bit unlikely, since this new HGST drive is more power demanding than the previous Seagate it replaced. - Can I in this stage of the shrinking process "safely" (I know I no longer have valid parity) power down the server and do some changing of cables? Physically remove the now unassigned old array disks? - When I after this have rebooted the server, should I do a short SMART self-test? Since I no longer have a valid parity I can't start the array without the drive either and conduct another pre-clear on it. So SMART tests is basically what I could do. Any advice for me here? Am I missing something? What is my best course of action at this point forward (other than restoring from backup)? Note: Drives are connected via SAS->SATA breakout cables to an Adaptec ASR-71605 in HBA mode. Since unRAID has disabled the drive I can't see it in the maxView Storage Manager for the Adaptec card either. unRAID OS is 6.12.4 All the best! /Yivey define7-diagnostics-20231207-2209.zip

Thanks a lot! Using this with a Tasmota flashed Shelly Plug S. Is there any possibility to add time active field to “Total”? Total is quite useless unless you know when it was reset last. I haven’t seen this on the Tasmota UI either, so perhaps it’s not possible to do.

Haven't uploaded it yet. Life got in the way... I'll try and get to it.

Did you ever get this working with your X12SCA-5F? I'm thinking of buying this board but I would like to be sure that it'll work with unraid and I can use the all the functions on the MB.