26 minutes ago, HagenS said:

Yes. More than an hour since clicking the ball. But never alone before since updating...

The spin down delay for UD devices is the global disk spin down delay.  Maybe you aren't giving it enough time.

Thank you very much for your quick answer

45 minutes ago, dlandon said:

The spin down delay for UD devices is the global disk spin down delay.  Maybe you aren't giving it enough time.

I gave several days - but just the array disks are spinning down (Timeout is 30 Minutes). The unassigned disk is rotating all the time - then i tend to write here to search for help.

48 minutes ago, HagenS said:

I gave several days - but just the array disks are spinning down (Timeout is 30 Minutes). The unassigned disk is rotating all the time - then i tend to write here to search for help.

Post diagnostics.

1 hour ago, dlandon said:

Post diagnostics.

Mailed as PM.

23 hours ago, dlandon said:

Do you have the latest version of UD?  Post diagnostics.

 

Confirmed UD is the latest version, still no automount. Fresh diagnostics after reboot below.skallox-diagnostics-20210307-1211.zip 

11 hours ago, dlandon said:

Are you using Jumbo frames?

 

 

MTU is set to 1500 in unRAID.

Edited March 7, 20215 yr by jlficken

@dlandon 

 

It appears that uninstalling the Cache Dirs plugin stopped the messages.

5 hours ago, skallox said:

 

Confirmed UD is the latest version, still no automount. Fresh diagnostics after reboot below.skallox-diagnostics-20210307-1211.zip 

If this is the disk, it is not marked as auto mount:

Mar  7 12:09:31 Kuroko unassigned.devices: Mounting 'Auto Mount' Devices...
Mar  7 12:09:31 Kuroko unassigned.devices: Disk with serial 'WDC_WD30EFRX-68EUZN0_WD-WMC4N2434274', mountpoint 'temp' is not set to auto mount.

 

3 hours ago, jlficken said:

@dlandon 

 

It appears that uninstalling the Cache Dirs plugin stopped the messages.

Read the message at the top about using cache dirs.

41 minutes ago, dlandon said:

If this is the disk, it is not marked as auto mount:

Mar  7 12:09:31 Kuroko unassigned.devices: Mounting 'Auto Mount' Devices...
Mar  7 12:09:31 Kuroko unassigned.devices: Disk with serial 'WDC_WD30EFRX-68EUZN0_WD-WMC4N2434274', mountpoint 'temp' is not set to auto mount.

 

 

Thank you for digging into my diognostis. I linked that excerpt in my inital post with the below image showing it marked as automount. 

 

So, circling back: Am I missing something? Would using the User Scripts plugin to mount it be an appropriate way to bandaid this issue?

 

2 hours ago, skallox said:

 

Thank you for digging into my diognostis. I linked that excerpt in my inital post with the below image showing it marked as automount. 

 

So, circling back: Am I missing something? Would using the User Scripts plugin to mount it be an appropriate way to bandaid this issue?

 

I think the configuration file may be corrupted.  Can you remove this drive and then remove the disk from the Historical settings?  That should clear the settings and start over.

 

2 hours ago, skallox said:

Would using the User Scripts plugin to mount it be an appropriate way to bandaid this issue?

No.

 

 

 

On 3/6/2021 at 4:36 PM, dlandon said:

Make sure the MTU on all servers is set to default values.  1500 for Unraid.

Well, both of my Unraid installations are 1500.  My router is a Google/Nest Wifi, which is difficult to find documentation for, and which does NOT have adjustable settings

 

Additionally, I have removed and redone the mounts in Unassigned Devices.  It doesn't make a difference.  Also, the other mounts are dropping out randomly now also, not limited to a single mount.

Edited March 8, 20215 yr by mikesp18

18 hours ago, dlandon said:

Read the message at the top about using cache dirs.

 

Yup.  I did and changed it to only include certain shares.

 

Sorry for the trouble!

6 hours ago, mikesp18 said:

Well, both of my Unraid installations are 1500.  My router is a Google/Nest Wifi, which is difficult to find documentation for, and which does NOT have adjustable settings

 

Additionally, I have removed and redone the mounts in Unassigned Devices.  It doesn't make a difference.  Also, the other mounts are dropping out randomly now also, not limited to a single mount.

Are you using cache dirs?  If so, remove it and see if it fixes your issues.

On 3/7/2021 at 6:44 PM, HagenS said:

Mailed as PM.

Did you had any chance to look into the diagnostics to see a cause for blocking spinning down my unassigned backup drive?

1 hour ago, HagenS said:

Did you had any chance to look into the diagnostics to see a cause for blocking spinning down my unassigned backup drive?

Turn off the docker and see if it will spin down.

1 hour ago, dlandon said:

Turn off the docker and see if it will spin down.

It seems that 6.9.1 solves the problem. 

Does anyone know why my VM using 'Unassigned devices' will no longer work after the most recent 6.9.1 update?

 

Disk is pushed using:  /dev/disk/by-id/

The error is keeps referring to /dev/sda2, even though the unassigned disk is /dev/sdc.

 

Running fsck states /dev/sda2 is not existent

 

1 hour ago, DaFr0n said:

Does anyone know why my VM using 'Unassigned devices' will no longer work after the most recent 6.9.1 update?

 

Disk is pushed using:  /dev/disk/by-id/

The error is keeps referring to /dev/sda2, even though the unassigned disk is /dev/sdc.

 

Running fsck states /dev/sda2 is not existent

 

It's very difficult to help you with this limited information.  Please post diagnostics.

4 hours ago, dlandon said:

It's very difficult to help you with this limited information.  Please post diagnostics.

Hi See attached, Cheers

 

Edited March 10, 20215 yr by DaFr0n

1 hour ago, DaFr0n said:

Does anyone know why my VM using 'Unassigned devices' will no longer work after the most recent 6.9.1 update?

 

Disk is pushed using:  /dev/disk/by-id/

The error is keeps referring to /dev/sda2, even though the unassigned disk is /dev/sdc.

 

Running fsck states /dev/sda2 is not existent

 

That disk has errors:

Mar 10 09:07:57 unRAID unassigned.devices: Mount drive command: /sbin/mount -t vfat -o rw,auto,async,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/sdc1' '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part1'
Mar 10 09:07:57 unRAID kernel: FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 10 09:07:57 unRAID unassigned.devices: Successfully mounted '/dev/sdc1' on '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part1'.
Mar 10 09:07:57 unRAID unassigned.devices: Adding disk '/dev/sdc2'...
Mar 10 09:07:57 unRAID unassigned.devices: Mount drive command: /sbin/mount -t ext4 -o rw,auto,noatime,nodiratime,async,nodev,nosuid '/dev/sdc2' '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part2'
Mar 10 09:07:58 unRAID kernel: EXT4-fs (sdc2): warning: mounting fs with errors, running e2fsck is recommended

Click on the check mark when the disk is unmounted and UD will check the disk and fix the error.

 

Why are you using a VFAT file system for a VM?  It would be better to use BTRFS, or XFS.

21 minutes ago, dlandon said:

That disk has errors:

Mar 10 09:07:57 unRAID unassigned.devices: Mount drive command: /sbin/mount -t vfat -o rw,auto,async,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/sdc1' '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part1'
Mar 10 09:07:57 unRAID kernel: FAT-fs (sdc1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 10 09:07:57 unRAID unassigned.devices: Successfully mounted '/dev/sdc1' on '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part1'.
Mar 10 09:07:57 unRAID unassigned.devices: Adding disk '/dev/sdc2'...
Mar 10 09:07:57 unRAID unassigned.devices: Mount drive command: /sbin/mount -t ext4 -o rw,auto,noatime,nodiratime,async,nodev,nosuid '/dev/sdc2' '/mnt/disks/ST1000DM003-1CH162_S1DETV80-part2'
Mar 10 09:07:58 unRAID kernel: EXT4-fs (sdc2): warning: mounting fs with errors, running e2fsck is recommended

Click on the check mark when the disk is unmounted and UD will check the disk and fix the error.

 

Why are you using a VFAT file system for a VM?  It would be better to use BTRFS, or XFS.

 

Sill get the same issue:

 

FS: ext4

/sbin/fsck.ext4 -v -f -p /dev/sdc2 2>&1



/dev/sdc2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
 

 

I only use this VM for Lancache, if i need to reformate due to the above error i will correct, i cant remember setting this originally.

1 minute ago, DaFr0n said:

I only use this VM for Lancache, if i need to reformate due to the above error i will correct, i cant remember setting this originally.

VFAT is not a good choice.  I would reformat the disk.

18 minutes ago, dlandon said:

VFAT is not a good choice.  I would reformat the disk.

Ok, will do. Cheers.

Is there anyway to pull the data first so i dont lose all the cached downloads?

 

Edit....

Got it sorted with:

cp -avr /mnt/disks/ST1000DM003-1CH162_S1DETV80-part2/home/david/lancache /mnt/user/LANCACHE

 

Once complete i will format to XFS and resetup the VM & Lancache

 

Cheers for the quick advise

Edited March 10, 20215 yr by DaFr0n