Bait Fish

The memory test passed. First boot into unRAID indicates the cache drive is missing. I'll check cables next. This SSD is only a couple/few months old. Sent from my Pixel 7 Pro using Tapatalk

I'll get a memtest going first thing tomorrow. Thanks for your guidance. Sent from my Pixel 7 Pro using Tapatalk

Now that I'm back in the land of the living, details I could not include in my haste this morning. These errors happened in the middle of the night on a system that was humming along without any other concerns previously. Shares are not showing that had been there previously. I'm sure this is a good part of the problem. Unraid Version: 6.11.5. Fix Common Problems greeted me with these issues when I checked on the server after coffee: Unable to write to cache_nvme Drive mounted read-only or completely full. Unable to write to cache_ssd Drive mounted read-only or completely full. Unable to write to Docker Image Docker Image either full or corrupted. On the Docker tab in Unraid, these errors show. Docker Containers APPLICATION VERSION NETWORK PORT MAPPINGS (APP TO HOST) VOLUME MAPPINGS (APP TO HOST) AUTOSTART UPTIME Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 898 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 712 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 967 No Docker containers installed And Unraid Settings>Docker mirrors these errors. Enable Docker: Yes One or more paths do not exist (view) Docker vDisk location: /mnt/user/system/docker/docker.img Path does not exist Default appdata storage location: /mnt/user/appdata/ Path does not exist

[Version: 6.11.5] Unraid, containers, and plugins. Seems to have had a BTFRS error on SDD1 this morning. Log attached. Gotta run to work now, so keeping this description short. Happy new year, and thanks for any help. homer-diagnostics-20230101-0456.zip

Chrome user here. Same error in regular Chrome window. No error (works!) when using Chrome incognito window. Error seems to be cached?

Following up. I did not get a good extended test log via Unraid. I instead swapped the suspect drive out and got its replacement going first. Attempts at testing it as an external drive kept failing, but without log as far as I could tell. Scanning it with Seatools on Windows ended with a failure in the long test warning that the drive is... failing. Thanks again, all of you, for your help. Unraid, and its communitity, are awesome! --------------- SeaTools for Windows v1.4.0.7 --------------- 5/24/2019 3:17:39 PM Model Number: Seagate Backup+ Hub BK Serial Number: NA8TGN5Z Firmware Revision: D781 SMART - Started 5/24/2019 3:17:39 PM SMART - Pass 5/24/2019 3:17:45 PM Short DST - Started 5/24/2019 3:17:52 PM Short DST - Pass 5/24/2019 3:18:58 PM Identify - Started 5/24/2019 3:19:03 PM Short Generic - Started 5/24/2019 3:25:19 PM Short Generic - Pass 5/24/2019 3:26:31 PM Identify - Started 5/3/2022 4:36:31 PM Short DST - Started 5/3/2022 4:36:46 PM Short DST - Pass 5/3/2022 4:37:58 PM Short Generic - Started 5/3/2022 4:38:45 PM Short Generic - Pass 5/3/2022 4:40:27 PM Long Generic - Started 5/3/2022 4:41:42 PM Long Generic - FAIL 5/4/2022 1:18:40 AM SeaTools Test Code: E896A6D4

Thanks for the tips and insights. Making progress now that spin down is disabled. So simple. . . I'll remember this next time. Your cautions spurred me to quit new disk intensive activity I started today. Now most everything is stopped, disk activity at a minimum. The new replacement 8TB drive's preclear is going to finish soon, 2% post-read left. To get the array to normal sooner, I'll play it safe by adding the new drive in first, rebuilding, then testing the failing drive later while unassigned.

Okay, I'm back. This should be my last edit. I do not think the extended test is completing. And I am not sure the downloaded SMART report will show that. This last, third time running the extended test. I sat and watched the progress. It appeared to stop on its own. I feel like the extended test should run for quite some time for an 8TB disk, not 10 minutes. In the drive capabilities section it states "Extended self-test routine recommended polling time: 937 minutes." Below is what I have observed. And I have also attached the last three SMART reports (download button). Even further below, are the last data from the Attributes table. Hope this helps diagnose. While I watch the progress of the SMART extended test (short test button greys out), the most progress observed is, self-test in progress, 10% complete. Then maybe 10 minutes later I notice it then says, Last SMART test result: No self-tests logged on this disk Refreshing the page shows a new status, Last SMART test result: Aborted by host (text colored orange) Further details from the page follow. I did not capture a downloaded report from the first extended test, four times ago. SMART self-test history: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Aborted by host 90% 47049 - # 2 Extended offline Aborted by host 90% 47048 - # 3 Extended offline Aborted by host 90% 47047 - # 4 Extended offline Aborted by host 90% 47047 - # 5 Short offline Completed without error 00% 21432 - SMART error log: No Errors Logged Attributes [before the last test. Also, highlighed in gold are #197 AND #198] # ATTRIBUTE NAME FLAG VALUE WORST THRESHOLD TYPE UPDATED FAILED RAW VALUE 1 Raw read error rate 0x000f 105 099 006 Pre-fail Always Never 7920184 3 Spin up time 0x0003 092 090 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 805 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 076 060 030 Pre-fail Always Never 91008406049 9 Power on hours 0x0032 047 047 000 Old age Always Never 47048 (5y, 4m, 13d, 8h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 293 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 000 Old age Always Never 0 188 Command timeout 0x0032 100 100 000 Old age Always Never 1 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 069 033 045 Old age Always In the past 31 (255 255 36 27 0) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 583 193 Load cycle count 0x0032 085 085 000 Old age Always Never 31233 194 Temperature celsius 0x0022 031 067 000 Old age Always Never 31 (0 19 0 0 0) 195 Hardware ECC recovered 0x001a 105 099 000 Old age Always Never 7920184 197 Current pending sector 0x0012 098 098 000 Old age Always Never 776 198 Offline uncorrectable 0x0010 098 098 000 Old age Offline Never 776 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 17295 (178 106 0) 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 94608024951 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 3333974639875 Attributes [after the last test. Again, highlighed in gold are #197 AND #198] # ATTRIBUTE NAME FLAG VALUE WORST THRESHOLD TYPE UPDATED FAILED RAW VALUE 1 Raw read error rate 0x000f 105 099 006 Pre-fail Always Never 7920184 3 Spin up time 0x0003 092 090 000 Pre-fail Always Never 0 4 Start stop count 0x0032 100 100 020 Old age Always Never 807 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 076 060 030 Pre-fail Always Never 91008485358 9 Power on hours 0x0032 047 047 000 Old age Always Never 47049 (5y, 4m, 13d, 9h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 293 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 100 100 000 Old age Always Never 0 188 Command timeout 0x0032 100 100 000 Old age Always Never 1 189 High fly writes 0x003a 100 100 000 Old age Always Never 0 190 Airflow temperature cel 0x0022 066 033 045 Old age Always In the past 34 (255 255 36 27 0) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 588 193 Load cycle count 0x0032 085 085 000 Old age Always Never 31241 194 Temperature celsius 0x0022 034 067 000 Old age Always Never 34 (0 19 0 0 0) 195 Hardware ECC recovered 0x001a 105 099 000 Old age Always Never 7920184 197 Current pending sector 0x0012 098 098 000 Old age Always Never 776 198 Offline uncorrectable 0x0010 098 098 000 Old age Offline Never 776 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 17296 (164 225 0) 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 94608024951 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 3333974639875 homer-smart-20220502-0943[1008].zip homer-smart-20220502-0943[0951].zip homer-smart-20220502-0821.zip

Good day everyone. My turn at asking for help. Diagnostics attached. My 5 year old Seagate 8TB drive (sdi) seems to have failed in the array this morning with 1024 errors. Luckily, I guess, it was holding a minimum of data. Before really reading up, I started Unbalance to move what little data it held on it to the other drives. I'm guessing this is for not, since I'm running emulated. I'll find a replacement drive ASAP and try to get that in there today. In the meantime, what's your take looking at the diags? This has been working for months, since last November. I haven't cracked the case open and do not suspect a cable or some other cause from me touching anything. It's just been. . . working, until this morning. Edit: added info, modified title homer-diagnostics-20220501-0722.zip

I use this one. But, admittedly, I have been booting with a monitor plugged in first. Sometimes my system seems to hang on boot/reboot, maybe BIOS. If I boot with a monitor, I can press keys to get past. Once Unraid it booting, I quickly swap off the monitor to the dummy plug *shrug*

The last Intel driver I installed before my success was a beta version. When it installed, it warned that it was older than what was already installed. That's the only difference I can think of that may be different from your experience. [EDIT: My current beta driver version is igfx_win_101.1121 with which I got success. Prior to that was igfx_win_101.1191. That may or may not be related. ] I never saw two monitors. But thinking back, I don't think I ever checked that detail. My process may have diverged some from alturismo's. Maybe his would work for you?

Success! Thanks for the ideas. They worked, slightly modified. I already had two other remote apps set up, Teamviewer and Parsec. I had hesitated before to remove the VNC device manually. That's why I was only disabling the QXC (VNC) display driver inside the VM in order to get Parsec to work without error. But both remote apps were stuck at 1024x768. This time I removed the VNC device manually as suggested. Upon shutting down the VM, I edited the XML and removed both graphics (VNC) and video (QXL) portions. I also deleted the gvt-g vgpu device, then started the VM. Using Teamviewer, it took a minute or two for the small black screen (640x480?) to finally bring up windows desktop and be functional. Checking Device Manager, no display drivers showed (good). I shut down the VM again, added the gvt-g vgpu device (V5_4), and started the VM. Teamviewer is now able to change resolutions, as is Parsec. And has also survived reboots. Thanks for the help, ich777 and alturismo. And BIG thanks for your contributions. I am continually amazed by how awesome Unraid is.

I am having the same issue too. Frustrating. Installed Teamviewer first to this Win10 VM, then Parsec. Parsec errors "-15000" while the Red Hat QXL display driver is active. Disabling the QXL driver allows Parsec to connect. Parsec and TeamViewer both show GPU use. But both are stuck at 1024x768 and cannot be changed while the QXL driver is disabled. Changing the Intel display driver, current and beta, do not fix. Attached are my diagnostics. I feel dumb, like I've overlooked something simple. The first time Parsec fired up after setting this VM up, it was awesome and full screen. I haven't seen it since. Tried uninstalling/reinstalling Parsec, drivers, etc. With the QXL driver enabled, the resolution is adjustable, but Parsec fails. At least Teamviewer works both ways. 1024 is disappointing though.

I am getting the same error as well.