Another full log post

[dbinott]

/var/log is getting full (currently 100 % used)

 

I recently swapped out 3 cache sdd's for 1x2TB SSD.

I added a 6TB drive to the array.

Is /var/log a directory or a file? When I go I see a directory and files are far from large.

found answer about log here https://wiki.unraid.net/Viewing_the_System_Log

 

Any help appreciated. Thanks.

predator-diagnostics-20200107-2034.zip

Edited January 7, 2020 by dbinott

[trurl]

The full log is just a trivial side effect of the fact that you have problems with multiple disks. Messages about those are what has filled your log.

 

Likely a result of the disk changes you made. Shutdown, double check all connections, power and SATA, both ends, including any power splitters.

 

When you reboot the log will be gone, that minor problem solved for now.

 

I didn't dig much deeper into your diagnostics so maybe you have other things that are less than ideal but let's deal with these major issues first.

[dbinott]

Thanks. Unfortunately the server is remote. Not far, but still have to go there. Will do that first chance I get.

[JorgeB]

These errors are caused by Unraid trying to spin down the disks, which isn't supported by Unraid on SAS disks:

 

Jan  7 04:40:51 Predator kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan  7 04:40:51 Predator kernel: mdcmd (398858): spindown 3
Jan  7 04:40:51 Predator kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5
Jan  7 04:40:51 Predator kernel: mdcmd (398859): spindown 4

 

Set spin down to never.

[dbinott]

Oh, thank you. Yes, I just set that actually.