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

There is a new feature in UD to help with plugins that need a mount point folder. UD now creates a mount folder '/mnt/addons'. This folder should be used to mount your plugin devices to prevent FCP warnings and keep your mounts separated from UD. It is recommended you switch to this new folder for your addon and custom mounts. You are welcome to leave the mounts at '/mnt/disks' or '/mnt/remotes'. Things will still work, but if you request support for UD issues, you will be asked to remove t

UD is now creating a mount point folder for plugins and addons

Recommended by dlandon

Squid

March 12, 20251 yr

Try this. Under the sharing options, check off the user for the Mac to store windows creds in a less secure manner but which gives greater compatibility

Recommended by Squid

January 30, 20233 yr

gringotts-diagnostics-20230129-1949.zip

Quote

Replies 11.9k
Views 2.1m
Created 10 yr10 yr
Last Reply Jun 26Jun 26

Popular Days

Posted Images

January 30, 20233 yr

Author

15 minutes ago, Andrew Dens said:

gringotts-diagnostics-20230129-1949.zip 177.92 kB · 0 downloads

Your disk appears to not be cleared of the previous ZFS file system:

Jan 29 19:48:07 Gringotts unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Jan 29 19:48:07 Gringotts unassigned.devices: Formatting disk '/dev/nvme0n1' with 'xfs' filesystem.
Jan 29 19:48:07 Gringotts unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/nvme0n1p1' 2>&1
Jan 29 19:48:07 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1 since it has a dos partition already
Jan 29 19:48:07 Gringotts  zed[4418]: zed_disk_event:
Jan 29 19:48:07 Gringotts  zed[4418]: #011class: EC_dev_add
Jan 29 19:48:07 Gringotts  zed[4418]: #011subclass: disk
Jan 29 19:48:07 Gringotts  zed[4418]: #011dev_name: /dev/nvme0n1p1
Jan 29 19:48:07 Gringotts  zed[4418]: #011path: /devices/pci0000:00/0000:00:01.2/0000:01:00.2/0000:02:00.0/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1
Jan 29 19:48:07 Gringotts  zed[4418]: #011devid: nvme-CT500P2SSD8_2151E5F48096-part1
Jan 29 19:48:07 Gringotts  zed[4418]: #011dev_size: 500106813440
Jan 29 19:48:07 Gringotts  zed[4418]: #011dev_parent_size: 500107862016
Jan 29 19:48:07 Gringotts  zed[4418]: zfs_slm_event: EC_dev_add.disk
Jan 29 19:48:07 Gringotts  zed[4418]: zfs_deliver_add: adding nvme-CT500P2SSD8_2151E5F48096-part1 (NULL) (is_slice 1)
Jan 29 19:48:07 Gringotts  zed[4418]: zfs_iter_pool: evaluating vdevs on ZFS50 (by devid)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_9MGZE6PJ-part1)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_9MHUW33U-part1)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_Y5KUR3EC-part1)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_Y5KUR47C-part1)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_Y6GJNR7D-part1)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B2DA2_2CGKS72N-part1)
Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev (null))
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan 29 19:48:22 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)
Jan 29 19:48:24 Gringotts unassigned.devices: Format disk '/dev/nvme0n1' with 'xfs' filesystem: meta-data=/dev/nvme0n1p1         isize=512    agcount=4, agsize=30524098 blks          =                       sectsz=512   attr=2, projid32bit=1          =                       crc=1        finobt=1, sparse=1, rmapbt=0          =                       reflink=1    bigtime=1 inobtcount=1 data     =                       bsize=4096   blocks=122096390, imaxpct=25          =                       sunit=0      swidth=0 blks naming   =version 2              bsize=4096   ascii-ci=0, ftype=1 log      =internal log           bsize=4096   blocks=59617, version=2          =                       sectsz=512   sunit=0 blks, lazy-count=1 realtime =none                   extsz=4096   blocks=0, rtextents=0 Discarding blocks...Done.
Jan 29 19:48:27 Gringotts unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Jan 29 19:48:27 Gringotts kernel: nvme0n1: p1
Jan 29 19:48:27 Gringotts unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Jan 29 19:48:27 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)
Jan 29 19:48:27 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1 since it has a dos partition already
Jan 29 19:48:27 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jan 29 19:48:30 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1 since it has a dos partition already
Jan 29 19:48:30 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)

Try clearing the disk with UD by clicking on the rec 'X' next to the serial number to clear the disk. That should clear out everything.

Quote

January 30, 20233 yr

Your disk appears to not be cleared of the previous ZFS file system:

Jan 29 19:48:07 Gringotts unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition tableJan 29 19:48:07 Gringotts unassigned.devices: Formatting disk '/dev/nvme0n1' with 'xfs' filesystem.Jan 29 19:48:07 Gringotts unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/nvme0n1p1' 2>&1Jan 29 19:48:07 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1 since it has a dos partition alreadyJan 29 19:48:07 Gringotts  zed[4418]: zed_disk_event:Jan 29 19:48:07 Gringotts  zed[4418]: #011class: EC_dev_addJan 29 19:48:07 Gringotts  zed[4418]: #011subclass: diskJan 29 19:48:07 Gringotts  zed[4418]: #011dev_name: /dev/nvme0n1p1Jan 29 19:48:07 Gringotts  zed[4418]: #011path: /devices/pci0000:00/0000:00:01.2/0000:01:00.2/0000:02:00.0/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1Jan 29 19:48:07 Gringotts  zed[4418]: #011devid: nvme-CT500P2SSD8_2151E5F48096-part1Jan 29 19:48:07 Gringotts  zed[4418]: #011dev_size: 500106813440Jan 29 19:48:07 Gringotts  zed[4418]: #011dev_parent_size: 500107862016Jan 29 19:48:07 Gringotts  zed[4418]: zfs_slm_event: EC_dev_add.diskJan 29 19:48:07 Gringotts  zed[4418]: zfs_deliver_add: adding nvme-CT500P2SSD8_2151E5F48096-part1 (NULL) (is_slice 1)Jan 29 19:48:07 Gringotts  zed[4418]: zfs_iter_pool: evaluating vdevs on ZFS50 (by devid)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_9MGZE6PJ-part1)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_9MHUW33U-part1)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_Y5KUR3EC-part1)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_Y5KUR47C-part1)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B1PA0_Y6GJNR7D-part1)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev ata-WDC_WD140EDGZ-11B2DA2_2CGKS72N-part1)Jan 29 19:48:07 Gringotts  zed[4418]:   zfs_iter_vdev: no match (nvme-CT500P2SSD8_2151E5F48096-part1 != vdev (null))### [PREVIOUS LINE REPEATED 1 TIMES] ###Jan 29 19:48:22 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)Jan 29 19:48:24 Gringotts unassigned.devices: Format disk '/dev/nvme0n1' with 'xfs' filesystem: meta-data=/dev/nvme0n1p1         isize=512    agcount=4, agsize=30524098 blks          =                       sectsz=512   attr=2, projid32bit=1          =                       crc=1        finobt=1, sparse=1, rmapbt=0          =                       reflink=1    bigtime=1 inobtcount=1 data     =                       bsize=4096   blocks=122096390, imaxpct=25          =                       sunit=0      swidth=0 blks naming   =version 2              bsize=4096   ascii-ci=0, ftype=1 log      =internal log           bsize=4096   blocks=59617, version=2          =                       sectsz=512   sunit=0 blks, lazy-count=1 realtime =none                   extsz=4096   blocks=0, rtextents=0 Discarding blocks...Done.Jan 29 19:48:27 Gringotts unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.Jan 29 19:48:27 Gringotts kernel: nvme0n1: p1Jan 29 19:48:27 Gringotts unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition tableJan 29 19:48:27 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)Jan 29 19:48:27 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1 since it has a dos partition alreadyJan 29 19:48:27 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)### [PREVIOUS LINE REPEATED 1 TIMES] ###Jan 29 19:48:30 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1 since it has a dos partition alreadyJan 29 19:48:30 Gringotts  zed[4418]: zed_udev_monitor: skip /dev/nvme0n1p1 (in use by xfs)

Try clearing the disk with UD by clicking on the rec 'X' next to the serial number to clear the disk. That should clear out everything.

Yeah I tried clearing the disk a few times with UD and formatting twice no luck with that either. I figured it was an issue with the old zfs pool since I never was able to destroy that pool when it became corrupted so I removed the devices and I don’t see it listed anywhere using zpool status

Sent from my iPhone using Tapatalk

Quote

January 30, 20233 yr

Sounds like the drive might have died and gone read-only, which would be the original reason for the pool corruption. Would try installing it in another system and trying to do things to it there but it'll likely be the same.

Quote

January 30, 20233 yr

Author

8 hours ago, Andrew Dens said:

Yeah I tried clearing the disk a few times with UD and formatting twice no luck with that either. I figured it was an issue with the old zfs pool since I never was able to destroy that pool when it became corrupted so I removed the devices and I don’t see it listed anywhere using zpool status

Sent from my iPhone using Tapatalk

In working with the zfs feature comming in 6.12 and doing some testing, it seems UD is not clearing off the zfs signature correctly on a zfs formatted disk. I'm looking into a solution.

Quote

January 30, 20233 yr

I tried zeroing out the device with preclear UD plugin, no luck. I plugged it into a windows pc and formatted it there as ntfs and then plugged back into unraid and that was able to mount by unassigned devices. Then I unmounted, cleared with UD, then tried to format as XFS/BTRFS and NTFS and it's still grey it won't allow mounting.

Quote

January 30, 20233 yr

Author

2 minutes ago, Andrew Dens said:

I tried zeroing out the device with preclear UD plugin, no luck. I plugged it into a windows pc and formatted it there as ntfs and then plugged back into unraid and that was able to mount by unassigned devices. Then I unmounted, cleared with UD, then tried to format as XFS/BTRFS and NTFS and it's still grey it won't allow mounting.

Post diagnostics.

Quote

January 30, 20233 yr

gringotts-diagnostics-20230130-1025.zip

Quote

January 30, 20233 yr

Something I noticed that might be part of the problem is when i do ls /dev/disk/by-id I see 2 different nvme drives even though there's only one plugged in? I can try with the nvme drive unplugged and starting up unraid to see what happens or plugging in a different nvme I have a few hot spares of the same brand from the raid 10 before

root@Gringotts:~# ls /dev/disk/by-id | grep nvme
nvme-CT500P2SSD8_2151E5F48096@
nvme-CT500P2SSD8_2151E5F48096-part1@
nvme-nvme.c0a9-323135314535463438303936-4354353030503253534438-00000001@
nvme-nvme.c0a9-323135314535463438303936-4354353030503253534438-00000001-part1@

Edited January 30, 20233 yr by Andrew Dens

Quote

January 30, 20233 yr

Author

5 minutes ago, dlandon said:

Post diagnostics.

Go to a command line and do the following commands and post the results:

zpool import -d /dev/sdX
and
zpool import -d /dev/sdX1

Where sdX is the device designation.

Quote

January 30, 20233 yr

10 minutes ago, Andrew Dens said:

I tried zeroing out the device with preclear UD plugin, no luck. I plugged it into a windows pc and formatted it there as ntfs and then plugged back into unraid and that was able to mount by unassigned devices. Then I unmounted, cleared with UD, then tried to format as XFS/BTRFS and NTFS and it's still grey it won't allow mounting.

This command may clear it, be extra sure you point it at the right device.

sgdisk -Z /dev/<device>

Quote

January 30, 20233 yr

Author

3 minutes ago, Andrew Dens said:

Something I noticed that might be part of the problem is when i do ls /dev/disk/by-id I see 2 different nvme drives even though there's only one plugged in? I can try and keeping the nvme drive unplugged and starting up unraid to see what happens or plugging in a different nvme I have a few hot spares of the same brand from the raid 10 i put together

root@Gringotts:~# ls /dev/disk/by-id | grep nvme
nvme-CT500P2SSD8_2151E5F48096@
nvme-CT500P2SSD8_2151E5F48096-part1@
nvme-nvme.c0a9-323135314535463438303936-4354353030503253534438-00000001@
nvme-nvme.c0a9-323135314535463438303936-4354353030503253534438-00000001-part1@

The disk and partition have separate entries. The partition is the one with the -part1 at the end.

Quote

January 30, 20233 yr

Author

Just now, Lev said:
This command may clear it, be extra sure you point it at the right device.
sgdisk -Z /dev/<device>

I'm not sure. The issue with a zpool disk is the zpool signature that is probably left on the disk.

Quote

January 30, 20233 yr

11 minutes ago, dlandon said:
Go to a command line and do the following commands and post the results:
zpool import -d /dev/sdX
and
zpool import -d /dev/sdX1

Where sdX is the device designation.

10 minutes ago, Lev said:
This command may clear it, be extra sure you point it at the right device.
sgdisk -Z /dev/<device>

root@Gringotts:~# ls /dev/nv*
/dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1
root@Gringotts:~# zpool import -d /dev/nvme0n1
no pools available to import

root@Gringotts:~# sgdisk -Z /dev/nvme0n1

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************

Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.

--- edit

I tried formatting with UD after doing the above and it's still got a grey mount button with UD. Appreciate the help guys this issue really stumped me.

Edited January 30, 20233 yr by Andrew Dens

Quote

January 30, 20233 yr

7 minutes ago, Andrew Dens said:

root@Gringotts:~# ls /dev/nv*
/dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1
root@Gringotts:~# zpool import -d /dev/nvme0n1
no pools available to import

root@Gringotts:~# sgdisk -Z /dev/nvme0n1

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************

Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.

Show me the output of this command. The -n means it will take no action, it'll just output a list of partitions.

wipefs -n /dev/<device>

Quote

January 30, 20233 yr

3 minutes ago, Lev said:
Show me the output of this command. The -n means it will take no action, it'll just output a list of partitions.
wipefs -n /dev/<device>

root@Gringotts:~# wipefs -n /dev/nvme0n1
DEVICE OFFSET TYPE UUID LABEL
nvme0n1 0x1fe dos

---

I had attempted to format as xfs on UD before running that command

Edited January 30, 20233 yr by Andrew Dens

Quote

January 30, 20233 yr

2 minutes ago, Andrew Dens said:

root@Gringotts:~# wipefs -n /dev/nvme0n1
DEVICE OFFSET TYPE UUID LABEL
nvme0n1 0x1fe dos

I'm out of things to suggest to try in UnRAID. Does it the drive still work and partition OK in Windows?

Last option I'd try in Windows is using whatever app Crucial has to wipe the drive and make sure it's got the latest firmware update.

Good luck to you.

Quote

January 30, 20233 yr

No worries yeah it does fine, as a workaround for now I guess i'll just format it on windows and then keep it as NTFS windows partitioned then setting it to mount in unraid as that or make a single zfs pool in unraid with this disk and try that.

Edited January 30, 20233 yr by Andrew Dens

Quote

February 1, 20233 yr

Got this error:

Feb  1 11:07:34 towerpve unassigned.devices: Mounting 'Auto Mount' Remote Shares...
Feb  1 11:07:35 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:37 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:38 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:41 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:44 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:47 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:50 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:52 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:53 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:56 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:07:59 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:08:02 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:08:05 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:08:07 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:08:08 towerpve root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
Feb  1 11:09:35 towerpve unassigned.devices: Cannot 'Auto Mount' Remote Shares.  Network not available!

Seems the share wants to mount before network is up - I got no option the reconnect since it is grayed out. I'm sure I'm not the first one but going though 342 pages is a bit much And don't let name of the unraid-server fool you - it runs directly on bare-metal. Not as vm

Quote

February 1, 20233 yr

Author

Post diagnostics.

Quote

February 1, 20233 yr

1 hour ago, dlandon said:

Post diagnostics.

towerpve-diagnostics-20230201-1405.zip

Quote

February 1, 20233 yr

Author

17 minutes ago, sjoerd said:

towerpve-diagnostics-20230201-1405.zip 97.2 kB · 0 downloads

UD waits for the network to start for two minutes as indicated by the time stamps on the log messages:

Feb  1 12:02:42 towerpve unassigned.devices: Mounting 'Auto Mount' Remote Shares...
Feb  1 12:03:54 towerpve webGUI: Successful login user root from 10.34.51.69
Feb  1 12:04:01 towerpve kernel: mdcmd (38): nocheck pause
Feb  1 12:04:02 towerpve kernel: md: recovery thread: exit status: -4
Feb  1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered blocking state
Feb  1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered disabled state
Feb  1 12:04:13 towerpve kernel: device vnet0 entered promiscuous mode
Feb  1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered blocking state
Feb  1 12:04:13 towerpve kernel: br0: port 2(vnet0) entered forwarding state
Feb  1 12:04:14 towerpve  avahi-daemon[5414]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:feaf:b722.
Feb  1 12:04:14 towerpve  avahi-daemon[5414]: New relevant interface vnet0.IPv6 for mDNS.
Feb  1 12:04:14 towerpve  avahi-daemon[5414]: Registering new address record for fe80::fc54:ff:feaf:b722 on vnet0.*.
Feb  1 12:04:44 towerpve unassigned.devices: Cannot 'Auto Mount' Remote Shares.  Network not available!

Check your network Gateway setting.

Quote

February 1, 20233 yr

Ah I see

root@towerpve:~# ping tower
ping: tower: Name or service not known
root@towerpve:~# ping tower.local
PING tower.local (10.34.51.54) 56(84) bytes of data.
64 bytes from tower.local (10.34.51.54): icmp_seq=1 ttl=64 time=0.284 ms
64 bytes from tower.local (10.34.51.54): icmp_seq=2 ttl=64 time=0.232 ms
64 bytes from tower.local (10.34.51.54): icmp_seq=3 ttl=64 time=0.251 ms
64 bytes from tower.local (10.34.51.54): icmp_seq=4 ttl=64 time=0.247 ms

towerpve is requesting pihole for tower... should fix that

Quote

February 2, 20233 yr

Hi all, I had a question about moving files from my external hard drives to my UnRAID server. I suspect I'm just overlooking something really obvious as I'm a beginner. I have the Unassigned Devices+ plugin installed, but I'm unable to mount some hfs+ and apfs partitions. On my computer I'm able to access these drives normally, so it doesn't seem like there's something up with the drives themselves. Does anyone know what it might be?

Thanks in advance!

Edited February 2, 20233 yr by lil-nas-x
added extra information

Quote

February 2, 20233 yr

Author

2 hours ago, lil-nas-x said:

Hi all, I had a question about moving files from my external hard drives to my UnRAID server. I suspect I'm just overlooking something really obvious as I'm a beginner. I have the Unassigned Devices+ plugin installed, but I'm unable to mount some hfs+ and apfs partitions. On my computer I'm able to access these drives normally, so it doesn't seem like there's something up with the drives themselves. Does anyone know what it might be?

Thanks in advance!

Post diagnostics.

On the apfs that won’t mount, click the drive settings (three gears) and set a different partition to mount. The bottom hpfs disk I don’t understand. The diagnostics will help me see what is going on.

Quote

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.

Followers

Go to topic listing

Replies 11.9k
Views 2.1m
Created 10 yr10 yr
Last Reply Jun 26Jun 26

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

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

dlandon

dlandon

dlandon

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

dlandon

dlandon

dlandon

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)