gssdu

No worries, no urgency on this end.

Ha ha! Sorry I looked at that and saw a Linux path, not a URL, so went straight to the terminal. Here you go: "connectPluginVersion":"2023.09.08.0637", "expireTime":1699631168000, "osVersion":"6.12.4",

@spencerJ not that I know of... but there was that trip to Romania a few years ago; lovely castles and forests. A lot of mosquitos too, always getting bitten. 🤷‍♂️

Didn't find this; did you mean /usr/local/emhttp/... ? That file, as the extention indicates, is just PHP code, no JSON there.

Not sure exactly what is going on here, some date/time conversion bug? The mouse-over text on the upper-right of dashboard for "Trial Key Expires in ..." reports my key expiring in 1704. Not a critical issue, but somewhat amusing.

Thanks @itimpi for your suggestion. I do understand that I'll be without protection until I can get a parity drive installed. I'm thinking it's a risk I will take as it should not be too long to get my replacement drive in place.

WD have agreed to issue an RMA. My only remaining question is should I (whilst waiting for the replacement drive) proceed to populate the array with data, and add the parity drive later, or should I wait for the parity drive to be in place before adding the data? Or does it not make a difference?

Tried a different SATA cable, same SATA port on the MB: same errors on ata2/sdb Also tried the second cable, different SATA port on MB: errors moved to ata3, but look the same. I'm thinking it looks a lot like the drive is bad. babel-diagnostics-20231014-1618.zip babel-diagnostics-20231014-1609.zip

There are a lot of ATA errors, I/O errors to sdb which is the parity disk. Funny that the Unraid UI hides all of this. Looks like my disk is DOA.

Sorry for the double post; it said that the first upload failed but it looks like it worked.

Here are the diagnostics.babel-diagnostics-20231013-0837.zip babel-diagnostics-20231013-0837.zip babel-diagnostics-20231013-0837.zip

It shows up in lsblk, so I'm pretty sure the power and connection are good. Looks like it doesn't have a partition like all of the other drives do though. I will post diagnostics as soon as I learn how to do that.

I'm using 6.12.4. When I selected the parity drive during device assignment, it just disappeared. There didn't seem to be a way to review or change the assignment. I went ahead and assigned array and pool devices, started the array and formatted everybody. Things look normal (green dotws everywhere) except that there's no sign of the parity drive. On the Dashboard tab, under Parity, it says Parity disks not present. On the Main tab, there's no sign of the parity disk. Under Array Operation, it says Started with the orange triangle exclamation mark and the hover text says Started, array unprotected. Tools, System Devices, SCSI Devices is the only place I see the parity disk. Is this normal? Is this just what it's like when the initial parity build is in progress?

Thanks @JorgeB for the hint! After several failed download attempts, I tunnelled my VPN to Spain, and ¡ole! Got about 2MB/sec download speeds, and was done in 4 minutes. For reference, I'm in Australia. I think DigitalOcean is definitely having a geographically segmented/varigated issue.

I'm seeing the same problem. I've tried three times now over the last four hours to download the 6.12.4 .ZIP file, only received some 100MB across the three attempts in that time. Did find out that DigitalOcean is reporting a CDN issue: https://status.digitalocean.com/incidents/lh3j71zp57hx