andyd

Looks like it's there. "apps" which is not showing up under the plugin

Thanks for the plugin! I set this up today - it picks up one of the pool drives but I have two formatted with zfs. Any reason the one would be ignored

Ok got it. I used the remote ip option and immediately see logs now. Thanks!

Ok I enabled the last option but I'm a little confused based on the help box that appears when clicking it - what's the point of the top part if I need the bottom as well? Is it that whatever is recorded on the flash drive will be moved to local syslog server periodically?

I have Syslog set up as shown below. If I check the share, there is nothing in it. I have this share on a ssd - that ssd has a logs folder, also nothing in it. Is there an issue with the configuration?

Somehow I got into the state where I can't move the domains folder back to the cache drive from the Array. Secondary storage doesn't give me any other option but a grayed out Array selection. Any way to fix this?

Ah makes sense .. that fixed it. Not sure why that was set to no since it was working before but all good now. Thanks!

I have not made any changes to this recently besides moving everything to a new server. Settings...

Hi. All of sudden the share on my unassigned drive is not showing up even though the drive is mounted. Any reason this may occur?

Yep - just ran into this issue - doesn't work in Chrome but does in Edge

It's on a different power connection as well - I swapped it into an entirely different position where all cables to it were different. Oh the RMA was already approved. I just have to pay the $25 for an advanced replacement though I guess I don't need to do advanced anymore since I already removed the drive from the array hmm

Well, ruled out cables and loose connectors unless the connectors can also be the ones on the drive. And I get 1 or 2 - it's happened at least 5 times till the last time where the drive was then disabled because of write error. I guess my concern is that my drive is still under warranty for another 6 months - is it worth the risk ignoring the errors and having to keep acknowledging / dealing with a disabled drive??

Sorry just getting back to this as I had taken out the drive and replaced it with a new larger drive... 1. The new drive is using the same cables that the original CRC error drive was on - no issues so far 2. After going through some set up stuff I wanted to do, I added back the original drive to get it back onto the array - so different cables / sata port. Immediately after starting the server I got a message about CRC error count on the original drive. And yeah, CRC warnings is something that I've been seeing since last year on this drive and I kept acknowledging the error. The write error and then disabling of the drive was the first time of seeing that happen. Seems like something is up with the drive? Considering the change in cables / port. But yeah SMART doesn't report any issues.

Yes exactly - I shrunk the array using a new config and rebuilt the parity afterwards. I moved the data still on the drive back onto the array then formatted to be used as an unassigned device

lol figured it out ... i had terminal windows opened and that was blocking the stop

Oh this is a completely separate issue - not related to the thread but it is a continuation of what I'm doing... 1. Removed a smaller drive from the array that was functioning properly but had data that I wanted 2. Drive not in array anymore 3. Moved the data from that drive back onto the array 4. Array is fine now / no data issues I now want to format that drive / erase all data on it as I will replace another smaller drive I keep around as an unassigned device homeserver-diagnostics-20220315-2038.zip

I was trying to format this drive after removing it from the array. To do so, I tried to stop the array which is now stuck with... `Retry unmounting user share` How do I force the unmount on the drive? Afraid to power down server and lead to data loss

So I swapped out the drive with a new larger drive - no CRC errors using the same cables etc. Could the connectors on the drive be problematic? I will soon add the drive back into the array

Yeah, I still had the data and moved it over. I'll probably use Unbalance next time

So I missed this important bullet point when removing a drive from an array... "This method does not keep the drive's data within the array." I am to blame but also I don't really understand why removing a drive is not a simpler procedure where I don't have to worry about this issue. Now that the drive is removed and the parity is being rebuilt - do I just mount this drive and move over the data from the removed drive? I do not want to lose the data on this drive.

Ok I'll check this weekend again

Attaching. While I understand the connection issue, this is a replacement drive...the previous drive on the same connection had no issues. I swapped out the cable to be sure as well logs.zip

For some time I've been seeing this error... UDMA CRC error count For a few months. Yesterday was the first time I got a write failed and the drive was disabled as you mentioned. I've already tried swapping out the cable / making sure everything is ok. This is also a refurb drive sent as a replacement for another drive that failed.

I am going to RMA the drive but it will take longer than a week to receive the replacement. I also placed an order on Amazon for a larger drive but that will take a week as well since they don't currently have inventory. Is it safer to remove the drive now? I have enough space to allow for the drive to be removed

pkill fails to run in the container kill doesn't return an error but the service seems to keep restarting has anyone able to successfully shut down the service in order to make db updates?