25 minutes ago, steve1977 said:

Yes. Plus another 4 that are at the bottom (didn't fit the screenshot). The issue is with these disks. DOn't think they should be "black tick", but shouldn't show up or also be deletable.

Looks like you have a lot of disks in that situation.  Aren't you interested in removing all of those?  Looks pretty messy.

 

I can't reproduce your issue  The only way the disk will show as being able to re-attach (delete 'X' disabled) is if you detached the disk in UD.

 

After your next reboot, those disks will show an enabled delete icon.

I never disabled any of them. At least I didn't do manually. Maybe Unraid did? Also, they still have the "black cross" after shutting downa and rebooting Unraid.

15 minutes ago, steve1977 said:

I never disabled any of them. At least I didn't do manually. Maybe Unraid did? Also, they still have the "black cross" after shutting downa and rebooting Unraid.

If you click on the three gears of one of those Historical devices, does the 'Attach' button show?

No, cannot attach. They're part of the array and active. That's also why they have the "green light" you can see at the screenshot above.

 

I think it may be because I did "new config". Maybe some order or so changed?

1 minute ago, steve1977 said:

No, cannot attach. They're part of the array and active. That's also why they have the "green light" you can see at the screenshot above.

 

I think it may be because I did "new config". Maybe some order or so changed?

I didn't ask you to attach a disk, I only asked if you click on the three gears if the 'Attach' button shows up.  I'm looking to see if the detection of a disk in this situation has a problem, or if UD needs to change how it detects this situation.

 

Booting the server should clear the status of a deteched disk.

 

So let's try once more.  If you click on the three gears does the 'Attach' button show up?

Nope, it does not show up. And when I restart the server, it still shows under historic with the black cross.

The issue is with the disabling of the delete 'X'.  I'll have a look.

Would anyone here be able to help me figure out why I can't seem to successfully format and mount this disk?

Feb 11 22:36:31 archivearea unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'.
Feb 11 22:45:54 archivearea unassigned.devices: Format device '/dev/nvme0n1'.
Feb 11 22:45:54 archivearea unassigned.devices: Device '/dev/nvme0n1' block size: 976773168.
Feb 11 22:45:54 archivearea unassigned.devices: Clearing partition table of disk '/dev/nvme0n1'.
Feb 11 22:45:56 archivearea unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Feb 11 22:45:56 archivearea unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Feb 11 22:45:56 archivearea unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme0n1'.
Feb 11 22:45:56 archivearea kernel: nvme0n1:
Feb 11 22:45:56 archivearea kernel: nvme0n1: p1
Feb 11 22:45:58 archivearea unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Feb 11 22:45:58 archivearea kernel: nvme0n1: p1
Feb 11 22:45:58 archivearea unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Feb 11 22:45:58 archivearea unassigned.devices: Formatting disk '/dev/nvme0n1' with 'xfs' filesystem.
Feb 11 22:45:58 archivearea unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/nvme0n1p1' 2>&1
Feb 11 22:46:14 archivearea 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.
Feb 11 22:46:17 archivearea unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Feb 11 22:46:17 archivearea kernel: nvme0n1: p1
Feb 11 22:46:17 archivearea unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Feb 11 22:46:20 archivearea kernel: nvme0n1: p1
Feb 11 22:46:30 archivearea unassigned.devices: Adding partition 'nvme0n1p1'...
Feb 11 22:46:30 archivearea unassigned.devices: Mounting partition 'nvme0n1p1' at mountpoint '/mnt/disks/2222E636C330'...
Feb 11 22:46:30 archivearea unassigned.devices: Mount drive command: /sbin/mount -t 'vfat' -o rw,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/nvme0n1p1' '/mnt/disks/2222E636C330'
Feb 11 22:46:30 archivearea kernel: FAT-fs (nvme0n1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Feb 11 22:46:30 archivearea kernel: FAT-fs (nvme0n1p1): bogus number of FAT structure
Feb 11 22:46:30 archivearea kernel: FAT-fs (nvme0n1p1): Can't find a valid FAT filesystem
Feb 11 22:46:33 archivearea unassigned.devices: Mount of 'nvme0n1p1' failed: 'mount: /mnt/disks/2222E636C330: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '

 

8 hours ago, syphant said:

Would anyone here be able to help me figure out why I can't seem to successfully format and mount this disk?

Feb 11 22:36:31 archivearea unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'.
Feb 11 22:45:54 archivearea unassigned.devices: Format device '/dev/nvme0n1'.
Feb 11 22:45:54 archivearea unassigned.devices: Device '/dev/nvme0n1' block size: 976773168.
Feb 11 22:45:54 archivearea unassigned.devices: Clearing partition table of disk '/dev/nvme0n1'.
Feb 11 22:45:56 archivearea unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Feb 11 22:45:56 archivearea unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Feb 11 22:45:56 archivearea unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme0n1'.
Feb 11 22:45:56 archivearea kernel: nvme0n1:
Feb 11 22:45:56 archivearea kernel: nvme0n1: p1
Feb 11 22:45:58 archivearea unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Feb 11 22:45:58 archivearea kernel: nvme0n1: p1
Feb 11 22:45:58 archivearea unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Feb 11 22:45:58 archivearea unassigned.devices: Formatting disk '/dev/nvme0n1' with 'xfs' filesystem.
Feb 11 22:45:58 archivearea unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/nvme0n1p1' 2>&1
Feb 11 22:46:14 archivearea 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.
Feb 11 22:46:17 archivearea unassigned.devices: Reloading disk '/dev/nvme0n1' partition table.
Feb 11 22:46:17 archivearea kernel: nvme0n1: p1
Feb 11 22:46:17 archivearea unassigned.devices: Reload partition table result: /dev/nvme0n1:  re-reading partition table
Feb 11 22:46:20 archivearea kernel: nvme0n1: p1
Feb 11 22:46:30 archivearea unassigned.devices: Adding partition 'nvme0n1p1'...
Feb 11 22:46:30 archivearea unassigned.devices: Mounting partition 'nvme0n1p1' at mountpoint '/mnt/disks/2222E636C330'...
Feb 11 22:46:30 archivearea unassigned.devices: Mount drive command: /sbin/mount -t 'vfat' -o rw,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/nvme0n1p1' '/mnt/disks/2222E636C330'
Feb 11 22:46:30 archivearea kernel: FAT-fs (nvme0n1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Feb 11 22:46:30 archivearea kernel: FAT-fs (nvme0n1p1): bogus number of FAT structure
Feb 11 22:46:30 archivearea kernel: FAT-fs (nvme0n1p1): Can't find a valid FAT filesystem
Feb 11 22:46:33 archivearea unassigned.devices: Mount of 'nvme0n1p1' failed: 'mount: /mnt/disks/2222E636C330: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call. '

 

Remove and reseat the nvme drive.

From today I'm not able to mount my SMB share on synology...

 

I had a unclean shutdown this morning, I'm not sure if it is related to that? If yes, why isn't it working?!

 

unraid 6.11.3

 

Feb 12 16:17:28 unraid unassigned.devices: Mounting Remote Share '//DS118/Datenbackup'...
Feb 12 16:17:28 unraid unassigned.devices: Mount SMB share '//DS118/Datenbackup' using SMB default protocol.
Feb 12 16:17:28 unraid unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup'
Feb 12 16:17:38 unraid unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup' 2>&1) took longer than 10s!
Feb 12 16:17:38 unraid unassigned.devices: SMB default protocol mount failed: 'command timed out'.
Feb 12 16:17:38 unraid unassigned.devices: Mount SMB share '//DS118/Datenbackup' using SMB 3.1.1 protocol.
Feb 12 16:17:38 unraid unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup'
Feb 12 16:17:39 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!

 

I deleted the mount and recreated it, even with a new smb user... no success

 

Any thoughts?

Edited February 12, 20233 yr by enJOyIT

35 minutes ago, enJOyIT said:

From today I'm not able to mount my SMB share on synology...

 

I had a unclean shutdown this morning, I'm not sure if it is related to that? If yes, why isn't it working?!

 

unraid 6.11.3

 

Feb 12 16:17:28 unraid unassigned.devices: Mounting Remote Share '//DS118/Datenbackup'...
Feb 12 16:17:28 unraid unassigned.devices: Mount SMB share '//DS118/Datenbackup' using SMB default protocol.
Feb 12 16:17:28 unraid unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup'
Feb 12 16:17:38 unraid unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup' 2>&1) took longer than 10s!
Feb 12 16:17:38 unraid unassigned.devices: SMB default protocol mount failed: 'command timed out'.
Feb 12 16:17:38 unraid unassigned.devices: Mount SMB share '//DS118/Datenbackup' using SMB 3.1.1 protocol.
Feb 12 16:17:38 unraid unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup'
Feb 12 16:17:39 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!

 

I deleted the mount and recreated it, even with a new smb user... no success

 

Any thoughts?

The commands on the remote server are timing out.  This implies a network or remote share issue.

 

Post diagnostics.

The same share is working on my laptop without issues.

 

Here is the diagnostic:

 

 

unraid-diagnostics-20230212-1708.zip

 

I see other messages:

 

Feb 12 17:15:25 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s!
Feb 12 17:15:30 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!
Feb 12 17:15:40 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s!
Feb 12 17:15:44 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!
Feb 12 17:15:54 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s!
Feb 12 17:16:00 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!
Feb 12 17:16:10 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s!
Feb 12 17:16:15 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!
Feb 12 17:16:25 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s!
Feb 12 17:16:30 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!

 

Edited February 12, 20233 yr by enJOyIT

18 minutes ago, enJOyIT said:

The same share is working on my laptop without issues.

 

Here is the diagnostic:

 

 

unraid-diagnostics-20230212-1708.zip 191.62 kB · 0 downloads

Do the following:

• Stop the array.
• Confirm and force an update to your SMB Settings.  You can force an update by making a change and reverting it back then apply.
• Start the array.

On 2/12/2023 at 5:30 PM, dlandon said:

Do the following:

• Stop the array.
• Confirm and force an update to your SMB Settings.  You can force an update by making a change and reverting it back then apply.
• Start the array.

 

sadly this didn't work.

3 minutes ago, enJOyIT said:

 

sadly this didn't work.

Your unclean shutdown probably caused a corruption on the flash drive if everything was working before that.  I was hoping it was as simple as redoing the SMB settings.  Try this:

• Take your flash to a PC and perform a file system check.  Fix any errors that show up.
• Restore the flash drive contents from a backup.

Does it work if i'm backing my settings now and restore it from that? My last backup is from 6th january... 

 

Can I pull the usb stick out while it's running?

Edited February 14, 20233 yr by enJOyIT

Just now, enJOyIT said:

Does it work if i'm backing my settings now and restore it from that?

Not necessarily if there is a file corruption.  What changed in your configuration since January 6th?

I installled some docker apps.

 

Do you can recommend a software for checking the usb filesystem? And do I have to shutdown the server or can it still run from RAM without the stick?

Edited February 14, 20233 yr by enJOyIT

37 minutes ago, enJOyIT said:

I installled some docker apps.

 

Do you can recommend a software for checking the usb filesystem? And do I have to shutdown the server or can it still run from RAM without the stick?

You can re-install the Docker apps.  You have to shut down the server.  Don't take the USB out while the server is running!

 

A Windows PC has a file system check you can run once the USB is installed in the PC.  Not sure what tools a Mac will have.

Ok, will try that tomorrow!

 

Will the docker configs be lost?

No. As long as your appdata is intact. You will have to reconfigure the docker xml since it is stored on the flash.

 

 

 

 

 

 

 

 

 

 

 

 

Would it be possible to have this format blank drives? I.E a drive that hasn't been initialised.

 

For example I have a new drive that I want to use outside of unraid.

I would like to format it as exfat. so it is readable on mac & windows (& linux).

Really I want to use unraid machine to copy from one unassisned drive (drone SSD) to another unassigned drive (client harddrive) rather than tie my laptop up for hours (they send a slow drive).

 

At the moment the drive doesn't show up in unraid unless I add it as part of a pool or the array and format it into btrfs or xfs.

Could also be useful for USB sticks etc.

At the moment I use my laptop to format the new drive then plug back into unraid & mount with unassigned.

 

Thanks

Edited February 14, 20233 yr by dopeytree

1 hour ago, dopeytree said:

Would it be possible to have this format blank drives? I.E a drive that hasn't been initialised.

 

For example I have a new drive that I want to use outside of unraid.

I would like to format it as exfat. so it is readable on mac & windows (& linux).

Really I want to use unraid machine to copy from one unassisned drive (drone SSD) to another unassigned drive (client harddrive) rather than tie my laptop up for hours (they send a slow drive).

 

At the moment the drive doesn't show up in unraid unless I add it as part of a pool or the array and format it into btrfs or xfs.

Could also be useful for USB sticks etc.

At the moment I use my laptop to format the new drive then plug back into unraid & mount with unassigned.

 

Thanks

How are you connecting the drive?  If Linux does not recognize the drive, UD won't see it.  I'd ask you to post diagnostics, but there is no value in that unless the disk is not being recognized when you run diagnostics.

Hello,

 

is it possible to make this plugin accessible for Screen Reader users? For Example it is not possible to set the Buttons or Checkboxes PASSED THROUGH, DISABLE MOUNT BUTTON, READ ONLY, AUTOMOUNT, SHARE, SHOW PARTITIONS with the Keyboard and a Screen Reader like NVDA or JAWS for Windows. The Links in The Main Screen of the Plugin in the Dash are not readable too.

 

Thanks and best regards.