6 minutes ago, dlandon said:

That is not supposed to happen on USB devices.  Please post diagnostics and I will run a few tests to see if I can find out what's going on.

 

Thanks :

tower-diagnostics-20220122-1153.zip

5 minutes ago, deadnote said:

Thanks :

 

I need to see two files.  Post the results of the following commands:

cat /usr/local/emhttp/state/devs.ini
cat /var/state/unassigned.devices/unassigned.devices.ini

 

The second one will be fairly large.  It would be best to zip them and post the zip file.

4 minutes ago, dlandon said:

 

I need to see two files.  Post the results of the following commands:

cat /usr/local/emhttp/state/devs.ini
cat /var/state/unassigned.devices/unassigned.devices.ini

 

The second one will be fairly large.  It would be best to zip them and post the zip file.

root@Tower:~# cat /usr/local/emhttp/state/devs.ini
["dev1"]
name="dev1"
id="ST5000LM000-2AN170_WCJ0QEH3"
device="sde"
sectors="9767541167"
sector_size="512"
rotational="1"
spundown="0"
temp="*"
numReads="0"
numWrites="0"
root@Tower:~# cat /var/state/unassigned.devices/unassigned.devices.ini

[/dev/disk/by-id/ata-ST5000LM000-2AN170_WCJ0QEH3]
DEVLINKS = "/dev/disk/by-id/ata-ST5000LM000-2AN170_WCJ0QEH3 /dev/disk/by-id/wwn-0x5000c500b999fee4 /dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0"
DEVNAME = "/dev/sdf"
DEVPATH = "/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/host8/target8:0:0/8:0:0:0/block/sdf"
DEVTYPE = "disk"
ID_ATA = 1
ID_ATA_DOWNLOAD_MICROCODE = 1
ID_ATA_FEATURE_SET_APM = 1
ID_ATA_FEATURE_SET_APM_CURRENT_VALUE = 128
ID_ATA_FEATURE_SET_APM_ENABLED = 1
ID_ATA_FEATURE_SET_HPA = 1
ID_ATA_FEATURE_SET_HPA_ENABLED = 1
ID_ATA_FEATURE_SET_PM = 1
ID_ATA_FEATURE_SET_PM_ENABLED = 1
ID_ATA_FEATURE_SET_PUIS = 1
ID_ATA_FEATURE_SET_PUIS_ENABLED = 0
ID_ATA_FEATURE_SET_SECURITY = 1
ID_ATA_FEATURE_SET_SECURITY_ENABLED = 0
ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN = 66356
ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN = 66356
ID_ATA_FEATURE_SET_SMART = 1
ID_ATA_FEATURE_SET_SMART_ENABLED = 1
ID_ATA_ROTATION_RATE_RPM = 5526
ID_ATA_SATA = 1
ID_ATA_SATA_SIGNAL_RATE_GEN1 = 1
ID_ATA_SATA_SIGNAL_RATE_GEN2 = 1
ID_ATA_WRITE_CACHE = 1
ID_ATA_WRITE_CACHE_ENABLED = 1
ID_BUS = "ata"
ID_MODEL = "ST5000LM000-2AN170"
ID_MODEL_ENC = "ST5000LM000-2AN170\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20"
ID_PART_TABLE_TYPE = "gpt"
ID_PART_TABLE_UUID = "f8fc2d4c-97ad-4e41-91bf-0eb0c542d645"
ID_PATH = "pci-0000:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0"
ID_PATH_TAG = "pci-0000_00_1a_0-usb-0_1_2_1_0-scsi-0_0_0_0"
ID_REVISION = 0001
ID_SERIAL = "ST5000LM000-2AN170_WCJ0QEH3"
ID_SERIAL_SHORT = "WCJ0QEH3"
ID_TYPE = "disk"
ID_WWN = "0x5000c500b999fee4"
ID_WWN_WITH_EXTENSION = "0x5000c500b999fee4"
MAJOR = 8
MINOR = 80
SUBSYSTEM = "block"
USEC_INITIALIZED = 3021988604199

[/dev/disk/by-id/ata-ST5000LM000-2AN170_WCJ0QEH3-part2]
DEVLINKS = "/dev/disk/by-id/ata-ST5000LM000-2AN170_WCJ0QEH3-part2 /dev/disk/by-id/wwn-0x5000c500b999fee4-part2 /dev/disk/by-label/Unraid\x20Backup /dev/disk/by-partlabel/Basic\x20data\x20partition /dev/disk/by-partuuid/57e72313-abd7-478e-bd40-2fffe570c653 /dev/disk/by-path/pci-0000:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0-part2 /dev/disk/by-uuid/A0286E45286E1B14"
DEVNAME = "/dev/sdf2"
DEVPATH = "/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/host8/target8:0:0/8:0:0:0/block/sdf/sdf2"
DEVTYPE = "partition"
ID_ATA = 1
ID_ATA_DOWNLOAD_MICROCODE = 1
ID_ATA_FEATURE_SET_APM = 1
ID_ATA_FEATURE_SET_APM_CURRENT_VALUE = 128
ID_ATA_FEATURE_SET_APM_ENABLED = 1
ID_ATA_FEATURE_SET_HPA = 1
ID_ATA_FEATURE_SET_HPA_ENABLED = 1
ID_ATA_FEATURE_SET_PM = 1
ID_ATA_FEATURE_SET_PM_ENABLED = 1
ID_ATA_FEATURE_SET_PUIS = 1
ID_ATA_FEATURE_SET_PUIS_ENABLED = 0
ID_ATA_FEATURE_SET_SECURITY = 1
ID_ATA_FEATURE_SET_SECURITY_ENABLED = 0
ID_ATA_FEATURE_SET_SECURITY_ENHANCED_ERASE_UNIT_MIN = 66356
ID_ATA_FEATURE_SET_SECURITY_ERASE_UNIT_MIN = 66356
ID_ATA_FEATURE_SET_SMART = 1
ID_ATA_FEATURE_SET_SMART_ENABLED = 1
ID_ATA_ROTATION_RATE_RPM = 5526
ID_ATA_SATA = 1
ID_ATA_SATA_SIGNAL_RATE_GEN1 = 1
ID_ATA_SATA_SIGNAL_RATE_GEN2 = 1
ID_ATA_WRITE_CACHE = 1
ID_ATA_WRITE_CACHE_ENABLED = 1
ID_BUS = "ata"
ID_FS_LABEL = "Unraid_Backup"
ID_FS_LABEL_ENC = "Unraid\x20Backup"
ID_FS_TYPE = "ntfs"
ID_FS_USAGE = "filesystem"
ID_FS_UUID = "A0286E45286E1B14"
ID_FS_UUID_ENC = "A0286E45286E1B14"
ID_MODEL = "ST5000LM000-2AN170"
ID_MODEL_ENC = "ST5000LM000-2AN170\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20\x20"
ID_PART_ENTRY_DISK = "8:80"
ID_PART_ENTRY_NAME = "Basic\x20data\x20partition"
ID_PART_ENTRY_NUMBER = 2
ID_PART_ENTRY_OFFSET = 264192
ID_PART_ENTRY_SCHEME = "gpt"
ID_PART_ENTRY_SIZE = 9767276544
ID_PART_ENTRY_TYPE = "ebd0a0a2-b9e5-4433-87c0-68b6b72699c7"
ID_PART_ENTRY_UUID = "57e72313-abd7-478e-bd40-2fffe570c653"
ID_PART_TABLE_TYPE = "gpt"
ID_PART_TABLE_UUID = "f8fc2d4c-97ad-4e41-91bf-0eb0c542d645"
ID_PATH = "pci-0000:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0"
ID_PATH_TAG = "pci-0000_00_1a_0-usb-0_1_2_1_0-scsi-0_0_0_0"
ID_REVISION = 0001
ID_SERIAL = "ST5000LM000-2AN170_WCJ0QEH3"
ID_SERIAL_SHORT = "WCJ0QEH3"
ID_TYPE = "disk"
ID_WWN = "0x5000c500b999fee4"
ID_WWN_WITH_EXTENSION = "0x5000c500b999fee4"
MAJOR = 8
MINOR = 82
PARTN = 2
PARTNAME = "Basic data partition"
SUBSYSTEM = "block"

 

Ok.  Here's the situation.  You unplugged that disk before it was unmounted:

### Disk was removed before it was unmounted.  Originally mounted as /dev/sde
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771681, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771682, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771683, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771684, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 809369, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 733102712, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636525, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636526, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636527, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636528, lost async page write

### Disk was re-inserted and assigned to /dev/sdf
Jan 21 08:21:30 Tower unassigned.devices: Successfully mounted 'sdf2' on '/mnt/disks/Unraid_Backup'.
Jan 21 08:21:30 Tower unassigned.devices: Mount warning: The disk contains an unclean file system (0, 1). The file system wasn't safely closed on Windows. Fixing. .

 

Because the device is now /dev/sdf, Unraid thinks it's still /dev/sde and does not assign it a 'devX' assignment.  In this case UD assumes the disk dropped out of the array.  The disk is not tagged as a USB device, so UD marks it as 'Array'.

 

Bottom line, remove the disk and reboot.  The disk is currently unmounted.

Edited January 22, 20224 yr by dlandon

16 minutes ago, dlandon said:

Ok.  Here's the situation.  You unplugged that disk before it was unmounted:

### Disk was removed before it was unmounted.  Originally mounted as /dev/sde
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771681, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771682, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771683, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 771684, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 809369, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 733102712, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636525, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636526, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636527, lost async page write
Jan 10 01:00:30 Tower kernel: Buffer I/O error on dev sde2, logical block 737636528, lost async page write

### Disk was re-inserted and assigned to /dev/sdf
Jan 21 08:21:30 Tower unassigned.devices: Successfully mounted 'sdf2' on '/mnt/disks/Unraid_Backup'.
Jan 21 08:21:30 Tower unassigned.devices: Mount warning: The disk contains an unclean file system (0, 1). The file system wasn't safely closed on Windows. Fixing. .

 

Because the device is now /dev/sdf, Unraid thinks it's still /dev/sde and does not assign it a 'devX' assignment.  In this case UD assumes the disk dropped out of the array.  The disk is not tagged as a USB device, so UD marks it as 'Array'.

 

Bottom line, remove the disk and reboot.  The disk is currently unmounted.

Ok thanks

I'm pretty sure to always unmount drive before remove it but maybe I forgot last time.

5 minutes ago, deadnote said:

Ok thanks

I'm pretty sure to always unmount drive before remove it but maybe I forgot last time.

 

With the latest UD you can assign an alias disk name and use this command in your script to unmount the disk:

/usr/local/sbin/rc.unassigned umount name=diskname

 

Also, one of the things I do is to put some sounds in the script to let you know when a disk is mounted, unmounted, etc.  Look at the first post of UD for some ideas.  The sample script has some 'beep' commands that do that.  You of course need a speaker in your server.

 

EDIT: You should also do a file sysem check on that disk.

Edited January 22, 20224 yr by dlandon

I am trying to mount a few drives to and everytime I try to mount the drives I get the following error in device log:

 

Jan 22 11:46:06 Tower unassigned.devices: Mount of 'sdk1' failed: 'mount: /mnt/disks/MN1240FA14K9LD: /dev/sdk1 already mounted or mount point busy. '

 

I have tried uninstalling Unassigned Drives and reinstalling but still receive the same error.  Seems like the mount is stuck somewhere and I cannot remove.  Any help would be appreciated.

 

I see the +sdk1 file in /dev folder.  Should I delete that or need to go another route?

 

I am just trying to use Midnight Commander to copy files from the drive to my array.  Thanks for your help.

Edited January 22, 20224 yr by MKIV Surfer

50 minutes ago, MKIV Surfer said:

I have tried uninstalling Unassigned Drives and reinstalling but still receive the same error.  Seems like the mount is stuck somewhere and I cannot remove.  Any help would be appreciated.

Uninstalling and re-installing UD doesn't do anything.  I see users try this all the time and it never works to fix problems.

 

Most likely what you've done is to try a copy when the disk wasn't mounted and you created a mount point folder.  Get into a command line and do this command 'ls /mnt/disks/' and see if the '/mnt/disks/MN1240FA14K9LD' folder is there.  If it is there, run this command 'rm -R /mnt/disks/MN1240FA14K9LD'.  Then you should be able to mount the disk,

7 minutes ago, dlandon said:

Uninstalling and re-installing UD doesn't do anything.  I see users try this all the time and it never works to fix problems.

 

Most likely what you've done is to try a copy when the disk wasn't mounted and you created a mount point folder.  Get into a command line and do this command 'ls /mnt/disks/' and see if the '/mnt/disks/MN1240FA14K9LD' folder is there.  If it is there, run this command 'rm -R /mnt/disks/MN1240FA14K9LD'.  Then you should be able to mount the disk,

Thank you for the quick reply.  I saw that on another thread and tried that.  This is all I get when doing that.  I'm assuming because I don't have any disks mounted in UD.

3 minutes ago, MKIV Surfer said:

Thank you for the quick reply.  I saw that on another thread and tried that.  This is all I get when doing that.  I'm assuming because I don't have any disks mounted in UD.

Post diagnostics so I can have a look.  Normally that is from the situation I described to you.

 

Also show me the output from the 'mount' command from the command line.

3 minutes ago, dlandon said:

Post diagnostics so I can have a look.  Normally that is from the situation I described to you.

 

Also show me the output from the 'mount' command from the command line.

 

Again, thank you for helping me so quickly.  I have attached the diagnostics for you and here is the results of the 'mount' command.

 

tower-diagnostics-20220122-1314.zip

Linux does not think the disk is mounted, so I don't quite get what is happening.

 

One last request.  Post a screen shot of the UD page.  Is this a USB disk?

 

Next response I'll have some ideas for you to solve this.

5 minutes ago, dlandon said:

Linux does not think the disk is mounted, so I don't quite get what is happening.

 

One last request.  Post a screen shot of the UD page.  Is this a USB disk?

 

Next response I'll have some ideas for you to solve this.

One is a USB drive and one is a Sata.  The Sata (hitachi) is the one not working.

 

Also, the check mark is not blue for the Hitachi drive either to run file system check.  But I'm assuming that is because it has trouble finding it.

3 minutes ago, MKIV Surfer said:

Also, the check mark is not blue for the Hitachi drive either to run file system check.  But I'm assuming that is because it has trouble finding it.

The disk is in a very funny state.  It is not detected as mounted at '/mnt/disks', but '/dev/sdk' appears to be mounted.

 

I think your best option at this point is a reboot.

5 minutes ago, dlandon said:

The disk is in a very funny state.  It is not detected as mounted at '/mnt/disks', but '/dev/sdk' appears to be mounted.

 

I think your best option at this point is a reboot.

 

Yeah, I have tried rebooting multiple times with no luck (also after I uninstalled the plugin which we know didn't do anything).

1 minute ago, MKIV Surfer said:

 

Yeah, I have tried rebooting multiple times with no luck (also after I uninstalled the plugin which we know didn't do anything).

Something is mounting /dev/sdk.  Let me look at the diagnostics once more.

Has this just started to be a problem, or has it always been  a problem?

 

Try one more command for me:

mount | grep /dev/sdk

 

4 minutes ago, dlandon said:

Has this just started to be a problem, or has it always been  a problem?

 

Try one more command for me:

mount | grep /dev/sdk

 

I have had UD installed for quite some time but just never got around to using it, so these drives have just been sitting there in the plugin but have never used it.  So not sure if its been a problem or not because I just now was looking to use it.

 

I wonder if I can shutdown, unplug the drive and restart the tower.  Then replug the drive back in or would that not do anything?

 

Edited January 22, 20224 yr by MKIV Surfer

8 minutes ago, MKIV Surfer said:

I wonder if I can shutdown, unplug the drive and restart the tower.  Then replug the drive back in or would that not do anything?

That would be a good idea.  Honestly I am at a loss, Linux thinks the drive is mounted, but by all indications, it's not.

 

Before you do that, remove the disklocation-master plugin.  And try again,

7 hours ago, dlandon said:

That would be a good idea.  Honestly I am at a loss, Linux thinks the drive is mounted, but by all indications, it's not.

 

Before you do that, remove the disklocation-master plugin.  And try again,

Thank you for your help. After uninstalling dislocation and uninstalling the disk, it still didn't work. We'll just chalk it up as unfixable. I might try plugging it into my sata to USB adapter and see if that works. Thanks for all the help.

9 hours ago, MKIV Surfer said:

Thanks for all the help.

If you wanted to pursue this further, the best way is for me to team viewer to your system.  Your choice.

On 1/21/2022 at 8:00 PM, dlandon said:

Yes, the help does provide a lot of information.

I think I found out why I did not find it earlier:
The help for UD  / SMB / Shares and such opens from the Click on Boot Device
I'm not sure whether the entry Boot device was present before I installed UD (I guess it was), but its a bit counter intuitive to check there.
(Click red to open both blue (and the following blue as well, not on screenshot)

21 minutes ago, wambo said:

(Click red to open both blue (and the following blue as well, not on screenshot)

I don't use the non-tabbed view so I've never seen this before.  I'm looking into it.

18 hours ago, dlandon said:

I don't use the non-tabbed view so I've never seen this before.  I'm looking into it.

 

I saw the changelog today but I can't see any difference.
Also tried the tabbed view,  but there I just cannot access the blue help text at all. (Even if I open the one from previous tab)

Maybe I have another plugin interfering?

Edited January 24, 20224 yr by wambo

First, thanks for developing this plugin, I have been enjoying it much with USB drives, NVMes etc.

 

Yesterday my dockers no longer start and I get the error message "Docker Service failed to start." It happened after I updated a few plugins and unassigned devices was one of them I believe. After that, I could no longer access my NVMe drive where my dockers, appdata etc are located. The other NVMe is still accessible though. I have tried to reboot a number of times without any luck.

 

Any suggestion on what to do? Im a total noob on unRaid and any Linux in general so be gentle :-)

 

I tried to include the logs, hope I got it right.

 

Thanks in advance!

unserver-diagnostics-20220124-0923.zip