Jump to content

(SOLVED) 6.4.0 Spin Down Delay problem or other issue.


skeil909

Recommended Posts

This is a clean 6.4.0 install that's only been running a few days.

ALL drives are set to never spin down. Each drive is individually set to Never and the system settings are globally set to Never. Oddly enough something is still causing the shares to be unavailable for 10-30s every morning and several times throughout the day. I don't remember having this issue with 6.3.5. 

 

Am I missing something?

 

MB - Asus Z9PE-D16

CPU- 2 x Xeon E5-2690

RAM- 64GB ECC

NIC - 10GB MELLANOX CONNECTX-2 PCIe

HDD - 2 x 3TB WD Red (1 parity, 1 data)

HDD - 2 x 3TB Seagate (data)

HDD - 2 x 500GB 850 EVO SSD's (cache pool)

 

Current Plugins

Community Applications

Dynamix SSD Trim

Dynamix System Buttons

Dynamix System Information

Dynamix System Statistics

Dynamix System Temperature

Fix Common Problems

Nerd Tools

Unassigned Devices

 

Current Dockers

binhex-delugevpn

binhex-emby

 

Link to comment
8 minutes ago, Squid said:

Is it the same time every morning?  What does the log show?

 

Nothing in the log and it's been every morning on the 1st use and then random times during the day after periods of non-use.

Jan 14 03:40:11 unRipper root: move: file /mnt/cache/Downloads/Switch IE Proxy.msi
Jan 14 03:40:11 unRipper shfs: set_nocow path: /mnt/cache/domains
Jan 14 03:40:11 unRipper shfs: set_nocow path: /mnt/cache/system
Jan 14 03:40:11 unRipper root: move: skip /mnt/disk1/system/docker/docker.img
Jan 14 03:40:11 unRipper root: move_object: /mnt/disk1/system/docker: Directory not empty
Jan 14 03:40:11 unRipper root: move: skip /mnt/disk1/system/libvirt/libvirt.img
Jan 14 03:40:11 unRipper root: move_object: /mnt/disk1/system/libvirt: Directory not empty
Jan 14 03:40:11 unRipper root: move_object: /mnt/disk1/system: Directory not empty
Jan 14 03:40:11 unRipper root: mover: finished
Jan 14 06:30:06 unRipper root: /etc/libvirt: 1022.5 MiB (1072177152 bytes) trimmed
Jan 14 06:30:06 unRipper root: /var/lib/docker: 17.2 GiB (18458447872 bytes) trimmed
Jan 14 06:30:06 unRipper root: /mnt/cache: 929.7 GiB (998198837248 bytes) trimmed
Link to comment
2 minutes ago, skeil909 said:

 

Nothing in the log and it's been every morning on the 1st use and then random times during the day after periods of non-use.

Try referencing all of your shares / server's on the client PCs based upon their IP address instead of the server's name.  Probably down to Windows / SMB issues.  Referencing via IP usually solves all.  Or peruse the Windows issues with unRaid thread.

Link to comment
54 minutes ago, Squid said:

Try referencing all of your shares / server's on the client PCs based upon their IP address instead of the server's name.  Probably down to Windows / SMB issues.  Referencing via IP usually solves all.  Or peruse the Windows issues with unRaid thread.

 

Using the IP seems to be working much better.

 

Thanks.

Link to comment

Found the actual cause of my issues. SMB 1.0/CIFS Client was turned off.

 

Windows 10

Turn Windows features on or off

SMB 1.0/CIFS File Sharing Support

Enable SMB 1.0/CIFS Client (Was turned off)

 

unRAID now shows up and works fine.

It also fixed a problem with Emby not playing media from the browser. Emby would return an error "no streams available".

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...