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


dlandon

Recommended Posts

2 hours ago, luca2 said:

The pass phrase doesn't match:

Sep 22 14:19:59 shogun unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Sep 22 14:19:59 shogun kernel: device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: email@removed.com
Sep 22 14:20:02 shogun unassigned.devices: luksOpen result: No key available with this passphrase. 
Sep 22 14:20:02 shogun unassigned.devices: Partition 'ST8000DM004-2CX188_WCT2AE35' cannot be mounted.

Don't use special characters.  php has trouble with some.

Link to comment
38 minutes ago, dlandon said:

The pass phrase doesn't match:

Sep 22 14:19:59 shogun unassigned.devices: Using disk password to open the 'crypto_LUKS' device.
Sep 22 14:19:59 shogun kernel: device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: email@removed.com
Sep 22 14:20:02 shogun unassigned.devices: luksOpen result: No key available with this passphrase. 
Sep 22 14:20:02 shogun unassigned.devices: Partition 'ST8000DM004-2CX188_WCT2AE35' cannot be mounted.

Don't use special characters.  php has trouble with some.

Thx dlandon! ... that did the trick.

Just curious:

-what is then maximum length accepted for the password ?

-where does UD store the keyfile?

Rgds

Link to comment

I have 11 HDDs connected to Unraid via USB adapters and a USB hub. The USB adapters are from the same manufacturer. They share the same device ID and name. To pass through them to VMs, I have to define the address/bus/port manually. I have done so successfully.

image.png.9533c91ef5fdda85565b3db66c4c82c5.png

 

 

 

The issue is: When I try to mount them via the Unassigned Devices plug, not all the disks are displayed in the UD.

image.png.97bd94a7ebac2bff47519dd4cb6c0a6a.png

The disks found here seem to be random—both the number of them and which disks could have appeared.

If I Mount them, then only those 4 or 5 disks(most times 4 disks) can be found in the /mnt/remotes

 

Any help or ideas would be greatly appreciated!

Link to comment
2 hours ago, hunter6756 said:

I have 11 HDDs connected to Unraid via USB adapters and a USB hub. The USB adapters are from the same manufacturer. They share the same device ID and name. To pass through them to VMs, I have to define the address/bus/port manually. I have done so successfully.

image.png.9533c91ef5fdda85565b3db66c4c82c5.png

 

 

 

The issue is: When I try to mount them via the Unassigned Devices plug, not all the disks are displayed in the UD.

image.png.97bd94a7ebac2bff47519dd4cb6c0a6a.png

The disks found here seem to be random—both the number of them and which disks could have appeared.

If I Mount them, then only those 4 or 5 disks(most times 4 disks) can be found in the /mnt/remotes

 

Any help or ideas would be greatly appreciated!

Your disks are not all being recognized by Unraid as unassigned disks.  The 'Dev 4' disk is the only one being recognized by Unraid as unassigned.

 

'Dev 4' you have marked as 'Passed Through'.  Not sure if you intended to do that.

 

All physical disks are mounted at /mnt/disks/ not /mnt/remotes/.  /mnt/remotes/ is where remote shares are mounted.

 

Post your diagnostics.

Link to comment
8 hours ago, dlandon said:

Your disks are not all being recognized by Unraid as unassigned disks.  The 'Dev 4' disk is the only one being recognized by Unraid as unassigned.

 

'Dev 4' you have marked as 'Passed Through'.  Not sure if you intended to do that.

 

All physical disks are mounted at /mnt/disks/ not /mnt/remotes/.  /mnt/remotes/ is where remote shares are mounted.

 

Post your diagnostics.

Hi dlandon,

Yes, I'm intended to pass through 'Dev 4' to Syno, this one is not the issue.

The others are expected to be 'Mounted' at /mnt/disks/

 

here are my diagnostics.

tower-diagnostics-20210925-0517.zip

Link to comment
28 minutes ago, hunter6756 said:

The others are expected to be 'Mounted' at /mnt/disks/

They are mounted at /mnt/disks/:

Sep 24 01:32:50 Tower unassigned.devices: Successfully mounted '/dev/sdl1' on '/mnt/disks/mybook1'.

Sep 24 01:33:03 Tower unassigned.devices: Successfully mounted '/dev/sdk1' on '/mnt/disks/Elements'.

Sep 24 01:33:19 Tower unassigned.devices: Successfully mounted '/dev/sdg1' on '/mnt/disks/element1'.

etc.

 

Link to comment
23 minutes ago, dlandon said:

They are mounted at /mnt/disks/:

Sep 24 01:32:50 Tower unassigned.devices: Successfully mounted '/dev/sdl1' on '/mnt/disks/mybook1'.

Sep 24 01:33:03 Tower unassigned.devices: Successfully mounted '/dev/sdk1' on '/mnt/disks/Elements'.

Sep 24 01:33:19 Tower unassigned.devices: Successfully mounted '/dev/sdg1' on '/mnt/disks/element1'.

etc.

 

Yes, but only some of them...

 

I got 11 HDDs connented via usb adapters, UD only recognized 5 of them, and only found 4 of them in /mnt/disks/ after 'Mounted'

image.png.6190cf20e83b088d571a5781d629db91.png

 

image.png.66c01af358b61676268612674856bd49.png

Edited by hunter6756
Link to comment
11 minutes ago, hunter6756 said:

Yes, but only some of them...

 

I got 11 HDDs connented via usb adapters, UD only recognized 5 of them, and only found 4 of them in /mnt/disks/ after 'Mounted'

That's correct.  You have a total of 11 disks in the system.  Five are unassigned.  Only disks not in the array are shown as unassigned.  In your case sdh, sdr, sds, sdp, and sdt are unassigned.  The other six disks are in the array.

 

The 'Seagate2' partition is not mounted, so it will not show in /mnt/disks/.

 

If you still think you have a total of 11 USB disks attached, they are not being recognized.  There are apparently issues with the disks:

Sep 24 01:57:32 Tower emhttpd: device /dev/sdh problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdi problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sda problem getting id
Sep 24 01:57:40 Tower kernel: sdh: sdh1
Sep 24 01:57:40 Tower kernel: sd 7:0:0:0: [sdh] Attached SCSI disk
Sep 24 01:57:41 Tower unassigned.devices: Disk with serial 'WDC_WD101EMAZ-11G7DA0_VCGLEWYP', mountpoint 'element1' is not set to auto mount.
Sep 24 01:57:42 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdi problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sda problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sds problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdi problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sds problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdi problem getting id

 

Link to comment
22 minutes ago, dlandon said:

That's correct.  You have a total of 11 disks in the system.  Five are unassigned.  Only disks not in the array are shown as unassigned.  In your case sdh, sdr, sds, sdp, and sdt are unassigned.  The other six disks are in the array.

 

The 'Seagate2' partition is not mounted, so it will not show in /mnt/disks/.

 

If you still think you have a total of 11 USB disks attached, they are not being recognized.  There are apparently issues with the disks:

Sep 24 01:57:32 Tower emhttpd: device /dev/sdh problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdi problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sda problem getting id
Sep 24 01:57:40 Tower kernel: sdh: sdh1
Sep 24 01:57:40 Tower kernel: sd 7:0:0:0: [sdh] Attached SCSI disk
Sep 24 01:57:41 Tower unassigned.devices: Disk with serial 'WDC_WD101EMAZ-11G7DA0_VCGLEWYP', mountpoint 'element1' is not set to auto mount.
Sep 24 01:57:42 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sdi problem getting id
Sep 24 01:57:42 Tower emhttpd: device /dev/sda problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sds problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:57:59 Tower emhttpd: device /dev/sdi problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdb problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdf problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sds problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdq problem getting id
Sep 24 01:58:04 Tower emhttpd: device /dev/sdi problem getting id

 

 

I got 16 disks in total.

4 HDDs connected via Sata, 3 of them are setup in the array, 1 is pass through to Syno.

1 SSD is used as Cache.

Other 11 HDDs are connected via usb adapter. 

image.thumb.png.ffc8bb5b23d7d5e10f98257967edf05c.png

 

 

The issues is with the 11 HDDs connected via usb adapter., not all of them can be recognized.

I can see them in the System Devices.

image.thumb.png.6ec0e047d8b953b4ce240a4a5fd4ce97.png

 

Also I can pass through them into VM by define the Address as below.

    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='7'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='8'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='9'/>
      </source>
      <address type='usb' bus='0' port='4'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='10'/>
      </source>
      <address type='usb' bus='0' port='5'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='11'/>
      </source>
      <address type='usb' bus='0' port='6'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='12'/>
      </source>
      <address type='usb' bus='0' port='7'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='13'/>
      </source>
      <address type='usb' bus='0' port='8'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='14'/>
      </source>
      <address type='usb' bus='0' port='9'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='15'/>
      </source>
      <address type='usb' bus='0' port='10'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='16'/>
      </source>
      <address type='usb' bus='0' port='11'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='yes'>
      <source>
        <address bus='2' device='17'/>
      </source>
      <address type='usb' bus='0' port='12'/>
    </hostdev>

 

The problem is: how can I pass through them to a Docker?

I'm not able to define the PATH in docker if UD can't recognize them properly.

Link to comment

Hi Big fan!

 

I just added a new UAD drive that I wanted to replace with a new bigger drive

 

Adding and mounting the drive was no problem

I then ran the:

 

rsync -avPX /mnt/disks/SEED/ /mnt/disks/SEED18

Also did a update of any new files:

rsync -auv /mnt/disks/SEED/ /mnt/disks/SEED18

 

Quote

Update: Did I miss a "/" on the old drive? did I copy the partition?

 

I then renamed the new drive to the old drive name and stopped and started the Array

And now it looks like I have a partition on the new drive in the size of the old one?

But it looked okay before the restart?

 

image.thumb.png.7809e5f8ecf23bb85d6ea5e119124a13.png

 

Also why does the FS for the format says "luks" ? before reboot it was "xfs,xfs"

 

Link to comment
11 hours ago, dlandon said:
Sep 24 01:57:32 Tower emhttpd: device /dev/sdh problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdd problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sde problem getting id
Sep 24 01:57:32 Tower emhttpd: device /dev/sdb problem getting id

This means the devices have all the same ID, quite common with USB devices, in this case:

 

Sep 23 22:18:59 Tower kernel: scsi 8:0:0:0: Direct-Access     JMicron  Generic          0209 PQ: 0 ANSI: 6

 

That won't work with Unraid, it requires each device to have a unique identification.

Link to comment
21 minutes ago, casperse said:

Hi Big fan!

 

I just added a new UAD drive that I wanted to replace with a new bigger drive

 

Adding and mounting the drive was no problem

I then ran the:

 

rsync -avPX /mnt/disks/SEED/ /mnt/disks/SEED18

Also did a update of any new files:

rsync -auv /mnt/disks/SEED/ /mnt/disks/SEED18

 

 

I then renamed the new drive to the old drive name and stopped and started the Array

And now it looks like I have a partition on the new drive in the size of the old one?

But it looked okay before the restart?

 

image.thumb.png.7809e5f8ecf23bb85d6ea5e119124a13.png

 

Also why does the FS for the format says "luks" ? before reboot it was "xfs,xfs"

 

Removed the partition on the new drive and formattet id with XFS encrupt. did a reboote and now have the old drive with xfs, xfs again?

image.thumb.png.b09d51199e6b0ff3279745f0fd1314c1.png

 

Link to comment

I'm getting the following syntax error.

 

Warning: syntax error, unexpected '!' in Unknown on line 41 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1834

 

This is a new Unraid server and I've temporarily connected a USB3 Probox drive encloser with 4 sata drives until I can complete coping the data of it. I also have two sata drives connected to sata ports on the Intel Z170 motherboard.  The Unraid array itself is using a LSI HBA. 

 

As far as I have found the syntax error has not impeded the functionality of the UD plugin.

unraidserver-diagnostics-20210926-0245.zip

Link to comment
4 hours ago, docfallingapart said:

I'm getting the following syntax error.

 

Warning: syntax error, unexpected '!' in Unknown on line 41 in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 1834

 

This is a new Unraid server and I've temporarily connected a USB3 Probox drive encloser with 4 sata drives until I can complete coping the data of it. I also have two sata drives connected to sata ports on the Intel Z170 motherboard.  The Unraid array itself is using a LSI HBA. 

 

As far as I have found the syntax error has not impeded the functionality of the UD plugin.

unraidserver-diagnostics-20210926-0245.zip 212.32 kB · 1 download

Can you post the output of the following command:

cat /var/state/unassigned.devices/unassigned.devices.ini

 

Link to comment
2 hours ago, dlandon said:
cat /proc/mounts
rootfs / rootfs rw,size=32739196k,nr_inodes=8184799 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,relatime,size=32739204k,nr_inodes=8184801,mode=755 0 0
devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /dev/shm tmpfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
cgroup_root /sys/fs/cgroup tmpfs rw,relatime,size=8192k,mode=755 0 0
cpuset /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
cpu /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
cpuacct /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
blkio /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
memory /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
devices /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
freezer /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
net_cls /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls 0 0
perf_event /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
net_prio /sys/fs/cgroup/net_prio cgroup rw,relatime,net_prio 0 0
hugetlb /sys/fs/cgroup/hugetlb cgroup rw,relatime,hugetlb 0 0
pids /sys/fs/cgroup/pids cgroup rw,relatime,pids 0 0
tmpfs /var/log tmpfs rw,relatime,size=131072k,mode=755 0 0
/dev/sda1 /boot vfat rw,noatime,nodiratime,fmask=0177,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,flush,errors=remount-ro 0 0
/dev/loop0 /lib/modules squashfs ro,relatime 0 0
/dev/loop1 /lib/firmware squashfs ro,relatime 0 0
hugetlbfs /hugetlbfs hugetlbfs rw,relatime,pagesize=2M 0 0
overlay /lib/modules overlay rw,relatime,lowerdir=/lib/modules,upperdir=/var/local/overlay/lib/modules,workdir=/var/local/overlay-work/lib/modules 0 0
overlay /lib/firmware overlay rw,relatime,lowerdir=/lib/firmware,upperdir=/var/local/overlay/lib/firmware,workdir=/var/local/overlay-work/lib/firmware 0 0
rootfs /mnt rootfs rw,size=32739196k,nr_inodes=8184799 0 0
tmpfs /mnt/disks tmpfs rw,relatime,size=1024k 0 0
tmpfs /mnt/remotes tmpfs rw,relatime,size=1024k 0 0
nfsd /proc/fs/nfs nfsd rw,relatime 0 0
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0
tmpfs /tmp/EmbyRamScratch tmpfs rw,relatime,size=8388608k 0 0
tmpfs /tmp/PlexRamScratch tmpfs rw,relatime,size=8388608k 0 0
tmpfs /tmp/EmbyRamScratch tmpfs rw,relatime,size=8388608k 0 0
tmpfs /tmp/PlexRamScratch tmpfs rw,relatime,size=8388608k 0 0
/dev/mapper/md1 /mnt/disk1 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md2 /mnt/disk2 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md3 /mnt/disk3 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md4 /mnt/disk4 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md5 /mnt/disk5 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md6 /mnt/disk6 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md7 /mnt/disk7 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md8 /mnt/disk8 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md9 /mnt/disk9 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md10 /mnt/disk10 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md11 /mnt/disk11 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md12 /mnt/disk12 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md13 /mnt/disk13 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md14 /mnt/disk14 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md15 /mnt/disk15 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md17 /mnt/disk17 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md18 /mnt/disk18 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md19 /mnt/disk19 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md20 /mnt/disk20 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md21 /mnt/disk21 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/md22 /mnt/disk22 xfs rw,noatime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/nvme0n1p1 /mnt/cache btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0
shfs /mnt/user0 fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0
shfs /mnt/user fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0
tmpfs /tmp/EmbyRamScratch tmpfs rw,relatime,size=8388608k 0 0
tmpfs /tmp/PlexRamScratch tmpfs rw,relatime,size=8388608k 0 0
/dev/loop2 /var/lib/docker btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0
/dev/loop2 /var/lib/docker/btrfs btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0
/dev/loop3 /etc/libvirt btrfs rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/ 0 0
nsfs /var/run/docker/netns/default nsfs rw 0 0
nsfs /var/run/docker/netns/af0ca5d48ca0 nsfs rw 0 0
nsfs /var/run/docker/netns/c69b5061ae08 nsfs rw 0 0
nsfs /var/run/docker/netns/a2eec510e8c2 nsfs rw 0 0
nsfs /var/run/docker/netns/6d7e60f58521 nsfs rw 0 0
nsfs /var/run/docker/netns/2f86374148d1 nsfs rw 0 0
nsfs /var/run/docker/netns/08afabb265ec nsfs rw 0 0
nsfs /var/run/docker/netns/e56b4af7f70b nsfs rw 0 0
nsfs /var/run/docker/netns/c6f9f26bc3bc nsfs rw 0 0
nsfs /var/run/docker/netns/bea51fff217e nsfs rw 0 0
nsfs /var/run/docker/netns/d331e0d43b95 nsfs rw 0 0
nsfs /var/run/docker/netns/fcc5d03ff157 nsfs rw 0 0
nsfs /var/run/docker/netns/4942e60e1f4d nsfs rw 0 0
nsfs /var/run/docker/netns/80bd94893048 nsfs rw 0 0
nsfs /var/run/docker/netns/c2d0c3ca95d4 nsfs rw 0 0
nsfs /var/run/docker/netns/0ed243b5f45c nsfs rw 0 0
nsfs /var/run/docker/netns/a4af87ec6a28 nsfs rw 0 0
nsfs /var/run/docker/netns/a43c3a83de47 nsfs rw 0 0
/dev/mapper/SEED /mnt/disks/SEED xfs rw,noatime,nodiratime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
/dev/mapper/SEED_NEW /mnt/disks/SEED_NEW xfs rw,noatime,nodiratime,attr2,inode64,logbufs=8,logbsize=32k,noquota 0 0
nsfs /var/run/docker/netns/5da03b4a5235 nsfs rw 0 0
nsfs /var/run/docker/netns/f27c01f97146 nsfs rw 0 0
nsfs /var/run/docker/netns/0596f205e063 nsfs rw 0 0
nsfs /var/run/docker/netns/f5960a6c3a6b nsfs rw 0 0
nsfs /var/run/docker/netns/78640e0fa51f nsfs rw 0 0
nsfs /var/run/docker/netns/dec306ebfaa4 nsfs rw 0 0
nsfs /var/run/docker/netns/2058a66d1423 nsfs rw 0 0

 

Link to comment

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.