dlandon

I'm preclearing a disk now so I can try to reproduce the problem.

The preclear_disk.sh script is failing on v6.2 betas because the sfdisk -R is no longer supported. Preclear_disk.sh is reporting the disk as busy and will not preclear it. It looks like 'blockdev --rereadpt' is the replacement according to the sfdisk man-pages here http://man7.org/linux/man-pages/man8/sfdisk.8.html. " Since version 2.26 sfdisk no longer provides the -R or --re-read option to force the kernel to reread the partition table. Use blockdev --rereadpt instead." EDIT: There is also an issue with reads failing. I changed the following: read_entire_disk( ) { # Get the disk geometry (cylinders, heads, sectors) fgeometry=`fdisk -l $1 2>/dev/null` units=`echo "$fgeometry" | grep Units | awk '{ print $9 }'` to read_entire_disk( ) { # Get the disk geometry (cylinders, heads, sectors) fgeometry=`fdisk -l $1 2>/dev/null` units=`echo "$fgeometry" | grep Units | awk '{ print $8 }'` and the reads will work. Joe L. - Can we get an official fix and an update from you?

Do you have the 6.2 beta? The line in the preclear script that triggers the "Device X is busy" calls sfdisk -R, but the version of sfdisk in 6.2 doesn't have the -R option. Yes, I do. That must be the problem. I needed dual parity. I looked around for a bit but didn't have time to dig through the whole thread for the cause. The beta version of the plugin works fine though. Are there any major differences between the normal version and beta version scripts? I looked through them and they are obviously different scripts but didn't go through the functions to see what the actual differences were, task wise. Make a simple modification to the preclear_disk.sh script. Change the 'sfdisk -R $theDisk' to 'blockdev --rereadpt $theDisk' in two places and it should work. Do this at your own risk as I do not know enough about the preclear script to know if this is the right thing to do.

I think I have it sorted out. Update the plugin and give it another try and let me know. I may have to add some more extensive logging in order to track it down if this doesn't get it. EDIT: This should also solve the SSD drive not formatting problem.

Ok. I see it. The drive is not formatted, that's why the script button does not show.

There seem to be two issues going on with formatting that I actually think are related. One is that SSD disks cannot be formatted, and I think in the case of spinners, the common theme is that they cannot be formatted after being pre-cleared. Has anyone had a formatting problem that is neither of these cases? I can't reproduce the problem because I can't get preclear to work on my 6.2 test server and I don't have an SSD drive to test, but I have a theory that I am working on that I will implement in the next release for those having formatting problems to try.

Your disk is a 3TB disk and there seems to be an issue with formatting disks 2TB and larger. I found a 2TB in my collection and will do some testing to see if I can reproduce the issue.

sdd is not visible on the dashboard. There is a feature I implemented for a user who wanted to have a disk installed as a hot standby and didn't want UD to monitor the disk. When this feature is used, it also disables the disk attributes capability. The way it works is that if there is no script file, UD thinks the drive is to just sit there and be left alone so it does not monitor the disk temperature or check for idle status. In some cases, monitoring for disk status will spin up disks. That's why this feature was requested. I'll update the second post about best practices to make a note about this feature turning off the disk attributes. Go to the edit script and choose the default scipt (which does nothing) and you should then be able to get the disk attributes. I don't understand why the unassigned disk does not show up in the Dashboard, and I don't have any ideas on what that problem could be.

The sdd text is not active. There is a tooltip available for the two elements under identification, but neither the grey dot or the sdd text are interactive. Browse to the Dashboard and you'll see the smart report hand icon under the disk drive designation that is unassigned. You should be able to see the smart report from there. Nope, 2TB WD I'll have to dig up a 2TB disk and do some testing.

There's no reason it shouldn't work with SSD drives. I've never tested UD with SSDs. When I can get some time and an SSD drive, I'll do some testing and try to sort it out.

Apparently not.

The four squares icon is for a file system check. It will only be active when a file check can be performed. For BTRFS, the drive must be mounted. For XFS, the drive has to be unmounted. It's the nature of the file systems. I can't reproduce the format errors you are seeing. Are you trying to format an SSD?

1. You can get a smart report by clicking on the sdd text on the left side of the line for the drive. Again, hover your mouse over the active area and it will display a tool tip of what that active area does. It should display 'Disk Attributes on sdd'. If it does not, the smart report is not available. 2. I cannot reproduce the format error but I am testing on a spinner. I suspect you are trying to format an SSD drive. Is the drive an SSD?

If you hover your mouse over the active areas on the page, you will see a tool tip that can help you understand what each active area does. Click on the red X to delete the partition called /mnt/disks/ssd and then I think the 'Mount' button will turn into a 'Format' button. You have to remove all the partitions until the btrfs format goes away.

Click on the device serial number, than click on the icon that is four little squares.

Yes. Turn on destructive mode in the UD settings, delete the partition on UD, and the re-format.

I did a little research a while back on mounting a VM disk image and found some concern about corrupting the VM image if the VM is running at the same time. I played around a bit, but abandoned the idea because of this and the offset issue when mounting the image file. This is an interesting idea, but I think it might be better if it were incorporated into the VM manager by LT. I am not comfortable messing with a VM image file with UD.

Found some nfs issues with v6.2 beta. Nfs does not like to export remotely mounted file systems. Remote shares will no longer be exported with nfs on the local machine. If you have any remote shares and have nfs export enabled in the UD settings, unmount those remote shares before updating UD so the existing nfs export entries will be removed. EDIT: This applies to 6.1.9 and 6.2. 6.1.9 has the same issue, it just did not complain about it.

Post the UD log please.

Look at the UD log. A Windows ntfs drive will not mount r/w under some circumstances. The log will show the mount error before it is mounted r/o.

This plugin uses the built in recycle bin capability of samba. I don't see the functionality you are asking for ever, as it is not a trivial task and is not functionality that samba offers.

This is a to do in the future as time permits.

It would help if you would post a UD log. Click on Help and at the bottom of the help text you'll see a Download button. Click on that and post the downloaded zip file.

Thanks for the heads up. If this becomes an issue, I'll look at hosting the packages on my github.

New release. Changed the parted package link to one that may be more reliable and updated the ntfs-3g package. These packages don't change very often so I am thinking I just may update the plugin as necessary. If it continues to be a problem, I may have to host the packages at my github repository.