dlandon

Type 'Yes'. Upper case 'Y'.

Disk problem.

In ud settings. Unless the btrfs disk is on a pool, there is no problem.

If you remove a disk from the array, it will show a duplicate uuid in ud. Go to ud settings and change the uuid of that disk. It should mount then.

One of your didks has some issues: Jul 3 19:35:55 Tower emhttpd: mounting /mnt/disk2 Jul 3 19:35:55 Tower emhttpd: shcmd (130): mkdir -p /mnt/disk2 Jul 3 19:35:55 Tower emhttpd: shcmd (131): mount -t xfs -o noatime,nouuid /dev/md2p1 /mnt/disk2 Jul 3 19:35:55 Tower kernel: XFS (md2p1): Mounting V5 Filesystem Jul 3 19:35:55 Tower kernel: ata5.00: exception Emask 0x10 SAct 0x7000 SErr 0x400000 action 0x6 frozen Jul 3 19:35:55 Tower kernel: ata5.00: irq_stat 0x08000000, interface fatal error Jul 3 19:35:55 Tower kernel: ata5: SError: { Handshk } Jul 3 19:35:55 Tower kernel: ata5.00: failed command: WRITE FPDMA QUEUED Jul 3 19:35:55 Tower kernel: ata5.00: cmd 61/10:60:00:a5:e1/00:00:e8:00:00/40 tag 12 ncq dma 8192 out Jul 3 19:35:55 Tower kernel: res 40/00:00:10:a5:e1/00:00:e8:00:00/40 Emask 0x10 (ATA bus error) Jul 3 19:35:55 Tower kernel: ata5.00: status: { DRDY } Jul 3 19:35:55 Tower kernel: ata5.00: failed command: WRITE FPDMA QUEUED Jul 3 19:35:55 Tower kernel: ata5.00: cmd 61/08:68:48:a5:e1/00:00:e8:00:00/40 tag 13 ncq dma 4096 out Jul 3 19:35:55 Tower kernel: res 40/00:00:10:a5:e1/00:00:e8:00:00/40 Emask 0x10 (ATA bus error) it seems to be CRC errors on disk2. Check cables. Samba is crashing: Jul 3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.638592, 0] ../../lib/util/fault.c:173(smb_panic_log) Jul 3 19:53:38 Tower smbd[20168]: =============================================================== Jul 3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.640121, 0] ../../lib/util/fault.c:174(smb_panic_log) Jul 3 19:53:38 Tower smbd[20168]: INTERNAL ERROR: Signal 7: Bus error in pid 20168 (4.17.7) Jul 3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.642863, 0] ../../lib/util/fault.c:178(smb_panic_log) Jul 3 19:53:38 Tower smbd[20168]: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting Jul 3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.648126, 0] ../../lib/util/fault.c:183(smb_panic_log) Jul 3 19:53:38 Tower smbd[20168]: =============================================================== Jul 3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.648831, 0] ../../lib/util/fault.c:184(smb_panic_log) Jul 3 19:53:38 Tower smbd[20168]: PANIC (pid 20168): Signal 7: Bus error in 4.17.7 Jul 3 19:53:38 Tower smbd[20168]: [2023/07/03 19:53:38.658840, 0] ../../lib/util/fault.c:292(log_stack_trace) Not sure where that is coming from. I don't recall seeing that issue before.

The iGPU driver has been troublesome for a long time. One thing gets fixed and another breaks. If it were me, I'd disable it and upgrade for all the other great features of 6.12. If you wait for it to be fixed, you may be waiting for quite a while.

If you have the cache dirs plugin installed, it shouldn't spin up disks. Having the background check off will probably spin up disks whenever you access the recycle bin.

You have some FCP issues: Jul 4 08:26:50 unraid root: Fix Common Problems: Warning: Jumbo Frames detected on eth0 Jul 4 08:26:50 unraid root: Fix Common Problems: Warning: Jumbo Frames detected on eth1 Jul 4 08:26:50 unraid root: Fix Common Problems: Warning: The plugin prometheus_smartctl_exporter.plg is not known to Community Applications and is possibly incompatible with your server ** Ignored Jul 4 08:26:50 unraid root: Fix Common Problems: Error: /boot/config/unraid_notify.cfg corrupted ** Ignored May not be the issue, but be sure you know what you are doing when using Jumbo frames. It is not recommended and doesn't really improve throughput. It's not worth the grief. Your docker image is not in a normal location: Jul 4 08:37:12 unraid emhttpd: shcmd (250): /usr/local/sbin/mount_image '/mnt/user/ISOs/docker.img' /var/lib/docker 40 Jul 4 08:37:12 unraid root: '/mnt/user/ISOs/docker.img' is in-use, cannot mount Jul 4 08:37:12 unraid emhttpd: shcmd (250): exit status: 1 and it is in use? Are you sure it is mapped where you want it? ISOs share is pretty unusual.

UD Prelear won't let you preclear a disk with partitions. This is done for safety. Install UD+, enable UD destructive mode, then click the red 'X' next to the disk ID and clear off the disk. It will then show up in UD Preclear.

Disk problem.

Network, cable, switch, or router issue?

Post diagnostics.

Understood. Post diagnostics so we can look into it further.

It can take a few minutes for the SMB shares to be current after changes. Give it some time, or if it doesn't go away, just click on the double arrows icon at the the upper right hand of the UD page to refresh UD.

Unrelated, but you have a disk with errors: Jul 3 18:47:01 Lucy root: Fix Common Problems Version 2023.04.26 Jul 3 18:47:02 Lucy root: Fix Common Problems: Error: disk3 (WDC_WD60EFRX-68MYMN1_WD-WX21D84R1EK9) has read errors It looks like the disk mounted r/w: Jul 2 15:25:30 Lucy unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/WD_My_Passport_0827'... Jul 2 15:25:30 Lucy unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime,space_cache=v2 '/dev/sda1' '/mnt/disks/WD_My_Passport_0827' Jul 2 15:25:30 Lucy kernel: BTRFS info (device sda1): using crc32c (crc32c-intel) checksum algorithm Jul 2 15:25:30 Lucy kernel: BTRFS info (device sda1): using free space tree Jul 2 15:25:33 Lucy unassigned.devices: Successfully mounted 'sda1' on '/mnt/disks/WD_My_Passport_0827'. Why do you think it's read only? You have errors on that disk: Jul 3 19:27:44 Lucy kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 515, rd 137, flush 0, corrupt 0, gen 0 Jul 3 19:27:44 Lucy kernel: I/O error, dev sda, sector 2248416 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jul 3 19:27:44 Lucy kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 515, rd 138, flush 0, corrupt 0, gen 0 Jul 3 19:27:51 Lucy kernel: I/O error, dev sda, sector 94112 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 Jul 3 19:27:51 Lucy kernel: BTRFS error (device sda1: state EA): bdev /dev/sda1 errs: wr 515, rd 139, flush 0, corrupt 0, gen 0 Jul 3 19:27:51 Lucy kernel: I/O error, dev sda, sector 2191264 op 0x0:(READ) flags 0x1000 phys_seg 4 prio class 2 @JorgeB can probably help with the disk issues.

The orb ball is only based on being able to ping the remote share server. The 'Mount' button and the size, used, and free indicators (from df) will show mount status.

Your issue is not a UD Preclear issue. Please post your issue with diagnostics here:

I need the log when Unraid shuts down and reboots. Unfortunately, it is lost when rebooting. You have the Tips and Tweaks plugin installed. There is a log archive feature that saves a copy of the syslog on the flash when Unraid is shutting down. Set the "Enable syslog Archiving?" to 'Yes' and then start a preclear and shut down Unraid. When you reboot, the syslog will be archived to '/flash/logs/'.

Unraid 6.12 introduced the concept of listening interfaces. Read the release notes here https://docs.unraid.net/unraid-os/release-notes/6.12.0/ and see if you need to add your interface so UD can mount remote shares. For example, if you use a Zerotail or Tailscale VPN.

Posting diagnostics can help with diagnosing your issue.

I just tried a reboot to see if there was an issue with pausing and resuming a preclear and it worked for me. In order to catch this so I can troubleshoot this, do this: Set up the syslog server to write the log to disk. Reboot while running a preclear. Post the syslog.

Which computer is the client and which is the server?

Here is what I see: Jun 23 04:40:02 Tower root: Fix Common Problems Version 2023.04.26 Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Unraid OS not up to date Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Docker Application thespaghettidetective_redis_1 has an update available for it Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Share Secure-storage is set for both included (disk4) and excluded (disk1,disk2,disk3) disks Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Share VMs is set for both included (disk3) and excluded (disk1,disk2) disks Jun 23 04:40:03 Tower root: Fix Common Problems: Warning: Deprecated plugin ca.backup2.plg Jun 23 04:40:05 Tower root: Fix Common Problems: Warning: Docker application Dolphin has moderator comments listed Jun 23 04:40:05 Tower root: Fix Common Problems: Warning: Docker application PlexMediaServer has moderator comments listed Jun 23 04:40:05 Tower root: Fix Common Problems: Warning: Docker application steamcache-DNS has moderator comments listed ** Ignored Jun 23 04:40:06 Tower root: Fix Common Problems: Warning: NerdPack.plg Not Compatible with Unraid version 6.11.5 Jun 23 04:40:07 Tower root: minecraft-James-revelation: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:07 Tower root: Minecraft-polytech-direwolf20-1.19: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:08 Tower root: urBackup-Server: Could not download icon http://192.168.1.90:55414/images/urbackup.png Jun 23 04:40:10 Tower root: minecraft-James-revelation: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:11 Tower root: Minecraft-polytech-direwolf20-1.19: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:11 Tower root: urBackup-Server: Could not download icon http://192.168.1.90:55414/images/urbackup.png Jun 23 04:40:11 Tower root: minecraft-James-revelation: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:11 Tower root: Minecraft-polytech-direwolf20-1.19: Could not download icon https://vignette.wikia.nocookie.net/minecraft/images/7/7b/Grass_block.png Jun 23 04:40:12 Tower root: urBackup-Server: Could not download icon http://192.168.1.90:55414/images/urbackup.png Jun 23 04:40:12 Tower root: Fix Common Problems: Warning: Write Cache is disabled on disk5 Jun 23 04:40:13 Tower root: Fix Common Problems: Other Warning: Unassigned Devices Plus not installed Jun 23 04:40:14 Tower root: Fix Common Problems: Warning: Docker Update Patch not installed Jun 23 04:47:31 Tower apcupsd[7934]: Communications with UPS lost. Here are my suggestions: Go through all the FCP issues and get them sorted out. Be sure to remove the NerdPack plugin as it is not compatible with 6.11. You have some disk mapping issues. Find out why your UPS keeps losing communications. Run Unraid without any Docker containers running and see if the log messages and filling of the log stops.

UD is used by many users like myself to back up files. I plug in a USB disk and a device script runs doing the work I want done for that device. The Historical devices are devices that were in UD but have been removed as you noted. When I plug in a USB disk, the disk mounts and runs the script as defined in the Historical devices. This makes the backup a plug and play operation. Without the Historical device settings, UD does not know what to do when a disk in plugged in.

You have a network issue.