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


Recommended Posts

just rebooted

Try to call the unassigned (and shared) Ubuntu disk....

Unfortunately - no change...

UD sees the Ubuntu machine - I log in with the smb username and password (different than passwd of local machine user) - then domain (I leave that open) then shares...... UD cannot find any share.

Windows 10 finds the share immediately and can open the folder

Greyed out in Unraid...

Are there perhaps other issues within unraid, which might be misconfigured ?

Link to comment
9 minutes ago, ullibelgie said:

just rebooted

Try to call the unassigned (and shared) Ubuntu disk....

Unfortunately - no change...

UD sees the Ubuntu machine - I log in with the smb username and password (different than passwd of local machine user) - then domain (I leave that open) then shares...... UD cannot find any share.

Windows 10 finds the share immediately and can open the folder

Greyed out in Unraid...

Are there perhaps other issues within unraid, which might be misconfigured ?

As I said, the only thing that gray's out the device ball and mount button is a ping problem.  The file system has nothing to do with it.

 

Run this command and post the results:

cat /var/state/unassigned.devices/ping_status.json

 

Link to comment
13 minutes ago, ullibelgie said:

just rebooted

Try to call the unassigned (and shared) Ubuntu disk....

Unfortunately - no change...

UD sees the Ubuntu machine - I log in with the smb username and password (different than passwd of local machine user) - then domain (I leave that open) then shares...... UD cannot find any share.

Windows 10 finds the share immediately and can open the folder

Greyed out in Unraid...

Are there perhaps other issues within unraid, which might be misconfigured ?

Are you using the ip address or server name to reference the remote server?

Link to comment

here is the result from UD-terminal:

 

root@Tower:~# cat /var/state/unassigned.devices/ping_status.json
{"ON5KQ-X8DA3":{"timestamp":1628176963,"no_pings":0,"online":"no","changed":"no"},"192.168.1.120":{"timestamp":1628177166,"no_pings":0,"online":"yes","changed":"yes"}}root@Tower:~# ^C

 

I used both:

At first tried at first with just the found servername... - no shares could be found from the wizard

Then I tried again with the IP-adres 192.168.1.120 (the Ubuntu-client) - at least the $print share could be found at the end, but not the shared folders....

see above result from terminal

 

 

Link to comment
1 minute ago, ullibelgie said:

here is the result from UD-terminal:

 

root@Tower:~# cat /var/state/unassigned.devices/ping_status.json
{"ON5KQ-X8DA3":{"timestamp":1628176963,"no_pings":0,"online":"no","changed":"no"},"192.168.1.120":{"timestamp":1628177166,"no_pings":0,"online":"yes","changed":"yes"}}root@Tower:~# ^C

 

I used both:

At first tried at first with just the found servername... - no shares could be found from the wizard

Then I tried again with the IP-adres 192.168.1.120 (the Ubuntu-client) - at least the $print share could be found at the end, but not the shared folders....

see above result from terminal

 

 

Use the IP address and then post the ping status file.  UD thinks the server is offline.  You'll probably have to enter the share manually if UD can't look it up.

Link to comment

whow, this works indeed:

 

input manually the Ubuntu-client IP-adress:  192.168.1.120

then input smb user registered at the Ubuntu-client

then input passwd for that user

then manually input the shared folder name....

 

Bingo!

A green smb unassigned disk shows up

 

However it cannot be mounted....;-(

 

response from the UD-terminal:

 

root@Tower:~# cat /var/state/unassigned.devices/ping_status.json
{"ON5KQ-X8DA3":{"timestamp":1628176963,"no_pings":0,"online":"no","changed":"no"},"192.168.1.120":{"timestamp":1628178231,"no_pings":0,"online":"yes","changed":"no"}}root@Tower:~#

Link to comment
12 minutes ago, ullibelgie said:

whow, this works indeed:

 

input manually the Ubuntu-client IP-adress:  192.168.1.120

then input smb user registered at the Ubuntu-client

then input passwd for that user

then manually input the shared folder name....

 

Bingo!

A green smb unassigned disk shows up

 

However it cannot be mounted....;-(

 

response from the UD-terminal:

 

root@Tower:~# cat /var/state/unassigned.devices/ping_status.json
{"ON5KQ-X8DA3":{"timestamp":1628176963,"no_pings":0,"online":"no","changed":"no"},"192.168.1.120":{"timestamp":1628178231,"no_pings":0,"online":"yes","changed":"no"}}root@Tower:~#

Look at the syslog and it should tell you why it won't mount.  You do realize you need to click the 'Mount' button to get it to mount?

Link to comment

Now I found the following:

- the original shared folder "backup' can be SMB imported with green dot, but not mounted

- I made additional folder 'another' which can also be Smb imported with green dot and also mounted....

So the newly written folder another works perfectly - I have just tried that...

 

Difference:

'backup' contains zip-file of a database

'another' contains only simple txt file

 

I have no problems to erase 'backup' folder, as it was only a test with a just formatted FAT32 disk on the Ubuntu server...

But why this happened ? I have no idea...

Link to comment
Just now, ullibelgie said:

Yes, indeed - mounting is not automatically process - it needs manual click... ;-)

may be there is something wrong with the old shared folder... will check the syslog...

 

I think it works now !

 

"Waiter, could you please bring two more beer for the experts how helped me..." .....;-)

Most likely the issue is permissions.  The syslog will tell you.

Link to comment

While preparing for a backup, I pre-cleared a 1Tb external USB-Harddisk  with unassigned disk plug-in

After 18hours it was finished successfully...

 

Now I format the disk XFS with unassigned disk plug-in - however after short time a "FAIL" pop-up window appears and the UD-log shows:

------------------------------

FS: xfs

/sbin/xfs_repair -n /dev/sdf1 2>&1

Phase 1 - find and verify superblock...
bad primary superblock - filesystem mkfs-in-progress bit set !!!

attempting to find secondary superblock...
-----------------------------

 

It already runs for half an hour...

grafik.thumb.png.024e0f217fe2609de1ffaf0b9470f244.png

 

What to do ? just wait ....

The number of reads and writes is still growing - so there is something running in the background....

 

Thanks for advice

Link to comment

It seams, I need to be more patient...hi

As I wrote my previous post, the formatting seemed to be repaired ?!

 

I could also mount the USB disk now

The log shows now:

grafik.thumb.png.a4349eb6d0192455ddfc93b3aa64d5a7.png

 

So , I believe the issue is solved and I can start the backup on this USB disk , right ?

 

Can someone explain to me what happened before - why the format procedere throwed the alert pop-up "FAIL" before?

Link to comment
2 hours ago, ullibelgie said:

It seams, I need to be more patient...hi

As I wrote my previous post, the formatting seemed to be repaired ?!

 

I could also mount the USB disk now

The log shows now:

grafik.thumb.png.a4349eb6d0192455ddfc93b3aa64d5a7.png

 

So , I believe the issue is solved and I can start the backup on this USB disk , right ?

 

Can someone explain to me what happened before - why the format procedere throwed the alert pop-up "FAIL" before?

Post diagnostics.

Link to comment
4 minutes ago, ullibelgie said:

Here is the Diagnostics file:

 

Diagnostics.zip 144.33 kB · 1 download

Your disk has a problem:

Aug  7 09:36:05 Tower unassigned.devices: Formatting disk '/dev/sdf' with 'xfs' filesystem.
Aug  7 09:36:06 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:06 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 38 5a f0 00 00 f0 00
Aug  7 09:36:06 Tower kernel: print_req_error: 2 callbacks suppressed
Aug  7 09:36:06 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976771824 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:06 Tower emhttpd: read SMART /dev/sdf
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e1 10 00 00 f0 00
Aug  7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976871696 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e2 00 00 00 f0 00
Aug  7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976871936 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e2 f0 00 00 f0 00
Aug  7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872176 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e3 e0 00 00 f0 00
Aug  7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872416 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e4 d0 00 00 f0 00
Aug  7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872656 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:08 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e5 c0 00 00 f0 00
Aug  7 09:36:08 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976872896 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e6 b0 00 00 80 00
Aug  7 09:36:09 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976873136 op 0x1:(WRITE) flags 0x0 phys_seg 16 prio class 0
Aug  7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e7 30 00 00 f0 00
Aug  7 09:36:09 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976873264 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Aug  7 09:36:09 Tower kernel: sd 5:0:0:0: [sdf] tag#0 CDB: opcode=0x2a 2a 00 3a 39 e8 20 00 00 f0 00
Aug  7 09:36:09 Tower kernel: blk_update_request: I/O error, dev sdf, sector 976873504 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
Aug  7 09:36:09 Tower kernel: floppy: error 10 while reading block 0
### [PREVIOUS LINE REPEATED 5 TIMES] ###

I wouldn't use the disk until you sort this out.

Link to comment

Hi,

 

is it possible to mount two different external USB Disks to the same mount point (not at the same time!). Background: i wanna use two USB Disks in periodicaly exchange for a backup script and it would be easier if can use only one mount point for the two disks in the backup script.

 

Thank You!

Link to comment
14 minutes ago, Shantarius said:

Hi,

 

is it possible to mount two different external USB Disks to the same mount point (not at the same time!). Background: i wanna use two USB Disks in periodicaly exchange for a backup script and it would be easier if can use only one mount point for the two disks in the backup script.

 

Thank You!

Yes, but don't install or mount them both at the same time.

Link to comment
3 hours ago, Shantarius said:

mount two different external USB Disks to the same mount point (not at the same time!). Background: i wanna use two USB Disks in periodicaly exchange for a backup script and it would be easier if can use only one mount point for the two disks in the backup script.

This is exactly what I do and it works fine. In fact, this is my main use for Unassigned Devices. I have been using one backup script for rotating external backups for years.

Link to comment
On 8/8/2021 at 7:17 PM, dlandon said:

Yes, but don't install or mount them both at the same time.

 Thank you both for your answers. My question is how can i (auto)mount two different USB Disks (in rotation) to the same mount point, for example

/mnt/disks/usb_backup

 

Can i use the /etc/fstab file? Is this permanently?

Link to comment
2 minutes ago, Shantarius said:

 Thank you both for your answers. My question is how can i (auto)mount two different USB Disks (in rotation) to the same mount point, for example


/mnt/disks/usb_backup

 

Can i use the /etc/fstab file? Is this permanently?

Use UD and install one at a time  Set the the mount point you want, and click the three gears icon and set the disk to auto mount.  Do the same for the other disk.  Then just plug in a disk when you want to back up.

Link to comment

I'm having trouble mounting a certain NTFS drive with UD under 6.9.2 that previously mounted.

 

Before rebooting to install 6.9.2 I also had a problem with Transmission giving me an I/O error, so I suspect this drive isn't in great shape, although running a SMART test seems OK? 

 

Now when I reboot unRAID, I get a 'current pending sector' error popping up that seems to resolve itself. I'd like to mount this drive, copy everything off it, and then decommission it. But I can't seem to mount it under UD: When I click on the orange 'mount' button, it goes grey and the spinner spins for a bit, and then it goes back to orange 'mount' like nothing happened.

 

How can I solve this problem?

Edited by Karyudo
Link to comment
5 hours ago, Karyudo said:

I'm having trouble mounting a certain NTFS drive with UD under 6.9.2 that previously mounted.

 

Before rebooting to install 6.9.2 I also had a problem with Transmission giving me an I/O error, so I suspect this drive isn't in great shape, although running a SMART test seems OK? 

 

Now when I reboot unRAID, I get a 'current pending sector' error popping up that seems to resolve itself. I'd like to mount this drive, copy everything off it, and then decommission it. But I can't seem to mount it under UD: When I click on the orange 'mount' button, it goes grey and the spinner spins for a bit, and then it goes back to orange 'mount' like nothing happened.

 

How can I solve this problem?

Post diagnostics.

Link to comment
43 minutes ago, Karyudo said:

Ah, yes. But of course....

 

It's 'sde' that's the drive I'm asking about here.

Your disk is having a problem:

Aug 14 16:36:16 Shinagawa unassigned.devices: Mounting 'Auto Mount' Devices...
Aug 14 16:36:16 Shinagawa unassigned.devices: Disk with serial 'Cruzer_Glide_3.0_4C530001290809121503', mountpoint 'SanDisk_Cruzer_Glide_3.0' is not set to auto mount.
Aug 14 16:36:16 Shinagawa unassigned.devices: Adding disk '/dev/sde1'...
Aug 14 16:36:16 Shinagawa unassigned.devices: No filesystem detected on '/dev/sde1'.
Aug 14 16:36:16 Shinagawa unassigned.devices: Partition 'WDC_WD40EFRX-68WT0N0_WD-WCC4E3KZDDCH-part1' cannot be mounted.
Aug 14 16:36:16 Shinagawa unassigned.devices: Adding disk '/dev/sde2'...
Aug 14 16:36:16 Shinagawa unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o rw,auto,async,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sde2' '/mnt/disks/DB6'
Aug 14 16:36:20 Shinagawa kernel: ata5.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x0
Aug 14 16:36:20 Shinagawa kernel: ata5.00: irq_stat 0x40000008
Aug 14 16:36:20 Shinagawa kernel: ata5.00: failed command: READ FPDMA QUEUED
Aug 14 16:36:20 Shinagawa kernel: ata5.00: cmd 60/00:90:f0:e8:63/01:00:00:00:00/40 tag 18 ncq dma 131072 in
Aug 14 16:36:20 Shinagawa kernel:         res 41/40:00:80:e9:63/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Aug 14 16:36:20 Shinagawa kernel: ata5.00: status: { DRDY ERR }
Aug 14 16:36:20 Shinagawa kernel: ata5.00: error: { UNC }
Aug 14 16:36:20 Shinagawa kernel: ata5.00: configured for UDMA/133
Aug 14 16:36:20 Shinagawa kernel: scsi_io_completion_action: 2 callbacks suppressed
Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=3s
Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 Sense Key : 0x3 [current] 
Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 ASC=0x11 ASCQ=0x4 
Aug 14 16:36:20 Shinagawa kernel: sd 6:0:0:0: [sde] tag#18 CDB: opcode=0x88 88 00 00 00 00 00 00 63 e8 f0 00 00 01 00 00 00
Aug 14 16:36:20 Shinagawa kernel: print_req_error: 2 callbacks suppressed
Aug 14 16:36:20 Shinagawa kernel: blk_update_request: I/O error, dev sde, sector 6547840 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Aug 14 16:36:20 Shinagawa kernel: ata5: EH complete
Aug 14 16:36:24 Shinagawa kernel: ata5.00: exception Emask 0x0 SAct 0x4003fc SErr 0x0 action 0x0
Aug 14 16:36:24 Shinagawa kernel: ata5.00: irq_stat 0x40000008
Aug 14 16:36:24 Shinagawa kernel: ata5.00: failed command: READ FPDMA QUEUED
Aug 14 16:36:24 Shinagawa kernel: ata5.00: cmd 60/00:b0:f0:e9:63/01:00:00:00:00/40 tag 22 ncq dma 131072 in
Aug 14 16:36:24 Shinagawa kernel:         res 41/40:00:f8:e9:63/00:00:00:00:00/40 Emask 0x409 (media error) <F>
Aug 14 16:36:24 Shinagawa kernel: ata5.00: status: { DRDY ERR }
Aug 14 16:36:24 Shinagawa kernel: ata5.00: error: { UNC }
Aug 14 16:36:24 Shinagawa kernel: ata5.00: configured for UDMA/133
Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=6s
Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 Sense Key : 0x3 [current] 
Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 ASC=0x11 ASCQ=0x4 
Aug 14 16:36:24 Shinagawa kernel: sd 6:0:0:0: [sde] tag#22 CDB: opcode=0x88 88 00 00 00 00 00 00 63 e9 f0 00 00 01 00 00 00
Aug 14 16:36:24 Shinagawa kernel: blk_update_request: I/O error, dev sde, sector 6547960 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Aug 14 16:36:24 Shinagawa kernel: ata5: EH complete

and

Aug 14 16:37:32 Shinagawa unassigned.devices: Mount of '/dev/sde2' failed: 'ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read NTFS : Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. '
Aug 14 16:37:32 Shinagawa unassigned.devices: Partition 'DB6' cannot be mounted.

 

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.