dlandon
-
Posts
10,381 -
Joined
-
Last visited
-
Days Won
20
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by dlandon
-
The Recycle Bin plugin uses the following command to find aged files: find /mnt/RecycleBin/User\ Shares/*/* -type f -atime +4 Run this command and see what comes up as aged files. These are the files that are deleted. I'm not seeing anything yet, but I'm still checking.
-
Yes. It's the 'Verify Disk' option. When you're on the UD Preclear page, click on the Help icon and you'll see an explanation of the script options. The disk has to be in the precleared state - preclear signature present and zeroed disk.
-
Looking into this.
-
The recycle bin files are not aged by last modified (mtime). They are aged by the atime.
-
Sounds like the User Script cron is not set up right.
-
Yes. UD sets up the shares and Unraid enables them on a polling schedule that I believe is one minute. -
You can't get Linux to unforget the disk. If it's properly unmounted, there is no problem. Don't remove it until it is unmounted. If it's not unmounted before removal, you risk data loss/corruption.
-
The disk is mounted. You are browsing it. Unmount the disk then change the mount point.
-
Your script can do an unmount when it is done, or you can unmount the disk with a User Script on a cron. Go to the UD page and click on the help icon and read about using the UD script to mount and unmount the disk. The problem with the cron is that you'd also need to confirm it got unmounted or you'll be back in the same pickle. My suggestion is to set up a User Script to do the copying and unmount the disk at the end of the script. As I read your post, it is a manual process.
-
This happens when the disk is removed without being unmounted first. When it is re-installed, Linux assigns a new sdX designation. Unraid does not see the new disk as an Unassigned DIsk and UD thinks it's a disk that fell out of the array. You'll need to reboot to clear it up.
-
The format created a partition but did not create a file system on the partition. Please post your diagnistics zip file.
-
Remove the 'min protocol = SMB2' line or change it to: [global] server min protocol = SMB2 if you really need it.
-
There is no way at this time to hide an Unassigned Device.
-
How about you post your smb-extra.conf file. You seem to have an entry that is causing this.
-
How about a screen shot of the disk in the UD page? You haven't given us enough information to help you.
-
Looks like a credentials problem.
-
Some observations: Your xml shows 6GB of memory but your video shows 4GB? That's not what your xml shows. I can't understand how you can peg your CPU usage at 100% with 3 cores and 6 CPUs doing a file copy. Did you have the xml setup you posted when you did the video? You have the vdisk on a UD device. Is it a SSD or a spinner disk? How is it formatted? Why not put that disk in a Pool and do your VMs there? As you said before, you need to concentrate on hardware issues.
-
Correct. BTRFS disks can only be scrubbed when they are mounted.
-
Linux does not see any partitions on those disks. UD can't do anythig with them.
-
You need to reboot. That disk was removed before it was unmounted and when re-installed, it was assigned a new sdX designation by Linux and Unraid did not assign it as Unassigned. UD thinks it is an array disk that disconnected.
-
You don't need to use the cli to clear the disk. Enable Destructive Mode in UD settings and use UD to clear the disk. Click on the red X next to the serial number. Show a screen shot of the disk in UD.
-
I see a few issues right away. The SCSI disk driver is not the best to use. Use the VirtIO disk driver. It looks like you are using memory balloon. Set Initial and max memory to the same value. Also post a screen shot of your Logical CPU assignments.
-
Click on the check mark.
-
Click on the '+' to show the partition, then click on the check mark to the left. Hover your mouse over the icons and the tooltip will explain what each icon does.
-
The spinner has a file system problem. Try a file system check.
