Wisnaeme

Hi all, I use Uptime Robot (UR) for a few projects and want to monitor Unraid by sending a ping/connect to the server and see if I get a response. Currently I use UR to reach out to the internal FTP server (Yeah I know) which replies and all is good. Problem is that the internal FTP server is not considered safe. What do you suggest as the lightest way to get a "I'm alive" packet back to UR? All we need to do is reply to an inbound connect request and nothing more. Ta!

Hmm. Thanks. I was sure the other server had SAS powerdown capability. I'll need to check later.

Hi, When trying to spindown the drives I have one that just refuses and throws an error. Any suggestions? I see some historic posts on this but they all say it was fixed and mostly related to removable USB HDD's. This is internal SAS. Logs and details below: Unraid: Version: 6.8.3 Controller is: Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Drive is: [1:0:0:0]disk HGST HUS726040ALS211 BD05 /dev/sdb 4.00TB SCSI Devices [0:0:0:0]disk /dev/sda 8.08GB [1:0:0:0]disk HGST HUS726040ALS211 BD05 /dev/sdb 4.00TB [1:0:1:0]disk HGST SDLL1DLR480GCDA1 X130 /dev/sdc 480GB [1:0:2:0]disk ATA WDC WD30EFRX-68E 0A82 /dev/sdd 3.00TB [1:0:3:0]disk ATA WDC WD40PURZ-85T 0A80 /dev/sde 4.00TB [1:0:4:0]disk ATA WDC WD30EFRX-68E 0A80 /dev/sdf 3.00TB System Log: Jun 29 06:59:15 ADAM emhttpd: error: mdcmd, 2723: Input/output error (5): write Jun 29 06:59:15 ADAM kernel: mdcmd (66315): spindown 1 Jun 29 06:59:15 ADAM kernel: mdcmd (66316): spindown 2 Jun 29 06:59:15 ADAM kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5 Jun 29 06:59:15 ADAM kernel: mdcmd (66317): spindown 3 Jun 29 06:59:16 ADAM emhttpd: shcmd (277): /usr/sbin/hdparm -y /dev/sdc Jun 29 06:59:16 ADAM root: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 18 00 00 00 00 20 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Jun 29 06:59:16 ADAM root: Jun 29 06:59:16 ADAM root: /dev/sdc: Jun 29 06:59:16 ADAM root: issuing standby command Jun 29 06:59:17 ADAM emhttpd: error: mdcmd, 2723: Input/output error (5): write Jun 29 06:59:17 ADAM kernel: mdcmd (66318): spindown 2 Jun 29 06:59:17 ADAM kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5 Jun 29 06:59:18 ADAM kernel: mdcmd (66319): spindown 2 Jun 29 06:59:18 ADAM emhttpd: error: mdcmd, 2723: Input/output error (5): write Jun 29 06:59:18 ADAM kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5

Thanks for that. I just installed a fresh PRO version of windows 10 (1909) and had exactly the same issue, and fix. I wish Microsoft would get consistent with things like this. I fresh installed another machine last week from the same image and it worked just fine. Both are Lenovo machines, T460s and T470s. Thanks again!

Ok. This is weird. After posting I had a wee snooze.. Just woke up 2hours later to your posts. Home assistant is working. I shut it down and started it and it came online instantly. I've no idea what changed. Thanks to those that posted. On second thoughts.... It updated and fixed itself? Didn't work for me earlier... Oh well... ---Event: Community Applications ---Subject: Docker Auto Update ---Description: home-assistant Automatically Updated ---Importance: normal

I'm terrible at reading these logs and making any sense of them so I copy them below. Does anyone have any ideas? Log for_ home-assistant.html

I just tried the exact same with the same result. Not sure of a work around but it would be good to have Unraid capable of recording from this camera.

Not sure if this is new, but the logging is not currently reflecting the selected Timezone.

I lost access to my server for about an hour while I sorted these broken settings after update to 672. Changed after install Network name Custom UI Port Workgroup name SSL/TLS from OFF to AUTO All TIME settings. FTP re-enabled Not what I really wanted to start fixing after a long day. The other server can wait.

Here we are 3 hours into a Parity check... A full Smart test came back clean too.

Hi, Here's a snapshot of something that started today. I'm getting temperature warnings from one of my disks for no obvious reason. I've checked the hardware and it's cold. Has anyone seen this behaviour before? Not sure if it's Unraid or the drive going crazy. Not had a good time to reboot yet. One reading... Ten seconds later... The drive does seem to be aging though so probably best replaced soon anyway...

I just had the same issue. I stopped the docker, changed the docket storage size from 20GB to 40GB and restarted it. Everything worked at that point and the error is gone. Is there any way to find out what actually caused this problem? Is there a way to find out what is taking up all the storage? When check the container size now it shows that there should not have been a space problem. I most recently installed the MQTT and Home Assistant dockers around three weeks ago.

Suddenly Fix Common Problems is reporting this: "Unable to communicate with GitHub.comReset your modem / router or try again later, or set your DNS settings to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Router's IP address). Additionally, this may also mean that GitHub is currently down. This error means that you may not be able to update your OS or plugins" I'm not aware of any issues with my DNS, I use OpenDNS with 6.6.5 . I can use the Apps tab, Update checks all seems fine. No symptoms of any issues, except this message. Random App download and install is fine. Is it just me? Any suggestions on how to test further to see if the error is real or a mistake? Thanks Robertv!

Just installed this and it works perfectly for my Trust Oxxtron 1500VA UPS and it works well. Always struggled with PC software for this UPS so glad I can get it working on my Unraid box. Thanks for the work. Showing as: USB DEVICE: Bus 001 Device 003: ID 0925:1234 Lakeview Research Screenshot is for anyone else struggling with this UPS.

Just setting up a new server and I'm having this issue currently, see image. I need to open the terminal and "Reboot" the server to resume operation of the GUI. The system still responds to shares and VM's as expected. Anyone got a suggestion for this?