On 3/12/2018 at 8:18 AM, Sanches said:

Good morning @dlandon

 

As requested, I'm bringing my issue to this topic.

 

"Did anyone ever got this problem below?

 

I tried updating to the latest version, rebooting and reinstalling the plugin. This error appears only when I mount any drive.

 

Thoughts?

 

Thank you!"

 

Show me the output from the following command:

cat /etc/unraid-version

This is happening in the routine that shows the disk usage indicators.  There are several possibilities for where is is happening.  Do the following for me:

- Switch to a white theme.  The dark theme is too hard for me to read.

- Click the + icon on the UD page to show the partitions.

- Capture a screen shot for me to look at.

 

I suspect you will see a usage display issue on the partition.

Edited March 17, 20188 yr by dlandon

15 hours ago, Oldbean57 said:

After seeing the output of the diagnostics, I decided to have a look for the successful mounting of the HDD from the array to see why that would be any different for /dev/sdd, but I'm not sure if the details of a successful mount are recorded in detail as part of the "unassigned.devices" logging?

 

I was able to see the failed mount, for example:

Mar 16 16:57:31 NAS unassigned.devices: Adding disk '/dev/sdj1'...
Mar 16 16:57:31 NAS unassigned.devices: Mount drive command: /sbin/mount -t btrfs -o auto,async,noatime,nodiratime '/dev/sdj1' '/mnt/disks/WDC_WDS100T2B0B-00YS70_180481420126'
Mar 16 16:57:31 NAS unassigned.devices: Mount of '/dev/sdj1' failed. Error message: mount: /mnt/disks/WDC_WDS100T2B0B-00YS70_180481420126: wrong fs type, bad option, bad superblock on /dev/sdj1, missing codepage or helper program, or other error. 
Mar 16 16:57:31 NAS unassigned.devices: Partition 'WDC_WDS100T2B0B-00YS70_180481420126' could not be mounted...

Looking in the logs at how the encrypted disks in the array are unlocked using "cryptsetup" and then mounted, I replicated this manually via the Terminal for /dev/sdj1 and it mounted successfully, so I have a manual workaround for now from which I can run VMs:

root@NAS:/mnt# cryptsetup luksOpen /dev/sdj1 sdj1
Enter passphrase for /dev/sdj1:
root@NAS:/mnt# mount -t btrfs -o auto,async,noatime,nodiratime '/dev/mapper/sdj1' '/mnt/disks/test'
root@NAS:/mnt# cd /mnt/disks/test
root@NAS:/mnt/disks/test# ls
root@NAS:/mnt/disks/test# ls -la
total 16
drwxrwxrwx 1 nobody users  0 Mar 16 16:50 ./
drwxrwxrwx 3 nobody users 60 Mar 16 20:27 ../
root@NAS:/mnt/disks/test#

 

 

However it would be great to be able to use Unassigned Devices to have this happen automatically using the same passphrase as entered to start the array after each boot, then all will be mounted and ready for the VM services to start. I think the key is to work out why /dev/sdd mounted using the array passphrase but /dev/sdj will not.

 

Thanks for your help, Rich.

 

 

UD does not think it is an encrypted disk.  Show me a screen shot of the drive in UD.  I'd like to see what file system UD is picking up.  I believe you said earlier it was a nvme disk.

2 hours ago, dlandon said:

UD does not think it is an encrypted disk.  Show me a screen shot of the drive in UD.  I'd like to see what file system UD is picking up.  I believe you said earlier it was a nvme disk.

Hi,

 

It's funny you say that, before it started working (spoiler alert), the FS type was listed as btrfs in the FS column in UD. It's a SATA M.2 SSD.

 

After I did the manual decrypt with cryptsetup in the Terminal, I thought I would test a mount via the UD GUI, which unfortunately still didn't work (same error). However I noticed that the FS type changed to crypto_LUKS:

 

 

I wanted to send you a screenshot of the before and after, so rebooted to reset the encryption, but post-reboot the FS type was still crypto_LUKS, not back to btrfs.

 

After entering the array passphrase I then tried a UD mount and it worked! Automount post-reboot also works as expected, so I'm delighted about that.

 

I don't know whether it was the manual one-off cryptsetup or the reboot that resolved it, but all is now well. It might be hard to get to the bottom of it, but if there is anything further you'd be interested to see please do let me know.

 

Thanks for your help, small Paypal retirement contribution incoming

 

Rich.

 

8 minutes ago, Oldbean57 said:

Hi,

 

It's funny you say that, before it started working (spoiler alert), the FS type was listed as btrfs in the FS column in UD. It's a SATA M.2 SSD.

 

After I did the manual decrypt with cryptsetup in the Terminal, I thought I would test a mount via the UD GUI, which unfortunately still didn't work (same error). However I noticed that the FS type changed to crypto_LUKS:

 

 

I wanted to send you a screenshot of the before and after, so rebooted to reset the encryption, but post-reboot the FS type was still crypto_LUKS, not back to btrfs.

 

After entering the array passphrase I then tried a UD mount and it worked! Automount post-reboot also works as expected, so I'm delighted about that.

 

I don't know whether it was the manual one-off cryptsetup or the reboot that resolved it, but all is now well. It might be hard to get to the bottom of it, but if there is anything further you'd be interested to see please do let me know.

 

Thanks for your help, small Paypal retirement contribution incoming

 

Rich.

 

Glad it worked out.  The end result you see is how it is supposed to work.  It is probably related to the nvme drive.   They are recognized by Linux differently and have been a challenge for me in UD as I don't have one to do any testing.

On 3/15/2018 at 5:08 PM, dlandon said:

Do you have the preclear plugin installed?

As confirmed I do not.  I had but was all cleaned up 

On 17/03/2018 at 10:06 AM, dlandon said:

Show me the output from the following command:

cat /etc/unraid-version

This is happening in the routine that shows the disk usage indicators.  There are several possibilities for where is is happening.  Do the following for me:

- Switch to a white theme.  The dark theme is too hard for me to read.

- Click the + icon on the UD page to show the partitions.

- Capture a screen shot for me to look at.

 

I suspect you will see a usage display issue on the partition.

Holy S**t! You were right!

 

When using color bar to show the usage, this lines appear. When using gray bar or text, no issue!

 

Thank a lot!

 

 

Today is the first time to use Unassigned Devices. I took an old drive and did insert it into my unRAID box. I do see the drive in UA and UA reports about an existing partition.

 

Whenever I try to remove that partition, it reports success but the partition is still there. I would like to format that partition in XFS and share it's content.

 

What should I do?

 

Thanks in advance.

 

***Edit*** Destructive mode was and is enabled.

 

 

Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] 4096-byte physical blocks
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Write Protect is off
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Mode Sense: 9b 00 10 08
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 25 15:07:59 Tower kernel: sdg: sdg1
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Attached SCSI disk
Mar 25 15:08:29 Tower emhttpd: WDC_WD30EZRX-00MMMB0_WD-WCA********* (sdg) 512 5860533168
Mar 25 15:09:36 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdg'.
Mar 25 15:09:48 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdg'.
Mar 25 15:10:44 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdg'.

 

Edited March 25, 20188 yr by hawihoney

1 hour ago, hawihoney said:

Today is the first time to use Unassigned Devices. I took an old drive and did insert it into my unRAID box. I do see the drive in UA and UA reports about an existing partition.

 

Whenever I try to remove that partition, it reports success but the partition is still there. I would like to format that partition in XFS and share it's content.

 

What should I do?

 

Thanks in advance.

 

***Edit*** Destructive mode was and is enabled.

 

 

Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] 4096-byte physical blocks
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Write Protect is off
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Mode Sense: 9b 00 10 08
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 25 15:07:59 Tower kernel: sdg: sdg1
Mar 25 15:07:59 Tower kernel: sd 11:0:5:0: [sdg] Attached SCSI disk
Mar 25 15:08:29 Tower emhttpd: WDC_WD30EZRX-00MMMB0_WD-WCA********* (sdg) 512 5860533168
Mar 25 15:09:36 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdg'.
Mar 25 15:09:48 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdg'.
Mar 25 15:10:44 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdg'.

 

Short log snippets are not useful.  Please post your diagnostics.

Ah, sorry. Diagnostics attached.

 

tower-diagnostics-20180325-1649.zip

4 hours ago, hawihoney said:

Ah, sorry. Diagnostics attached.

 

tower-diagnostics-20180325-1649.zip

How is this disk partitioned?  It looks like UD cannot handle removing the partition.  What is the file system?  Can you show a screen shot of UD so I can see what it thinks is the file format?

 

You will probably have to take this to another computer and use a partitioning tool to remove the partition.

14 minutes ago, dlandon said:

You will probably have to take this to another computer and use a partitioning tool to remove the partition.

 

Or use wipefs command (being careful to wipe the correct device)

This drive was part of an unRAID machine. I did replace it with a 6TB. Don't know what filesyste it had (ReiserFS, XFS, BTRFS or parity).

 

Do I issue wipefs for the partition sdg1 or the drive sdg?

 

Thanks for helping.

This is the output of wipefs. DOS? On a 3TB drive? Last time I used DOS was when using 1,44MB diskettes.

 

Really weird. 

Linux 4.14.26-unRAID.
root@Tower:~# wipefs /dev/sdg
DEVICE OFFSET TYPE UUID LABEL
sdg    0x1fe  dos
root@Tower:~#

 

39 minutes ago, hawihoney said:

This drive was part of an unRAID machine. I did replace it with a 6TB. Don't know what filesyste it had (ReiserFS, XFS, BTRFS or parity).

 

Do I issue wipefs for the partition sdg1 or the drive sdg?

 

Thanks for helping.

There is no file system on the disk that UD recognizes.

9 minutes ago, hawihoney said:

This is the output of wipefs. DOS? On a 3TB drive? Last time I used DOS was when using 1,44MB diskettes.

 

Really weird. 

Linux 4.14.26-unRAID.
root@Tower:~# wipefs /dev/sdg
DEVICE OFFSET TYPE UUID LABEL
sdg    0x1fe  dos
root@Tower:~#

 

That would explain it.

I'm not a programmer but slowly learning.  Sorry if this is the incorrect forum.  Is there any way to utilize one of the built-in UD scripts to mount/unmount the drives from Duplicati?

 

Screen Grab from Duplicati:

 

 

Those scripts above are as follows:

 

mount_bu_drive.sh:

#!/bin/bash
 /usr/local/sbin/rc.unassigned mount /dev/sdg

 

unmount_bu_drive.sh

#!/bin/bash
 /usr/local/sbin/rc.unassigned umount /dev/sdg

 

Edited March 28, 20188 yr by kimocal
fix my copy and paste skills, take 2 Stupid Autocorrect!!

12 minutes ago, kimocal said:

mount_bu_drive.sh:

#!/bin/bash
 /usr/local/sbin/rc.unassigned umount /dev/sdg

 

unmount_bu_drive.sh

#!/bin/bash
 /usr/local/sbin/rc.unassigned mount /dev/sdg

 

 I think your scripts are reversed.

16 minutes ago, dlandon said:

 I think your scripts are reversed.

My Copy and Paste skills need some work, but just checked and and my scripts are correct on my Unraid server =P

 

I'll update my previous post.

4 minutes ago, kimocal said:

My Copy and Paste skills need some work, but just checked and and my scripts are correct on my Unraid server =P

 

I'll update my previous post.

Now your unmount script is the same as your mount script.

2 minutes ago, trurl said:

Now your unmount script is the same as your mount script.

Stupid Autocorrect

Hi All,

 

I am a noob on UD, but have some weird stuff going on. I am on 6.5-RC2 (been the case on 6.5 stable and Next RC1-2). I am mapping two shares from my NAS on boot, but shares are not mounting automatically. Might be a simple fix, but can't seem to get it to work.

 

I have also per reading through initiated "empty" Default script, but no change.

 

Hope you guys can help.

 

Best,

 

Casper

 

 

1 hour ago, mrbrowndk said:

Hi All,

 

I am a noob on UD, but have some weird stuff going on. I am on 6.5-RC2 (been the case on 6.5 stable and Next RC1-2). I am mapping two shares from my NAS on boot, but shares are not mounting automatically. Might be a simple fix, but can't seem to get it to work.

 

I have also per reading through initiated "empty" Default script, but no change.

 

Hope you guys can help.

 

Best,

 

Casper

 

 

Posting diagnostics will be the only way I can help you.

Thanks Dlandon. Attached please find diagnostics

brownsbeast-diagnostics-20180329-2254.zip

1 hour ago, mrbrowndk said:

Thanks Dlandon. Attached please find diagnostics

brownsbeast-diagnostics-20180329-2254.zip

The problem is that UD is trying to mount the NFS mounts before the network is up:

Mar 29 11:13:14 BrownsBeast unassigned.devices: Error: Remote SMB/NFS server '192.168.2.230' is offline and share '192.168.2.230://volume1/video' cannot be mounted.
Mar 29 11:13:14 BrownsBeast unassigned.devices: Error: Remote SMB/NFS server '192.168.2.230' is offline and share '192.168.2.230://volume1/photos' cannot be mounted.
Mar 29 11:13:14 BrownsBeast emhttpd: Starting services...
Mar 29 11:13:14 BrownsBeast emhttpd: shcmd (63): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
Mar 29 11:13:14 BrownsBeast kernel: BTRFS: device fsid e0a6a3d9-86b3-4967-8458-dc65511ef8d9 devid 1 transid 5602 /dev/loop2
Mar 29 11:13:14 BrownsBeast kernel: BTRFS info (device loop2): disk space caching is enabled
Mar 29 11:13:14 BrownsBeast kernel: BTRFS info (device loop2): has skinny extents
Mar 29 11:13:14 BrownsBeast root: Resize '/var/lib/docker' of 'max'
Mar 29 11:13:14 BrownsBeast kernel: BTRFS info (device loop2): new size for /dev/loop2 is 21474836480
Mar 29 11:13:14 BrownsBeast emhttpd: shcmd (65): /etc/rc.d/rc.docker start
Mar 29 11:13:14 BrownsBeast ntpd[1895]: Deleting interface #1 br0, 192.168.2.235#123, interface stats: received=11, sent=19, dropped=0, active_time=17 secs
Mar 29 11:13:14 BrownsBeast ntpd[1895]: 193.104.228.123 local addr 192.168.2.235 -> <null>
Mar 29 11:13:14 BrownsBeast ntpd[1895]: 212.99.225.86 local addr 192.168.2.235 -> <null>
Mar 29 11:13:14 BrownsBeast ntpd[1895]: 62.242.89.196 local addr 192.168.2.235 -> <null>
Mar 29 11:13:14 BrownsBeast ntpd[1895]: 92.246.24.225 local addr 192.168.2.235 -> <null>
Mar 29 11:13:14 BrownsBeast root: starting dockerd ...
Mar 29 11:13:14 BrownsBeast kernel: igb 0000:04:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Your network appears to be starting late in the boot up process.

Thanks for that thorough investigation!!! And here the noob q How to change when network is started before UD? 

 

Or somehow delay the auto mount e.g. 1 min?

Edited March 30, 20188 yr by mrbrowndk
got an idea :)