Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array


dlandon

5807 posts in this topic Last Reply

Recommended Posts

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.

Link to post
  • Replies 5.8k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

New release of UD.  Changes: When changing the mount point (which is also the share name), the mount point is checked for a duplicate of a user share or another UD device.  Samba cannot handle

While I appreciate your interest in esthetics, there is more to consider than just 'aligning' disk drive mounts: This disk is mounted without a UD script, it is probably better to put it in th

<step on soap box> Keep in mind that the Unraid array disk configuration is static and doesn't change until it is stopped.  UD has to deal with hot plugged disks, devices being dynamically

Posted Images

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.

Link to post
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 by DaFr0n
Link to post

Not sure what happened, but all of a sudden my share is only showing 1mb in size.  Yet, the drive in unassigned devices is showing 4tb.  Uninstalling/reinstalling the plugin did nothing.  Tried restoring Appdata from a previous backup (No change either).  I've been using the drive as a location for downloads and transcodes.

 

Ran a SMART test and everything passed.

This is what is showing currently:

 

image.thumb.png.01754e8ed64a5882c3f2cba1d84daca4.png

 

File System Check results:

image.png.36be6f04bf141f9230597b1e2b46dffe.png

 

when I navigate to the share in VNC, it is showing 1mb in size and I can go into the folder(s).  However, I can no longer create anything in there.  It is acting like the share is corrupt, but not sure how I can recreate it.

 

image.png.9b39b5c28dfcb865f5efe285b158bef1.png

Link to post
5 hours ago, dlandon said:

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

Well i reformatted and managed to copy my cached games before formatting, formatted as ext4 and created a new VM. After VM restart its changed back to vfat with a ext4 partition.

Never used to do this?

 

error.PNG

Link to post

Hi I upgraded from 6.8.3 to 6.9.1 then upgraded all my plugins to latest version. Now when I use unassigned devices, my USB drives will not unmount. The log shows that the unmount is taking place but the device is never actually unmounted. UD also still reports the device is mounted. Subsequent clicks of the unmount button result in error in log. UD just refreshes back and still displays the unmount button.

 

Syslog

1. Attaching USB hub with flash drive. (Mar 10 00:22:37)

2. Mounting partition (Mar 10 00:23:58)

2. Copying files.

3. Clicking unmount on unassigned devices. (Mar 10 00:28:49)

4. Clicking it again ~20 minutes later. (Mar 10 00:47:40)

Spoiler

Mar 10 00:22:37 Tower kernel: usb 3-12: USB disconnect, device number 4
Mar 10 00:23:37 Tower kernel: usb 3-12: new high-speed USB device number 7 using xhci_hcd
Mar 10 00:23:37 Tower kernel: hub 3-12:1.0: USB hub found
Mar 10 00:23:37 Tower kernel: hub 3-12:1.0: 4 ports detected
Mar 10 00:23:37 Tower kernel: usb 3-12.3: new high-speed USB device number 8 using xhci_hcd
Mar 10 00:23:37 Tower kernel: usb-storage 3-12.3:1.0: USB Mass Storage device detected
Mar 10 00:23:37 Tower kernel: scsi host2: usb-storage 3-12.3:1.0
Mar 10 00:23:38 Tower kernel: scsi 2:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] 122552320 512-byte logical blocks: (62.7 GB/58.4 GiB)
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Mar 10 00:23:38 Tower kernel: sdc: sdc1
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk
Mar 10 00:23:38 Tower unassigned.devices: Disk with serial 'Extreme_4C530001010308101401', mountpoint 'Flash' is not set to auto mount.
Mar 10 00:23:58 Tower emhttpd: SanDisk_Extreme_4C530001010308101401-0:0 (sdc) 512 122552320
Mar 10 00:23:58 Tower emhttpd: read SMART /dev/sdc
Mar 10 00:24:03 Tower unassigned.devices: Adding disk '/dev/sdc1'...
Mar 10 00:24:03 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o rw,auto,async,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdc1' '/mnt/disks/Flash'
Mar 10 00:24:06 Tower ntfs-3g[37851]: Version 2017.3.23 integrated FUSE 27
Mar 10 00:24:06 Tower ntfs-3g[37851]: Mounted /dev/sdc1 (Read-Write, label "Flash", NTFS 3.1)
Mar 10 00:24:06 Tower ntfs-3g[37851]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000
Mar 10 00:24:06 Tower ntfs-3g[37851]: Mount options: rw,nodiratime,nodev,nosuid,nls=utf8,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sdc1,blkdev,blksize=4096
Mar 10 00:24:06 Tower ntfs-3g[37851]: Global ownership and permissions enforced, configuration type 1
Mar 10 00:24:06 Tower unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). The file system wasn't safely closed on Windows. Fixing. 
Mar 10 00:24:06 Tower unassigned.devices: Successfully mounted '/dev/sdc1' on '/mnt/disks/Flash'.
Mar 10 00:28:49 Tower unassigned.devices: Unmounting disk 'Flash'...
Mar 10 00:28:49 Tower unassigned.devices: Unmounting '/dev/sdc1'...
Mar 10 00:28:49 Tower unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdc1' 2>&1
Mar 10 00:28:49 Tower ntfs-3g[37851]: Unmounting /dev/sdc1 (Flash)


Mar 10 00:47:40 Tower unassigned.devices: Unmounting disk 'Flash'...
Mar 10 00:47:40 Tower unassigned.devices: Unmounting '/dev/sdc1'...
Mar 10 00:47:40 Tower unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdc1' 2>&1
Mar 10 00:47:40 Tower unassigned.devices: Unmount of '/dev/sdc1' failed. Error message: umount: /mnt/disks/Flash: not mounted. 
 

 

mount 

root@Tower:~# mount
/dev/sdc1 on /mnt/disks/Flash type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)

 

umount

root@Tower:~# umount /mnt/disks/Flash/
umount: /mnt/disks/Flash: not mounted.

 

 

lsof returns blank - nothing open in that mount path

 

I have tried everything I can think of.

Different Flash drives

With/without a USB hub

Different ports

Different formats

Waiting several hours (in case cached data was still being written)

Rebooting (if unmount was pressed, the will system now hang unless USB drive physically removed)

 

It also worth mentioning at this when it is stuck unmounting I cannot stop the array. Unraid gets hung at the filesystem sync step waiting.

I have not found a command successful in force this drive to be ejected so I have resorted to manually unplugging it which then allows unraid to resume with stopping the array.

 

Any ideas what's going on. Thanks.

 

Edited by taychive
Link to post
7 minutes ago, DaFr0n said:

Well i reformatted and managed to copy my cached games before formatting, formatted as ext4 and created a new VM. After VM restart its changed back to vfat with a ext4 partition.

Never used to do this?

 

error.PNG

 

The disk was likely GPT formatted with the vfat 200mb partition left on it. This partition is normally only needed for bootable media, i.e. it's commonly used for the EFI partition on UEFI bootable devices. You can unmount the drive and then you can click on the red 'X' beside the vfat partition to remove it. To be entirely safe, you may want to backup your drive again, remove both partitions, re-format and then re-copy your required data. Note that when you reformat, if the disk is going to be for data storage only, you can change it from GPT to MBR so you'll only have 1 partition. You'll likely want to do the formatting using a partition tool on Windows, Disk Utility on a Mac or Disks on a Linux system.

 

 

 

 

Link to post
3 minutes ago, AgentXXL said:

 

The disk was likely GPT formatted with the vfat 200mb partition left on it. This partition is normally only needed for bootable media, i.e. it's commonly used for the EFI partition on UEFI bootable devices. You can unmount the drive and then you can click on the red 'X' beside the vfat partition to remove it. To be entirely safe, you may want to backup your drive again, remove both partitions, re-format and then re-copy your required data. Note that when you reformat, if the disk is going to be for data storage only, you can change it from GPT to MBR so you'll only have 1 partition. You'll likely want to do the formatting using a partition tool on Windows, Disk Utility on a Mac or Disks on a Linux system.

 

 

 

 

My Ubuntu VM uses the HDD directly, assume this is why it has bootable partitions?

/dev/disk/by-id.......... etc

Link to post
1 minute ago, DaFr0n said:

My Ubuntu VM uses the HDD directly, assume this is why it has bootable partitions?

/dev/disk/by-id.......... etc

 

It only needs the bootable partition if your VM is setup to use it for booting. If it's just for data, that 200mb partition is not required.

 

Link to post
1 minute ago, AgentXXL said:

 

It only needs the bootable partition if your VM is setup to use it for booting. If it's just for data, that 200mb partition is not required.

 

Cheers Assume its required then as its the only disk directly assigned to the VM :)

 

Link to post

I think the temperature monitoring notifications are broken for Unassigned device plugin.  I am constantly getting notificaitons for my unassigned NVME drive reaching temperatures over 45 degrees, but Ive changed it to only notify at 50 or higher.  This behavior does NOT happen with any of the drives in the array.  They all notify me properly at 50c or higher after I changed their values. 

Link to post
9 hours ago, Kreavan said:

Not sure what happened, but all of a sudden my share is only showing 1mb in size.  Yet, the drive in unassigned devices is showing 4tb.  Uninstalling/reinstalling the plugin did nothing.  Tried restoring Appdata from a previous backup (No change either).  I've been using the drive as a location for downloads and transcodes.

The disk is not mounted.  Because the mount points are in ram and incorrect mappings can cause ram to fill, there is a protection on the mount point /mnt/disks and it is limited to 1MB.  You are not really seeing the UD disk you think you are,

 

You need to find out why the disks aren't mounted and get them mounted.

Link to post
6 hours ago, taychive said:

Hi I upgraded from 6.8.3 to 6.9.1 then upgraded all my plugins to latest version. Now when I use unassigned devices, my USB drives will not unmount. The log shows that the unmount is taking place but the device is never actually unmounted. UD also still reports the device is mounted. Subsequent clicks of the unmount button result in error in log. UD just refreshes back and still displays the unmount button.

 

Syslog

1. Attaching USB hub with flash drive. (Mar 10 00:22:37)

2. Mounting partition (Mar 10 00:23:58)

2. Copying files.

3. Clicking unmount on unassigned devices. (Mar 10 00:28:49)

4. Clicking it again ~20 minutes later. (Mar 10 00:47:40)

  Reveal hidden contents

Mar 10 00:22:37 Tower kernel: usb 3-12: USB disconnect, device number 4
Mar 10 00:23:37 Tower kernel: usb 3-12: new high-speed USB device number 7 using xhci_hcd
Mar 10 00:23:37 Tower kernel: hub 3-12:1.0: USB hub found
Mar 10 00:23:37 Tower kernel: hub 3-12:1.0: 4 ports detected
Mar 10 00:23:37 Tower kernel: usb 3-12.3: new high-speed USB device number 8 using xhci_hcd
Mar 10 00:23:37 Tower kernel: usb-storage 3-12.3:1.0: USB Mass Storage device detected
Mar 10 00:23:37 Tower kernel: scsi host2: usb-storage 3-12.3:1.0
Mar 10 00:23:38 Tower kernel: scsi 2:0:0:0: Direct-Access     SanDisk  Extreme          1.00 PQ: 0 ANSI: 6
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] 122552320 512-byte logical blocks: (62.7 GB/58.4 GiB)
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Mar 10 00:23:38 Tower kernel: sdc: sdc1
Mar 10 00:23:38 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk
Mar 10 00:23:38 Tower unassigned.devices: Disk with serial 'Extreme_4C530001010308101401', mountpoint 'Flash' is not set to auto mount.
Mar 10 00:23:58 Tower emhttpd: SanDisk_Extreme_4C530001010308101401-0:0 (sdc) 512 122552320
Mar 10 00:23:58 Tower emhttpd: read SMART /dev/sdc
Mar 10 00:24:03 Tower unassigned.devices: Adding disk '/dev/sdc1'...
Mar 10 00:24:03 Tower unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o rw,auto,async,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sdc1' '/mnt/disks/Flash'
Mar 10 00:24:06 Tower ntfs-3g[37851]: Version 2017.3.23 integrated FUSE 27
Mar 10 00:24:06 Tower ntfs-3g[37851]: Mounted /dev/sdc1 (Read-Write, label "Flash", NTFS 3.1)
Mar 10 00:24:06 Tower ntfs-3g[37851]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000
Mar 10 00:24:06 Tower ntfs-3g[37851]: Mount options: rw,nodiratime,nodev,nosuid,nls=utf8,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sdc1,blkdev,blksize=4096
Mar 10 00:24:06 Tower ntfs-3g[37851]: Global ownership and permissions enforced, configuration type 1
Mar 10 00:24:06 Tower unassigned.devices: Mount warning: The disk contains an unclean file system (0, 0). The file system wasn't safely closed on Windows. Fixing. 
Mar 10 00:24:06 Tower unassigned.devices: Successfully mounted '/dev/sdc1' on '/mnt/disks/Flash'.
Mar 10 00:28:49 Tower unassigned.devices: Unmounting disk 'Flash'...
Mar 10 00:28:49 Tower unassigned.devices: Unmounting '/dev/sdc1'...
Mar 10 00:28:49 Tower unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdc1' 2>&1
Mar 10 00:28:49 Tower ntfs-3g[37851]: Unmounting /dev/sdc1 (Flash)


Mar 10 00:47:40 Tower unassigned.devices: Unmounting disk 'Flash'...
Mar 10 00:47:40 Tower unassigned.devices: Unmounting '/dev/sdc1'...
Mar 10 00:47:40 Tower unassigned.devices: Unmount cmd: /sbin/umount '/dev/sdc1' 2>&1
Mar 10 00:47:40 Tower unassigned.devices: Unmount of '/dev/sdc1' failed. Error message: umount: /mnt/disks/Flash: not mounted. 
 

 

mount 


root@Tower:~# mount
/dev/sdc1 on /mnt/disks/Flash type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)

 

umount


root@Tower:~# umount /mnt/disks/Flash/
umount: /mnt/disks/Flash: not mounted.

 

 

lsof returns blank - nothing open in that mount path

 

I have tried everything I can think of.

Different Flash drives

With/without a USB hub

Different ports

Different formats

Waiting several hours (in case cached data was still being written)

Rebooting (if unmount was pressed, the will system now hang unless USB drive physically removed)

 

It also worth mentioning at this when it is stuck unmounting I cannot stop the array. Unraid gets hung at the filesystem sync step waiting.

I have not found a command successful in force this drive to be ejected so I have resorted to manually unplugging it which then allows unraid to resume with stopping the array.

 

Any ideas what's going on. Thanks.

 

Post diagnostics.

Link to post
3 hours ago, 007craft said:

I think the temperature monitoring notifications are broken for Unassigned device plugin.  I am constantly getting notificaitons for my unassigned NVME drive reaching temperatures over 45 degrees, but Ive changed it to only notify at 50 or higher.  This behavior does NOT happen with any of the drives in the array.  They all notify me properly at 50c or higher after I changed their values. 

Nvme drives can spike to a high temperature under a heavy load and Unraid doesn't update the displayed temperature very often.  In between the display refreshes, the temperature is probably spiking and you aren't seeing it, but it is going over the threshold.

 

I have mine set to 65C.

Link to post
10 hours ago, xrqp said:

In Unraid, or in UD, can we merge partitions without losing data?

 

Or can it merge partitions and wipe clean only one partition?

No.  Unraid doesn't have built in partition management tools like windows.  You'll need to copy the data from the two partitions, remove all partitions, format the drive, then copy all back.

Link to post
13 hours ago, dlandon said:

The disk is not mounted.  Because the mount points are in ram and incorrect mappings can cause ram to fill, there is a protection on the mount point /mnt/disks and it is limited to 1MB.  You are not really seeing the UD disk you think you are,

 

You need to find out why the disks aren't mounted and get them mounted.

 

I went in and disabled "Passthrough" in order to re-enable the option to "Mount."  When I tried, it immediately fails.  Checked the log and this is what is showing.

 

image.thumb.png.bcca53b25878c6fd694959021821a117.png

Link to post
34 minutes ago, Kreavan said:

 

I went in and disabled "Passthrough" in order to re-enable the option to "Mount."  When I tried, it immediately fails.  Checked the log and this is what is showing.

 

image.thumb.png.bcca53b25878c6fd694959021821a117.png

 

Since I didn't really have anything on that drive needing to be recovered, I wiped the partion, re-formatted, and it's back up and running again.  Still unsure what happened, but all good now.

 

Thanks for the help folks!

Link to post
7 hours ago, Kreavan said:

 

Since I didn't really have anything on that drive needing to be recovered, I wiped the partion, re-formatted, and it's back up and running again.  Still unsure what happened, but all good now.

 

Thanks for the help folks!

Passed Through means that the Docker is taking control of the disk directly and UD should not mount it.  That's why the 'Mount' button was grayed out.  If the Docker mounts the disk and UD mounts it also, you will get a corrupted file system,  The way you were referencing the disk in your Docker assumed that UD mounted it.  When the disk is Passed Through to the Docker, you deal with it differently in the Docker.

 

Anyway, glad you got it sorted out.

Link to post
7 hours ago, alitech said:

Hello

 

Has anyone noticed this on their MAIN dashboard?

 

image.thumb.png.689afb30f0e1b0f90536ff41ca858b98.png

Go to a command line and post the contents of this file '/var/state/unassigned.devices/unassigned.devices.ini'

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.