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


dlandon

Recommended Posts

9 minutes ago, dlandon said:

I think it's a permissions problem.  Go to an Unraid terminal session and run this command:


ls -l /mnt/disks/qB1

Show the results.

root@:~# ls -l /mnt/disks/qB1
total 204
drwxrwxrwx  8 nobody users    124 Oct 22 22:58 1/
drwxrwxrwx 35 nobody users   8192 Nov  2 16:28 2/
drwxrwxrwx  2 nobody users 159744 Nov  2 14:46 3/
drwxrwxrwx  2 nobody users      6 Oct 19 20:20 4/
drwxrwxrwx  7 nobody users    151 Aug 11 17:43 temp/


root@:~# ls -l /mnt/disks/qB2
total 120
drwxr-xr-x 12 nobody users   174 Oct 26 20:05 1/
drwxrwxrwx 17 nobody users  8192 Nov  2 16:30 2/
drwxrwxrwx  2 nobody users 86016 Nov  2 16:23 3/
drwxrwxrwx  2 nobody users     6 Oct 25 03:19 4/
drwxrwxrwx  2 nobody users     6 Oct  4 22:03 temp/

Link to comment
30 minutes ago, WaffleClap said:

root@:~# ls -l /mnt/disks/qB1
total 204
drwxrwxrwx  8 nobody users    124 Oct 22 22:58 1/
drwxrwxrwx 35 nobody users   8192 Nov  2 16:28 2/
drwxrwxrwx  2 nobody users 159744 Nov  2 14:46 3/
drwxrwxrwx  2 nobody users      6 Oct 19 20:20 4/
drwxrwxrwx  7 nobody users    151 Aug 11 17:43 temp/


root@:~# ls -l /mnt/disks/qB2
total 120
drwxr-xr-x 12 nobody users   174 Oct 26 20:05 1/
drwxrwxrwx 17 nobody users  8192 Nov  2 16:30 2/
drwxrwxrwx  2 nobody users 86016 Nov  2 16:23 3/
drwxrwxrwx  2 nobody users     6 Oct 25 03:19 4/
drwxrwxrwx  2 nobody users     6 Oct  4 22:03 temp/

Post diagnostics.

Link to comment

Any one else getting this error after updating from rc3 to rc5? It was working fine yesterday, but after the os update and yes I am on the latest ver. of unassigned devices.

ErrorWarningSystemArrayLogin


Nov 2 19:22:23 MasterServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
its just repeating itself I have tried reverting back to rc3 and no joy

 

Link to comment
9 minutes ago, cimmy01 said:

Any one else getting this error after updating from rc3 to rc5? It was working fine yesterday, but after the os update and yes I am on the latest ver. of unassigned devices.

ErrorWarningSystemArrayLogin


Nov 2 19:22:23 MasterServer root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
its just repeating itself I have tried reverting back to rc3 and no joy

 

You left a browser session running when you rebooted the server,  Close all browser sessions.

Link to comment

I dont have a Screen Shot. A Kernel panic is the warning I received when I plugged my monitor in to the GC  and the boot halted. It basically means that the kernel was unable to load for some reason. I did get the problem fixed by copying all of my usb data to another computer and reinstalled from unraid the os then copied my config to the usb I am back up and running but I still have the orginal unassigned devices error

 

Edited by cimmy01
typo
Link to comment
2 minutes ago, cimmy01 said:

I dont have a Screen Shot. A Kernel panic is the warning I received when I plugged my monitor in to the GC  and the boot halted. It basically means that the kernel was unable to load for some reason. I did get the problem fixed by copying all of my usb data to another computer and reinstalled from unraid the os then copied my config to the usb I am back up and running but I still have the orginal unassigned devices error

 

I was asking what the kind of kernel panic you received,  I know what a kernel panic is.

 

If your error is the csrf error again, you still have a browser session open somewhere.  If it's not the csrf error, then post diagnostics.

Link to comment

Thank you I recently added some memory to the server and I had forgot about that. I have got it back up and running by finding an older back up and redoing the usb drive with that and checked on the memory still only running at 2166 mhz but I dont care its running and this isn't exactly a high end gaming rig. It is back up and running. The error went away with out any other changes not sure what happened. Running a Parity check and when that's finished I'll try and look in to things alittle more 

Edited by cimmy01
Link to comment

I'm trying to mount an encrypted xfs drive that had been part of my array but I was having issues, maybe due to a bad SATA card/cable, so I ended up replacing the drive after installing a SAS card.  I suspect there might be files on it that are not on the array, so I have been trying to mount it in unasigned devices to find out, and if so recover them.  I was able to mount a another encrypted drive in a similar situation and recover files. The drive I'm having issues with won't mount when server is freshly booted and the array is off, but there's probably no mechanism to read an inputted key at this point, and it won't mount when array has been started and stopped either.  I see this in the logs when I try to mount:

 

Nov 3 03:00:05 Tower unassigned.devices: Adding disk '/dev/mapper/HGST_HDN726060ALE614_K1H90MAD'...
Nov 3 03:00:05 Tower unassigned.devices: luksOpen error: Device HGST_HDN726060ALE614_K1H90MAD already exists.
Nov 3 03:00:05 Tower unassigned.devices: Partition 'HGST_HDN726060ALE614_K1H90MAD' could not be mounted...

 

I'm ready to give up on the drive if there's nothing I can do, just want to check.  Maybe unrelated, but after attempting to mount the disk, I started my array ack up and a parity check started, despite running successfully to completion yesterday.  Attached is fresh diagnostics from after the newest parity chjeck was started and canceled.  If it helps I have been getting some excellent help from ti-ti jorge regarding the lead up to this situation on this thread: 

 

tower-diagnostics-20191103-1117.zip

Link to comment
8 minutes ago, bobobeastie said:

I'm trying to mount an encrypted xfs drive that had been part of my array but I was having issues, maybe due to a bad SATA card/cable, so I ended up replacing the drive after installing a SAS card.  I suspect there might be files on it that are not on the array, so I have been trying to mount it in unasigned devices to find out, and if so recover them.  I was able to mount a another encrypted drive in a similar situation and recover files. The drive I'm having issues with won't mount when server is freshly booted and the array is off, but there's probably no mechanism to read an inputted key at this point, and it won't mount when array has been started and stopped either.  I see this in the logs when I try to mount:

 

Nov 3 03:00:05 Tower unassigned.devices: Adding disk '/dev/mapper/HGST_HDN726060ALE614_K1H90MAD'...
Nov 3 03:00:05 Tower unassigned.devices: luksOpen error: Device HGST_HDN726060ALE614_K1H90MAD already exists.
Nov 3 03:00:05 Tower unassigned.devices: Partition 'HGST_HDN726060ALE614_K1H90MAD' could not be mounted...

 

I'm ready to give up on the drive if there's nothing I can do, just want to check.  Maybe unrelated, but after attempting to mount the disk, I started my array ack up and a parity check started, despite running successfully to completion yesterday.  Attached is fresh diagnostics from after the newest parity chjeck was started and canceled.  If it helps I have been getting some excellent help from ti-ti jorge regarding the lead up to this situation on this thread: 

 

tower-diagnostics-20191103-1117.zip 127.19 kB · 0 downloads

You have a keyfile problem.

Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (47): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (49): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (49): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (51): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (51): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (53): /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (53): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (55): /usr/sbin/cryptsetup luksOpen /dev/md5 md5 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (55): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (57): /usr/sbin/cryptsetup luksOpen /dev/md6 md6 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (57): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (59): /usr/sbin/cryptsetup luksOpen /dev/md7 md7 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (59): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (61): /usr/sbin/cryptsetup luksOpen /dev/md8 md8 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (61): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (63): /usr/sbin/cryptsetup luksOpen /dev/md9 md9 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (63): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (65): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (65): exit status: 1
Nov  1 06:37:43 Tower emhttpd: Missing encryption key
Nov  1 06:37:43 Tower kernel: mdcmd (46): stop 
Nov  1 06:37:43 Tower kernel: md1: stopping
Nov  1 06:37:43 Tower kernel: md2: stopping
Nov  1 06:37:43 Tower kernel: md3: stopping
Nov  1 06:37:43 Tower kernel: md4: stopping
Nov  1 06:37:43 Tower kernel: md5: stopping
Nov  1 06:37:43 Tower kernel: md6: stopping
Nov  1 06:37:43 Tower kernel: md7: stopping
Nov  1 06:37:43 Tower kernel: md8: stopping
Nov  1 06:37:43 Tower kernel: md9: stopping
Nov  1 06:37:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Nov  1 06:37:44 Tower avahi-daemon[6579]: Server startup complete. Host name is Tower.local. Local service cookie is 3274231656.
Nov  1 06:37:44 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Nov  1 06:37:44 Tower avahi-daemon[6579]: Service "Tower" (/services/ssh.service) successfully established.
Nov  1 06:37:44 Tower avahi-daemon[6579]: Service "Tower" (/services/smb.service) successfully established.
Nov  1 06:37:44 Tower avahi-daemon[6579]: Service "Tower" (/services/sftp-ssh.service) successfully established.
Nov  1 06:37:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
### [PREVIOUS LINE REPEATED 89 TIMES] ###
Nov  1 06:39:20 Tower unassigned.devices: Adding disk '/dev/mapper/HGST_HDN726060ALE614_K1H90MAD'...
Nov  1 06:39:20 Tower unassigned.devices: luksOpen: key file not found.

You need to start the array and enter the passphrase so it is available to UD, or provide the key file.  The keyfile is 'keyfile' and is stored at /root/.  It contains the passphrase that UD will use.

Link to comment
1 minute ago, dlandon said:

You have a keyfile problem.


Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (47): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (49): /usr/sbin/cryptsetup luksOpen /dev/md2 md2 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (49): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (51): /usr/sbin/cryptsetup luksOpen /dev/md3 md3 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (51): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (53): /usr/sbin/cryptsetup luksOpen /dev/md4 md4 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (53): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (55): /usr/sbin/cryptsetup luksOpen /dev/md5 md5 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (55): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (57): /usr/sbin/cryptsetup luksOpen /dev/md6 md6 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (57): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (59): /usr/sbin/cryptsetup luksOpen /dev/md7 md7 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (59): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (61): /usr/sbin/cryptsetup luksOpen /dev/md8 md8 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (61): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (63): /usr/sbin/cryptsetup luksOpen /dev/md9 md9 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (63): exit status: 1
Nov  1 06:37:43 Tower emhttpd: shcmd (65): /usr/sbin/cryptsetup luksOpen /dev/nvme0n1p1 nvme0n1p1 --allow-discards --key-file /root/keyfile
Nov  1 06:37:43 Tower root: Failed to open key file.
Nov  1 06:37:43 Tower emhttpd: shcmd (65): exit status: 1
Nov  1 06:37:43 Tower emhttpd: Missing encryption key
Nov  1 06:37:43 Tower kernel: mdcmd (46): stop 
Nov  1 06:37:43 Tower kernel: md1: stopping
Nov  1 06:37:43 Tower kernel: md2: stopping
Nov  1 06:37:43 Tower kernel: md3: stopping
Nov  1 06:37:43 Tower kernel: md4: stopping
Nov  1 06:37:43 Tower kernel: md5: stopping
Nov  1 06:37:43 Tower kernel: md6: stopping
Nov  1 06:37:43 Tower kernel: md7: stopping
Nov  1 06:37:43 Tower kernel: md8: stopping
Nov  1 06:37:43 Tower kernel: md9: stopping
Nov  1 06:37:43 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Nov  1 06:37:44 Tower avahi-daemon[6579]: Server startup complete. Host name is Tower.local. Local service cookie is 3274231656.
Nov  1 06:37:44 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Nov  1 06:37:44 Tower avahi-daemon[6579]: Service "Tower" (/services/ssh.service) successfully established.
Nov  1 06:37:44 Tower avahi-daemon[6579]: Service "Tower" (/services/smb.service) successfully established.
Nov  1 06:37:44 Tower avahi-daemon[6579]: Service "Tower" (/services/sftp-ssh.service) successfully established.
Nov  1 06:37:45 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
### [PREVIOUS LINE REPEATED 89 TIMES] ###
Nov  1 06:39:20 Tower unassigned.devices: Adding disk '/dev/mapper/HGST_HDN726060ALE614_K1H90MAD'...
Nov  1 06:39:20 Tower unassigned.devices: luksOpen: key file not found.

You need to start the array and enter the passphrase so it is available to UD, or provide the key file.  The keyfile is 'keyfile' and is stored at /root/.  It contains the passphrase that UD will use.

I don't have a keyfile as far as I know, and I don't see it in root using Krusader.  I enter my key in to a text field before starting my array, which works with no issues that I am aware of.  This is the same arrangement where I mounted another encrypted drive.  It it would help I could temporarily use a keyfile, do I simply create the file and then enter my encryption password as the only text in the file?

Link to comment
1 minute ago, bobobeastie said:

I don't have a keyfile as far as I know, and I don't see it in root using Krusader.  I enter my key in to a text field before starting my array, which works with no issues that I am aware of.  This is the same arrangement where I mounted another encrypted drive.  It it would help I could temporarily use a keyfile, do I simply create the file and then enter my encryption password as the only text in the file?

According to the log, the array is not starting because the keyfile is missing, so I don't see how you can say the array is working without issues.  The array has to be started before UD can see the keyfile.

 

You can create a keyfile with only the passphrase text,  Be sure there are no new lines in the file.

Link to comment
2 hours ago, dlandon said:

According to the log, the array is not starting because the keyfile is missing, so I don't see how you can say the array is working without issues.  The array has to be started before UD can see the keyfile.

 

You can create a keyfile with only the passphrase text,  Be sure there are no new lines in the file.

I can't figure out how to get a keyfile, Krusader won't allow me to place a file in root, and I can't copy a keyfile that I created in appdata.  Figuring it needed escalated priveledges, I tried mc from the terminal, but I can't figure out mc, command line file editors/browsers are beyond me.   I'm assuming I could copy the appdata keyfile to root on the command line if I had the right command.  I do see a keyfile in root in mc which thankfully defaults to root, but I can't figure out how to view it.

 

I'm not sure any of that matters, because I can most definitely start my array and access shares and files on them, docker starts fine.

 

edit: Is the missing key bit in the syslog just from after a reboot when it is waiting for me to provide the key maybe?  I think there are two different methods to unlock encryption, using a file and using a passphrase, and I'm using passphase, because I thought it would be more secure.

Edited by bobobeastie
more info
Link to comment
14 minutes ago, bobobeastie said:

I can't figure out how to get a keyfile, Krusader won't allow me to place a file in root, and I can't copy a keyfile that I created in appdata.  Figuring it needed escalated priveledges, I tried mc from the terminal, but I can't figure out mc, command line file editors/browsers are beyond me.   I'm assuming I could copy the appdata keyfile to root on the command line if I had the right command.  I do see a keyfile in root in mc which thankfully defaults to root, but I can't figure out how to view it.

 

I'm not sure any of that matters, because I can most definitely start my array and access shares and files on them, docker starts fine.

 

edit: Is the missing key bit in the syslog just from after a reboot when it is waiting for me to provide the key maybe?  I think there are two different methods to unlock encryption, using a file and using a passphrase, and I'm using passphase, because I thought it would be more secure.

Go to a Unraid terminal and type:

cat /root/keyfile

This will show you the keyfile contents.

 

If the keyfile exists, UD should mount the encrypted drive.

Edited by dlandon
Link to comment
2 minutes ago, dlandon said:

Go to a Unraid terminal and type:


cat /root/keyfile

This will show you the keyfile contents.

 

If the keyfile exists, UD should mount the encrypted drive.

That works, it shows my passphrase.  My assumption was that this issue was caused by this drive having been already in the array because of this bit of the log from when I try to mount:

 

Nov 3 03:00:05 Tower unassigned.devices: Adding disk '/dev/mapper/HGST_HDN726060ALE614_K1H90MAD'...
Nov 3 03:00:05 Tower unassigned.devices: luksOpen error: Device HGST_HDN726060ALE614_K1H90MAD already exists.
Nov 3 03:00:05 Tower unassigned.devices: Partition 'HGST_HDN726060ALE614_K1H90MAD' could not be mounted...

 

Specifically the already exists part.  Can I either make it ignore this safely, or can I make it realize that there are no disks in the array with the same serial?  I could off course be wrong, I'm not  an expert on any of this.

Link to comment
2 minutes ago, bobobeastie said:

That works, it shows my passphrase.  My assumption was that this issue was caused by this drive having been already in the array because of this bit of the log from when I try to mount:

 

Nov 3 03:00:05 Tower unassigned.devices: Adding disk '/dev/mapper/HGST_HDN726060ALE614_K1H90MAD'...
Nov 3 03:00:05 Tower unassigned.devices: luksOpen error: Device HGST_HDN726060ALE614_K1H90MAD already exists.
Nov 3 03:00:05 Tower unassigned.devices: Partition 'HGST_HDN726060ALE614_K1H90MAD' could not be mounted...

 

Specifically the already exists part.  Can I either make it ignore this safely, or can I make it realize that there are no disks in the array with the same serial?  I could off course be wrong, I'm not  an expert on any of this.

No.  You cannot force the disk to mount.

 

Looks like Unraid still thinks it is part of the array.  Please show a screen shot of the Main tab Array Devices.

Link to comment
  • trurl pinned this topic

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.