dlandon

What version of Unraid? There is a bug in older versions of Unraid where this would happen. The "Array" designation shows up because the device designation is "sdj" and not "Dev 2" after being plugged back in. That's not supposed to happen and has been fixed in 6.10.

UD sometimes can't delete partitions or the entire disk. Try this: Click on the blank mount point for the partition amd enter a mount point name. This will apply a disk label. Take the disk to a Windows computer and remove the disk partition with Windows.

Your best bet is to format it on a Windows computer.

Windows creates a small recovery partition and that's probably what you see with part1. Just leave it and ignore it.

How did you format the disk? There is a partition, but no file system. Until you get a mountable file system, your script will not work because it is only executed when the disk mounts. The disk will not mount without a valid file system.

It's already in Unraid. Has been for a while.

That happens when the disk is removed (disconnected) before it is unmounted. You'll need to reboot.

Remove the device from your server and it won't show as an unassigned device.

Looks like a disk/controller/cable issue: Apr 24 00:10:02 Tower kernel: blk_update_request: I/O error, dev sdg, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 0 Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 Sense Key : 0xb [current] Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 ASC=0x4b ASCQ=0x3 Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 CDB: opcode=0x28 28 00 91 87 ff 8f 00 00 15 00

New release. Over the last few weeks I have been tracking down a problem where the cron purge of aged files has been failing. I tracked it down to the trashsizes cron and the purge cron both running at the exact time on the hour and conflicting with each other. I've sorted it out, so it works now. This mostly showed up with large recycle bin contents. After upgrading and the cron purge removing aged files, you may see a significant decrease in the size of your Recycle Bin contents. This will happen if the cron purge of aged files has been failing. It will now catch up and purge aged files properly. It is nothing to be concerned about as it is only the aged files being purged catching up.

You have to understand that table management in UD is a total bear, because of the way Unraid is designed and the constant refresh of the UD page to keep information current. I'm not comfortable with any ideas I've come up with yet. I'm also hesitant to do changes to respond to one user's request. I want features to be applicable to all users. That being said, I'll ponder it a bit and see if I can come up with something that might work. Edit: I do see a way you can organize the passed through disks together. Give each disk an alias name like: Pass1, Pass2, Pass3, etc and all the Pass... names will be grouped together on the UD page.

Fix in the next release.

What doesn't work? Post your diagnostics and a screen shot of the settings.

Looks like I don't set up the directory to exclude properly when it's a sub-directory. Looking into it now.

That's built into Unraid. I have no control over it. Feel free to post a feature request.

Click on the 'X' to remove the banner. There is no way to prevent them from showing up.

Click on the double arrows on the UD webpage to refresh the configuration. If that doesn't work, post your diagnostics.

I would require another table to manage and there is limited space on the UI for another switch to enable/disable the passed through section. Right now I don't see enough need for this feature. It is somewhat of a corner case.

Just fixed. Wait a few minutes and try again.

The php warning doesn't make any sense because that is not the file UD is referencing in the settings page. The warning doesn't prevent UD from working and can be ignored for now. I'll do some more research and see if I can make sense of it.

Your remote server is offline or not responding to a ping: Apr 18 09:10:35 kimbie-server unassigned.devices: Remote Server 'KIMBIE-NAS01' is offline and share '//KIMBIE-NAS01/Downloads' cannot be mounted. Apr 18 09:10:35 kimbie-server unassigned.devices: Running device script: 'KIMBIE-NAS01_Downloads.sh' with action 'ERROR_MOUNT'. Apr 18 09:10:36 kimbie-server unassigned.devices: Mounting Remote Share '//KIMBIE-NAS01/Media'... Apr 18 09:10:52 kimbie-server unassigned.devices: Remote Server 'KIMBIE-NAS01' is offline and share '//KIMBIE-NAS01/Media' cannot be mounted. If the server doesn't respond to a ping, UD thinks it is offline. You can tell on the web page because the ball next to 'SMB' is gray and not green.

Post your diagnostics.

Post a screen shot of the UD page showing the SMB shares so I can see why the mount is grayed out.

Post a screen shot of the UD page and the diagnostics.

This isn't somthing I'd be looking at doing.