JieKie

I have the same issue, removed all plugins except for unassigned devices. rolled back to 6.10. I have some dockers using an unassigned drive for downloading. melchior-diagnostics-20221020-1810.rar

thanks, indeed the same issues. For now i have downgraded back to v6.10

melchior-diagnostics-20221020-1810.rar

So it happend again. I can't shut it down. When I ssh into the server and use poweroff i get the "The system is going down for system halt NOW!" but the server keeps running. When I use umout -a it says target is busy for most services

The issue has returned. Can I assume the unassigned devices plugin is causing issues? i'm afraid i can't download the log as the UI pages are mostly unresponsive and i will have to force restart the server. update: managed to snag the logs melchior-diagnostics-20221020-1810.zip

So far so good running only the unassigned devices and unassigned devices plus plugin. Maybe you could try monitoring with only the unassigned devices plugin. If you still have problems you can assume its this plugin.

After a forced reboot i was able to reboot into safe mode. So far i had no more issues, parity check completed. What can i do to determine if a plugin is causing issues?

I will follow this thread as I have the exact same problem for a couple of days now. Dockers themselves work fine, but i cant load the docker page. The server does not respond to shutting down, stopping the array, pausing parity check, even pressing the power button does nothing except for the "beeb". When i close a notification it pops back up after a few seconds. I had to forse shut down, problem cam back. Great server name btw.

Hhm, the ony thing i did since last time i used them (couple of months ago) was adding 2 disks, move the docker file to cache, and maybe an update. Anyway, doesn't matter, glad its ok now, thanks again.

Got it back up and running again. How is it possible this changed? My network always has been 192.168.0.0/24. I've been using these dockers for over a year, always worked. thanks a lot for the help

It's from different devices, different browsers, all in the same range. It's on DHCP but right now it's 192.168.0.20. Unraid is fixed. I tried clearing cache, incognito, etc..

it's briged

My apologies, added the log. So in short, I can't get into the UI (same for qbittorrentvpn an rtorrentvp. the regular binhex deluge works fine) supervisord.log

I have the same problem, none of the binhex vpn torrent clients seem to work. I tried removing these IP's but the problem is percisting.

Yeah, kind of. Ok, then everything checks out as it should be, nothing to worry about (except finding a new spot for my server, my little toddler is fascinated by flashing lights). I expected to just pop it back in and continue with my day. Thanks for the quick help and info!

So, turns out my kid opened the hotswap bay whilst playing. I popped it back in, but unraid couldn't find the disk. I was able to add it as a "new" one. I'ts currently rebuilding onto the same old disk. This can't be right no? melchior-diagnostics-20220126-2122.zip

Hi, So I just got my first ever hard drive failure. I got an alert saying one of my drives had errors. Took a look at the array and saw one drive was emulated. I checked the logs and found this: Jan 26 19:27:37 MELCHIOR kernel: md: disk2 read error, sector=10903897736 Jan 26 19:27:38 MELCHIOR kernel: md: disk2 write error, sector=10903897736 This is what the Disk Logs says: Dec 28 13:36:30 MELCHIOR kernel: mdcmd (3): import 2 sde 64 11718885324 0 WDC_WD120EMFZ-11A6JA0_9RJ64SWL Dec 28 13:36:30 MELCHIOR kernel: md: import disk2: (sde) WDC_WD120EMFZ-11A6JA0_9RJ64SWL size: 11718885324 Dec 28 13:36:30 MELCHIOR emhttpd: read SMART /dev/sde Jan 26 19:09:51 MELCHIOR kernel: sd 8:0:0:0: [sde] Synchronizing SCSI cache Jan 26 19:09:51 MELCHIOR kernel: sd 8:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 I can't seem to be able to start a SMART self test. Its a chucked WD 12TB, running about 1,5 years. I'm rocking version 6.9.2 with 2 parity drives. The drive itself is pretty full, 94%. I've got a spare 12TB lying around. Should I start preclearing it an replace the failed drive? Or can i check something else first? regards,

Hi everyone, It's my first post here, i've been using unraid for about half a year now and enjoying it. When i built the server i used a generic unbranded usb drive and a SSD with bad sectors. Not the best idea but i wanted to test unraid, had these laying around and now i'm stuck with these. I'm also running 6 6TB WD reds (1 parity) which i will be replacing with 8 12TB drives (shucked WD white label) (2 parity drives). I'm also looking into encrypting my data, but i'm still on the fence, it's mainly movies, shows, music and console games. What would be the best course of action? Replace the flash drive and SSD and gradually rebuild the hard drives? Or replace all drives, remove the config, add the old drives as unassigned drives and copy everything from the old hard drives to the new drives or maybe chuck them into my computer and transfer over the network? This way if something goes wrong i can rebuild the old setup. I could also add encryption, not sure on this as its just mostly media. my current setup: Supermicro X10SL7-F Intel® Core™ i3-4330 32 GiB DDR3 Single-bit ECC generic unbranded 16Gb flash drive CacheCorsair Force 3 SSD 120Gb with bad sectors as cache drive 6 x 6TB WD red (1 parity) future setup: sandisk cruzer mini 16Gb 2 x Samsung 860 QVO 1TB as cache raid 1 8 x 12TB WD white label (precleared) (2 parity) For now i'm using the server as a NAS, but in the future i will experiment with dockers and vm's. regards,