dlandon

How did you create that smb share? The source is very strange - '//192.168.1.11/></a>'. It contains html code.

Normally sda is the Unraid flash drive. In your case the flash is sdb. Is there something on your flash drive causing this? Take your flash to a PC and see if there is something that might be the problem.

Ok, looking at the message again I see where the UD fsck had a problem. I assume that the scrub didn't show any results? Back out of any browsers you had been using to access the server and then start the browser over and try again.

They are formatted ext4, but at the disk level. Udev does not show any partition info for the disks, so UD doesn't think they are formatted. If you look at the UD webpage, you'll see that UD doesn't see a partition, because udev does not present info on a partition. I'm not that familiar with ext4 file systems, but I'll do some research. For now assume UD can't handle this. If you can, re-install them in the old Ubuntu system and mount them as remote shares and transfer your data that way.

If they were formatted purely as xfs, then Linux (hence UD) would be able to recognize the file system. Were they in a raid or other configuration that might be a unique partition layout? Post the /var/state/unassigned.devices/unassigned.devices.ini file and I can see the disk details. This is the udev info for each disk. Let me know which /dev/sdX disk designations are the issue.

The limited screen shot you posted indicates that the disk format is not recognized by Linux.

You might try reassigning it back to the array, but I'd probably do a UD file system check first. You'd have to mount it then click on the check icon. It looks mountable in UD if you'd just rather mount it and unload it. I'd suggest setting it to read only to stop any write activity. Click on the three gears and set 'Read Only' On.

I have issued an update to the plugin. The application of tips and tweaks values will occur now later in the start up process. What I think might be happening is tips and tweaks applies the settings before Unraid is finished initializing. Update to the latest release and see if the settings get applied correctly after a reboot.

I've fixed the clear disk not showing after a preclear: I added the clear disk icon because parted has issues at times removing partitions. In your case, parted said the partition did not exist. Obviously there is a partition. The clear disk does a 'wipefs' that removes any and all partitions from a disk. Users have had to go to the command line to clear a disk, and there is too much chance of making a mistake.

Your flash drive is disconnecting and then reconnecting. When it reconnects, Linux assigns a new device designation thinking it is a new hot plugged drive. The server then loses access to sda. Do this: Shut down your system. Remove the flash drive and take it to a computer and try to repair the file system. Put the flash back into the server in a different USB slot. Try to use a USB2 slot.

I don't think that is the problem. I think there is a bug I didn't catch. I'm doing a preclear and will test this.

It looks like this: There may be an issue with preclear being installed. I'll have a look.

UD tried to delete the partition, but it doesn't exist. I added a red 'X' next to the serial number in release 12.13.2021 that does a wipefs on the whole disk and overcomes these kinds of issues. It's pretty brute force and takes all the partition information off the disk. Give that a try.

Post diagnostics.

Those disks are dropping out of the array and Linux then assigns new device numbers thinking they are new hot plugged disks. UD picks them up because they are not assigned to the array. I think you are wasting you time trying to rebuild the disk. You need to figure out why the disks are dropping off-line. How are the disks connected? What is common between those three disks? Post your diagnostics and one of the drive gurus like @JorgeB can lend a hand.

@JorgeB It appears that UD has a bug when presented with scsi disks. The original coding was set to handle scsi disks, but it is apparently not working. Is there a way I can add a scsi disk to my server without having to use an LSI controller and an 18TB disk?

Yes. UD expects ata devices. These disks are marked as scsi. Remove the dynamix scsi devices plugin. I think others have had this issue.

Yea, I get that, but I'm trying to gather information to see if I can find the problem. Try this: - Click on the double arrows in the upper right of the UD page. This will trigger udev to rediscover the disks. - If that doesn't clear up the problem, then post the contents of the file /var/state/unassigned.devices/unassigned.devices.ini.

Which disks? Can you post a screen shot of UD?

Unraid manages the array, pool devices, VMs and Docker containers. All will start and stop with the array. In my mind all these things are part of the array, though not necessarily the actual array. This came from people creating pools manually and then having UD manage them before Unraid had 'Pool Devices' capability. UD didn't do a great job with pools and I just cleaned it up a bit so the GUI could handle it better.

I don't know much about the Unraid UI, so I can't offer any help. It's possible it was a one time fluke. Keep an eye on it and see if the log fills with those messages again.

UD will not be creating pools. The only thing I wanted to do here is for UD to handle pooled disks a little better. Pooled disks are better done in 'Pool Devices' in Unraid.

Your log is flooded with: Dec 12 11:59:56 Kyber nginx: 2021/12/12 11:59:56 [alert] 17877#17877: worker process 15211 exited on signal 6 Dec 12 11:59:57 Kyber nginx: 2021/12/12 11:59:57 [alert] 17877#17877: worker process 15212 exited on signal 6 Dec 12 11:59:57 Kyber nginx: 2021/12/12 11:59:57 [alert] 17877#17877: worker process 15218 exited on signal 6 This could cause a problem with the GUI. I don't understand this well enough to help, but others that are more knowledgeable about nginx might be able to help. This is why rebooting worked - it cleared up the problem, but I suspect it will come back.

I am following up with you on this as requested by Unraid support. 512k is a bit of a strange number. The default setting for 'fs.inotify.max_user_watches' is actually 524,288. I suspect something is resetting the value after Tips and Tweaks sets it. So let's do this: - Post your diagnostics as they are right now. - Reboot your server in safe mode. - Check the value of 'fs.inotify.max_user_watches'.

I put together a simple test of a UD Pool and made changes to the UI to handle disk pools a little better. It also fixes the issue with checking for duplicate share names on pool disks without the setting to override the check. Mounting two different disks that are not in a pool to the same mount point can cause loss of data and the duplicate check offers some protection against that. I wanted to do this so UD at least handled disk pools better. This allows those that have legacy pools to mount them with UD and work with them. You should also be able to unassign a pool from the array and work with it in UD. The array pool offers a lot of advantages over UD and you should really use that instead of UD for pools.