Paul_G

@Jay3ird nice. That's where my one fell over. Lol. Thanks.

@Jay3ird awesome. What happens when you click on the Generate backup button?

I updated to Unraid V6.12.6 earlier today (still on connect plugin 2023.09.08.0637 as still the latest version). I no longer get the same errors that i screenshotted in my previous post. It looked to be resolved. The server seemed to be connected in the management access options so i went to the Unraid connect dashboard and this showed that a flash backup was already available. this seemed a bit odd as I'd only just booted the server in the new 6.12.6 update and the timestamp that was showing in the dashboard for the backup was more or less the same as the time it booted up. I tried to grab a copy of the new online flash backup to validate that it was working, but i kept getting an error. I thought I would try logging out and back into Unraid Connect and now I can't log back in, even after a server reboot!! Error: {"message":"Request failed with status code 403","data":"Oh noes! something doesn't seem right here"}

I'm fairly new here. Does anyone know if someone from Lime Technology is likely to look into it, or give an update here? It's obviously an issue. Does someone need to file a bug somewhere?

Same. Using latest version of both Unraid and the plugin Unraid V6.12.4 Connect plugin V2023.09.08.0637 It's a fairly new server, so I didn't have remote access allowed until today. I've enabled that (Dynamic - UPnP) and it connects ok: In the Flash backup settings on the management access settings page, Flash backup is activated: Not sure what's going on. I can't get any further than this. just keep getting "Failed to sync flash backup", and on the Unraid Connect page, the Flash backup page incorrectly says that I haven't got Flash backup activated: I tried deactivating Flash backup and activating it again, which didn't help. I then checked the forum and found this thread at the very top, so am guessing there's an issue somewhere!!

Thank you so much @JorgeB. That has been bugging me for ages!! As long as I haven't messed up and the space is available, then I'm good!!

Hi, I'm using Unraid Version: 6.12.4 and I've got three SSDs, 1TB each, in a raid 1 cache pool, which i think should get me 1.5TB of usable space. The Main tab shows that the cache size is 1.5TB in total, with 15.7GB used and 991GB free. Why doesn't the used plus the free space equal 1.5TB There seems to be half a terebyte missing!! I've included more screenshots and the diagnostics, if needed. Any help in understanding what is going on would be appreciated. Paul

Hi, I wouldn't worry too much as there's 10 gigabits between everything except for the last leg out to your ISP. They are both pretty sensible ways to connect everything up and I doubt there'll be any difference in performance at all between the two topologies you've sketched out. I would pick your topology based upon practical considerations such as the layout of your house, where the equipment is to be kept, how easy it's going to be to run any new cabling, what existing cables (or drill holes) you can utilise, where you want a stronger WiFi signal, things like. Thinking about stuff like this will probably make the decision for you.

I'm assuming a reallocated sector count of 64,712 is hilariously bad! is this the worst??: I'm new to Unraid and this is a test rig at the mo, with no data on there to lose. Have been watching the awesome @SpaceInvaderOne on YT (Total Legend) and playing with the preclear plugin. I had to mute the Telegram bot i set up as it spent the last day and a half relentlessly spamming me with notifications. The other drives i pre-cleared were done just fine but this one, the preclear log suggests it gave up at quarter past one this morning: Sep 04 20:12:36 preclear_disk_Z1F1VMBS_20858: Preclear Disk Version: 1.0.29 Sep 04 20:12:38 preclear_disk_Z1F1VMBS_20858: Disk size: 3000592982016 Sep 04 20:12:38 preclear_disk_Z1F1VMBS_20858: Disk blocks: 732566646 Sep 04 20:12:38 preclear_disk_Z1F1VMBS_20858: Blocks (512 bytes): 5860533168 Sep 04 20:12:38 preclear_disk_Z1F1VMBS_20858: Block size: 4096 Sep 04 20:12:38 preclear_disk_Z1F1VMBS_20858: Start sector: 0 Sep 04 20:12:49 preclear_disk_Z1F1VMBS_20858: Pre-read: pre-read verification started 1 of 5 retries... Sep 04 22:43:34 preclear_disk_Z1F1VMBS_20858: Pre-Read: progress - 25% read @ 82 MB/s Sep 05 00:45:03 preclear_disk_Z1F1VMBS_20858: Pre-Read: progress - 50% read @ 113 MB/s Sep 05 04:40:56 preclear_disk_Z1F1VMBS_20858: Pre-Read: progress - 75% read @ 28 MB/s Sep 05 10:28:01 preclear_disk_Z1F1VMBS_20858: Pre-Read: elapsed time - 14:15:08 Sep 05 10:28:01 preclear_disk_Z1F1VMBS_20858: Pre-read: pre-read verification completed! Sep 05 10:28:03 preclear_disk_Z1F1VMBS_20858: Zeroing: zeroing the disk started 1 of 5 retries... Sep 05 10:28:03 preclear_disk_Z1F1VMBS_20858: Zeroing: emptying the MBR. Sep 05 11:31:05 preclear_disk_Z1F1VMBS_20858: Zeroing: progress - 25% zeroed @ 196 MB/s Sep 05 12:38:54 preclear_disk_Z1F1VMBS_20858: Zeroing: progress - 50% zeroed @ 174 MB/s Sep 05 13:57:07 preclear_disk_Z1F1VMBS_20858: Zeroing: progress - 75% zeroed @ 143 MB/s Sep 05 15:42:17 preclear_disk_Z1F1VMBS_20858: Zeroing: progress - 100% zeroed @ 15 MB/s Sep 05 15:42:19 preclear_disk_Z1F1VMBS_20858: Zeroing: zeroing the disk completed! Sep 05 15:42:21 preclear_disk_Z1F1VMBS_20858: Signature: writing signature... Sep 05 15:42:23 preclear_disk_Z1F1VMBS_20858: Signature: verifying Unraid's signature on the MBR ... Sep 05 15:42:26 preclear_disk_Z1F1VMBS_20858: Signature: Unraid preclear signature is valid! Sep 05 15:42:27 preclear_disk_Z1F1VMBS_20858: Post-Read: post-read verification started 1 of 5 retries... Sep 05 15:42:28 preclear_disk_Z1F1VMBS_20858: Post-Read: verifying the beginning of the disk. Sep 05 15:42:28 preclear_disk_Z1F1VMBS_20858: Post-Read: verifying the rest of the disk. Sep 05 16:59:05 preclear_disk_Z1F1VMBS_20858: Post-Read: progress - 25% verified @ 114 MB/s Sep 05 18:24:05 preclear_disk_Z1F1VMBS_20858: Post-Read: progress - 50% verified @ 168 MB/s Sep 05 18:56:28 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 18s) Sep 05 18:56:28 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 18:56:51 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 18:57:30 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 18:57:31 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 18:57:51 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 18:58:53 preclear_disk_Z1F1VMBS_20858: killing smartctl with pid 20679 - probably stalled ... Sep 05 18:58:53 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 32s) Sep 05 18:58:55 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 18:59:15 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 19:13:03 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 18s) Sep 05 19:13:05 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 19:13:25 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 19:44:11 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 19:44:13 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 19:44:34 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 20:46:19 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 20:46:21 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 20:46:41 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 20:49:39 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 21s) Sep 05 20:49:41 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 20:50:01 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 20:52:08 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 16s) Sep 05 20:52:10 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 20:52:30 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:17:56 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 17s) Sep 05 21:17:58 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:18:19 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:24:49 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 20s) Sep 05 21:24:51 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:25:11 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:29:59 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:30:01 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:30:22 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:31:14 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 19s) Sep 05 21:31:16 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:31:36 preclear_disk_Z1F1VMBS_20858: killing smartctl with pid 11474 - probably stalled ... Sep 05 21:31:58 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:32:38 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:32:40 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:33:00 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:38:21 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:38:23 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:38:43 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:41:03 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 21s) Sep 05 21:41:05 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:41:25 preclear_disk_Z1F1VMBS_20858: killing smartctl with pid 28420 - probably stalled ... Sep 05 21:41:47 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:43:14 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:43:16 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:43:36 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:44:34 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:44:35 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:44:56 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:46:28 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:46:30 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:46:50 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:52:11 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 22s) Sep 05 21:52:13 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:52:33 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 21:53:09 preclear_disk_Z1F1VMBS_20858: Pause (smartctl run time: 19s) Sep 05 21:53:11 preclear_disk_Z1F1VMBS_20858: Paused Sep 05 21:53:31 preclear_disk_Z1F1VMBS_20858: Resumed Sep 05 23:07:35 preclear_disk_Z1F1VMBS_20858: Post-Read: progress - 75% verified @ 141 MB/s Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: elapsed time - 9:25:34 Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd command failed, exit code [1]. Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429281+0 records in Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429280+0 records out Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997417410560 bytes (3.0 TB, 2.7 TiB) copied, 34201.7 s, 87.6 MB/s Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429286+0 records in Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429285+0 records out Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997427896320 bytes (3.0 TB, 2.7 TiB) copied, 34223 s, 87.6 MB/s Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429289+0 records in Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429288+0 records out Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997434187776 bytes (3.0 TB, 2.7 TiB) copied, 34237.3 s, 87.5 MB/s Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429292+0 records in Sep 06 01:15:32 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429291+0 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997440479232 bytes (3.0 TB, 2.7 TiB) copied, 34250.2 s, 87.5 MB/s Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429296+0 records in Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429295+0 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997448867840 bytes (3.0 TB, 2.7 TiB) copied, 34269.6 s, 87.5 MB/s Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429300+0 records in Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429299+0 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997457256448 bytes (3.0 TB, 2.7 TiB) copied, 34283.4 s, 87.4 MB/s Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429421+0 records in Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429420+0 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2997711011840 bytes (3.0 TB, 2.7 TiB) copied, 34295 s, 87.4 MB/s Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429590+0 records in Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429589+0 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2998065430528 bytes (3.0 TB, 2.7 TiB) copied, 34315 s, 87.4 MB/s Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429590+0 records in Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429590+0 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2998067527680 bytes (3.0 TB, 2.7 TiB) copied, 34378.8 s, 87.2 MB/s Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: dd: error reading '/dev/sdb': Input/output error Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429590+1 records in Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 1429590+1 records out Sep 06 01:15:33 preclear_disk_Z1F1VMBS_20858: Post-Read: dd output: 2998069596160 bytes (3.0 TB, 2.7 TiB) copied, 34381.6 s, 87.2 MB/s Sep 06 01:15:35 preclear_disk_Z1F1VMBS_20858: Post-Read: post-read verification failed! Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Error: Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Reallocated_Sector_Ct 0 15624 Up 15624 Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Power_On_Hours 8965 8994 Up 29 Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Runtime_Bad_Block 1 1 - Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: End-to-End_Error 0 0 - Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Reported_Uncorrect 30 54 Up 24 Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Airflow_Temperature_Cel 40 48 Up 8 ->Failed in Past<- Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Current_Pending_Sector 48 8 Down 40 Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Offline_Uncorrectable 48 8 Down 40 Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: UDMA_CRC_Error_Count 4 4 - Sep 06 01:15:42 preclear_disk_Z1F1VMBS_20858: S.M.A.R.T.: Sep 06 01:15:44 preclear_disk_Z1F1VMBS_20858: error encountered, exiting ... at this point the reallocated sector count was 15,624, but my Telegram notifications show the process was still going after half past five this morning, and show the count continued way past 15,624 to the 64k range, where it is now. Am just wondering how dreadful the state of the drive is, and why the preclear log suggests the process ended before it actually did. any comments or observations from the community would be welcome. 😃 testerv2-diagnostics-20230906-1245.zip

That is exactly what i was looking for. Thanks! What cables would i need to connect the backplate to an LSI 9211-8i?

Hi, i've just bagged a "Genuine LSI MegaRAID 9211-8i IT Mode" card from eBay. No cables. I'm a bit of a noob and trying to get my first rig together. I read somewhere there are different types of Sata breakout cables. Would anyone be able to point me to the right pair of breakout cables i'm going to need? thanks, Paul.

Hi, would this work? My board has only PCIe 2.0 slots. would this cause issues?

Hi, I'm looking to upgrade my little 2-bay entry level QNAP, which is ace and uses hardly any electricity (but was expensive to buy) to something with a bit more capacity and flexibility. I've put together a test rig from old PC bits and a trial Unraid license, and I like what I see, so I'm going to level up a bit and would like some advice please. I assumed I'd need a motherboard with a ton of SATA ports, and found this on AliExpress. Has anyone got any opinions on this or has anyone got one of these??? I'm looking for something with enough CPU for a home server (maybe 10-12 disks and a few apps like SABnzbd and Plex) but also would like something economical on the electricity usage. It doesn't need to be mega fast or powerful. The motherboard I linked to above has an integrated N5095. Is this suitable for my use case? Has anyone else got a rig running an N5095? Should i steer clear of this CPU and motherboard combo and get something else with a few SATA expansion cards, perhaps? any suggestions would be appreciated. thanks, Paul.