CyberMew

Yes seems like it, thanks a lot! I guess after copy and rebuild operation there is a startup bug and it didn't try to attempt to start the services.. (I hope) Disk1 scan was also ok: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 64443 -

I googled and found a similar issue I restarted and that seemed to do the trick! Attached new diags just in case.tower-diagnostics-20230605-2330.zip I am also running the extended SMART test now. Thanks a lot! Thanks for the suggestions! Yes I should definitely get around to FCP.. The command "cat /etc/crond.d/root" is not working but I think you meant this: ~# cat /etc/cron.d/root # Generated docker monitoring schedule: 10 0 * * 1 /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 40 4 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 0 0 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null #Refresh plex tv shows at 3pm everyday 0 15 36 20 * * * logger -tscriptRefreshPlexLibrary5[$$] "Refreshing Plex library 5" && curl "http://127.0.0.1:32400/library/sections/5/refresh?deep=0&X-Plex-Token=xxx" &> /dev/null <- any idea how to remove this? # Generated array status check schedule: 20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null #Running subliminal At minute 0 past every 4th hour. cat /etc/cron.d/root 0 */4 * * * logger -tscriptSubliminal[$$] "Subliminal checking for subs" && /mnt/user/subliminal2/subliminal/checklast2dayspath.sh > /dev/null <- any idea how to remove this as well? # Generated cron settings for docker autoupdates 0 0 * * 0 /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1 # Generated cron settings for plugin autoupdates 0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # CRON for CA background scanning of applications 34 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 # Generated ssd trim schedule: 0 3 * * * /sbin/fstrim -a -v | logger &> /dev/null Not sure what is # 015..

Have attached as requested (it was after data rebuild). Data rebuild was completed 2 hours ago and I still don’t see Docker and VM up.. so something must be wrong.. thanks a lot for helping to look into it! tower-diagnostics-20230605-1612.zip

I am confused about your response because I didn't turn it off. This is my settings: So any idea why it is stopped? Is it because of the parityswap/data rebuild going on?

Thanks for the info, but is it supposed to be temporary turned off? I didn't see this in the guide, so am wondering if this is normal or not. Worried if it isn't..

Also, just to check, is it normal that Docker and VM is turned off when doing this parity swap and data rebuilding? Docker: Docker Service failed to start. VMs: Libvirt Service failed to start. Anything we should know about other services being turned off as well?

Find common problems plugin says this is no longer updated, and I always have lag issues loading the page anyway. I have Version: 2018.02.11, and I just removed the plg. Is there any leftover files I need to uninstall?

Thanks! I switch it and it seems to be working fine as expected. Copied without errors over the past day and rebuilding disk5 now. Edit: is the add on card problematic? Should I change it? Any brands or model to recommend?

I have attached as requested, hope you can advise on next steps.. What happened was Disk5 errored out, had to preclear new drive so unassigned Disk5 and started array to run Preclear on new disk. Now that its done, array has been stopped. tower-diagnostics-20230602-1746.zip

I got around to doing this today, and for some reason Parity 1 slot is not showing the new drive, but Parity 2 slot is able to show/select it. I want to use the bigger HDD for Parity 1 instead. Is this not possible? Current: Edit: after moving the drives around the new drive is somehow appearing under Parity 1 to be selectable. Not sure if this was a bug in 6.9.2. Edit2: After selecting the new drive in Parity 1 slot, it does not show up at all! Is the wiki instructions outdated?

Thanks for confirming! Hopefully my logs were helpful in helping you figure it out..

I tried to preclear using the binhex docker as suggested, and it precleared successfully. So maybe there is some bug with the plugin..? Should I stop preclear and Verify Disk using this plugin, or is the drive good to go now?

My disk 5 is unassigned right now with a red X, will it know to emulate disk 5 or remove it and update my parity (losing data)? Also have uploaded the requested logs here: TOWER-unassigned.devices.preclear-20230527-0806.zip tower-diagnostics-20230527-0048.zip

My array is currently stopped due to disabled drive and this new drive is supposed to replace that using the drive swap procedure, so unfortunately I can’t start and install the docker and run it.. is there another way to do it? I’ll post the unraid diagnostics once I am able to. How do I get the full UD Preclear log?

Failing again. Feels like something is not right. Doesn’t seem like an issue with the disk? Any idea what’s the issue and how to resolve it? #################################################################################################### # Unraid Server Preclear of disk xxx # # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 5 - Pre-read verification: [23:22:47 @ 213 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [23:23:33 @ 213 MB/s] SUCCESS # # Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying Unraid's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # # # # # # # #################################################################################################### # Cycle elapsed time: 47:11:04 | Total elapsed time: 47:11:05 # #################################################################################################### #################################################################################################### # S.M.A.R.T. Status (device type: default) # # # # ATTRIBUTE INITIAL STATUS # # Reallocated_Sector_Ct 0 - # # Power_On_Hours 94 - # # Temperature_Celsius 36 - # # Reallocated_Event_Count 0 - # # Current_Pending_Sector 0 - # # Offline_Uncorrectable 0 - # # UDMA_CRC_Error_Count 0 - # # # # # #################################################################################################### # # #################################################################################################### … May 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 408604901376 bytes (409 GB, 381 GiB) copied, 1449.55 s, 282 MB/sMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 196567+0 records inMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 196566+0 records outMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 412228780032 bytes (412 GB, 384 GiB) copied, 1462.4 s, 282 MB/sMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 198295+0 records inMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 198294+0 records outMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: dd output: 415852658688 bytes (416 GB, 387 GiB) copied, 1475.27 s, 282 MB/sMay 26 22:33:20 preclear_disk_xxx_2299: Post-Read: post-read verification failed!May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Error:May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.:May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUSMay 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Reallocated_Sector_Ct 0 0 -May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Power_On_Hours 94 141 Up 47May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Temperature_Celsius 36 51 Up 15May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Reallocated_Event_Count 0 0 -May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Current_Pending_Sector 0 0 -May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: Offline_Uncorrectable 0 0 -May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: UDMA_CRC_Error_Count 0 0 -May 26 22:33:25 preclear_disk_xxx_2299: S.M.A.R.T.: May 26 22:33:25 preclear_disk_xxx_2299: error encountered, exiting ...

Thanks, I verified disk and it says disk not zeroed out. Not sure how it even cleared Stage 4 if so.. I am now clearing the disk again starting with pre-read

I cleared my drive yesterday and I got this: # Cycle 1 of 1, partition start on sector 64. # # # # Step 1 of 5 - Pre-read verification: [23:22:44 @ 213 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [23:23:36 @ 213 MB/s] SUCCESS # # Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying Unraid's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: FAIL # Not sure if it happened while I knocked into the server case (doubt so though). How can I run Step 5 again without going through Step 1-4? And if Step 5 fails again, should I run the whole preclear again? Or will it be grounds for an RMA (don't know what to write for a return)? FWIW I start in safe mode so there are no other activities going on to interfere (drives are not mounted). Thanks for any advice in advance..

Ah I see! Got it now. Thanks a lot for clearing my doubts! Hope everything goes well 🤞

Because earlier you mentioned the array will be started, hence I came to that conclusion. Oh so you mean as I start the array, 4 and 5 will happen before the array is actually started and the drives starts to be in use?

Thanks but I still have a question.. that would mean the array is started, but Slot5 is invalid data and Parity2 is also empty. Wouldn’t this cause an issue though?

Yes that is what I meant, thanks for helping to clear that up! May I check, do I do the assignment both at once? My current state is Parity2 (10TB) still assigned, Disk5 empty (previously 6TB failed). 18TB (unassigned) being precleared (and assume it will be cleared for use). Meaning do I now, (1) Unassign Parity2 slot (10TB drive), (2) Assign that 10TB parity2 drive into Disk5 slot, (3) Assign 18TB into Parity2 slot, (4) Copy Disk5 (parity2 contents) into Parity2 (empty 18TB), (5) start array to rebuilt Disk5 (overriding its parity2 contents)? Really appreciate some confirmation as I do not want to screw this up.. thank you!

I currently have a failed drive (6TB) in my Disk5 slot (red ball icon). My 2 parity drives are 10TB. I shutdown my server, and I have removed the failed drive (6TB) and put in a new 18TB drive. I am preclearing my 18TB drive now. Array is currently stopped. Disk5 slot is now unassigned. I hope so far this is correct move by me.. please do correct me if I am wrong. Going by the swap procedure here https://wiki.unraid.net/The_parity_swap_procedure (which I didn't quite grasp, would be nice to have photos..), can I confirm that once the preclear is done, I need unassigned the Parity2 (or Parity1, but I am going to choose Parity2) drive (10TB), reassigned that parity 10TB drive to my Disk5 slot, and then assign the precleared 18TB drive into my Parity2 slot? If that is correct, I am not sure how that will 'restore' my previous Disk5 data and keep the parity.. Maybe I haven't reached that step yet, but can I assume, when I do those 2 reassignment actions, 2 things will happen: 1. Copy Disk5 data (which is my Parity2 drive data) to the new 18TB drive (in my Parity2 slot). While array is not started. 2. Disk5 remains a drive with parity data. Start array to rebuild Disk5 actual drive data based on the 2 parity drives (10TB and 18TB). Hope someone can confirm or correct me if I am wrong.. thank you!!

Sorry to ask a noob question but how do I install this plugin while the array is stopped? I can't start it until I preclear my drive and while trying to install this via Apps it says: Requirements not met The requirements for this upgrade have not been met on your system I am using unraidOS 6.9.2. Edit: just noticed the requirements and it says Unassigned Devices plugin required. Installed and all good now.

I am noticing the container size is growing. It grew by 2gb over a couple months. Settings is linked to app data folder on cache drive already. Any idea what is going on? edit: a restart fixed it. I wonder if we need to restart it manually often.

Sorry to necro this thread but is there an option (or a docker image) for this now? My desktop is always sleeping but my unraid server is always online, so it would be nice to wake up my desktop so I can remote in when I am outside, either WOL via an web interface accessible over the internet or vpn in. edit: found and used this worked fine!