Johann

I can't seem to start my array, its stuck on mounting disks, I attached my diagnostics below! I've tried booting from safe mode and the array still doesn't start. The below diagnostics is regular boot. toblerone-diagnostics-20220814-1446.zip

Would it be possible to use this to manage the UNRAID wireguard implementation, best of both worlds?

Is it possible to use share names with spaces in the name, I tried messing with the script but I wasn't able figure out how to do this. Any help is appreciated!

Can anyone chime in on this? It has happened twice. thanks in advance.

Hi, I had an unexpected shutdown and I did a extended problem test and it said there was a hardware error. I attached my diagnostics from Tools. Thanks in advance. toblerone-diagnostics-20210107-1858.zip

Thank you, I'm rebuilding it right now. I'm using a 8087 to 4x data breakout cable and I made sure the connection was good, its been fine forever not sure what went wrong. Thank you

How do I enable the disk again? Sent from my iPhone using Tapatalk

I received this error today, I’m not sure what to do. I attached the diagnostics below. Dec 16 00:31:28 Toblerone kernel: print_req_error: I/O error, dev sde, sector 63501512 Dec 16 00:31:28 Toblerone kernel: sd 1:0:0:0: [sde] Synchronizing SCSI cache Dec 16 00:31:28 Toblerone kernel: sd 1:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Sent from my iPhone using Tapatalk toblerone-diagnostics-20201216-0039.zip

Oh ok thanks

Oh i understand now so its nothing I did, its just a bug? Thanks for the help!

What should I do now, do I delete that file?

I don't think I added a ca_profile.xml as an app or container. This just suddenly happened.

When adding a container in docker, I get this: Warning: DOMDocument::load(): Opening and ending tag mismatch: Forum line 9 and Maintainer in /boot/config/plugins/dockerMan/templates/limetech/ca_profile.xml, line: 10 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 238 Warning: DOMDocument::load(): EndTag: '</' not found in /boot/config/plugins/dockerMan/templates/limetech/ca_profile.xml, line: 11 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 238 I'm not sure what this is. So I had tried this fix for an issue I had: but it caused more issues with updating and I reversed the changes and it fixed all the updates not pulling. I'm not sure what the above error is tho.

Alright thank you! Sent from my iPhone using Tapatalk

Thanks for the reply, so I’m able to safely ignore it? Sent from my iPhone using Tapatalk

Hey everyone, I just got this message: Machine Check Events detected on your server Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. I'm not sure where to get mcelog but I went to Tools --> Diagnostics and downloaded the file and attached it here. Any insight on whatever error in my hardware would be greatly appreciated! I attached the file below.toblerone-diagnostics-20200905-0034.zip

Ok thank you for the answer!

Thank you for the answer, I wasn't 100% sure.

Oh ok thanks for the reply. Its not too bad I guess. And I only have a 10tb spare and disk1 is a 8tb, can I replace the 8tb with the 10tb? My parity is already a 10tb

Ok awesome! Is it possible to move the data in disk1 into disk2 so that there's nothing that needs to rebuild in disk1 after I replace it?

And how long is a rebuild for a 8tb drive?

Will it be safer if I just took the drive out and replaced it with a different drive and save the one with the data just in case something goes wrong, or should I be able to just use the same write and rebuild over all the current data?

Ok thank you for the very quick reply.

Hi Everyone! I'm new to Unraid and I'm using the trial at the moment. I made the mistake of adding an external drive as Disk1 and I moved data to it. When I take it out and put it into the computer with a sata cable, it changes the identifier and Unraid marks it as missing. Is there anyway to fix this without having to pull the disk and rebuild it using parity?