Paul_G

Amazing. Thank you!

Hi, I've just moved 8 drives to an enclosure with a backplane. Previously I used two SAS to SataX4 breakout cables to connect the drives to my HBA, but now they're all connected via one SAS to SAS cable between the HBA and the back plane. Because both the HBA and the backplane have two SAS ports, would there be any benefit to using a second SAS to SAS cable? Is this a terrible idea? Thanks.

I have been pondering these very questions. thanks all.

Thanks. Yes. was an nvidia driver issue. I got Plex back up and running pretty quickly by removing the NVIDIA_DRIVER_CAPABILITIES and NVIDIA_VISIBLE_DEVICES variables, and the --runtime=nvidia extra parameter (need to click on advanced view). This got Plex back in action (but without a GPU) and i've only just now had chance to try to figure out why it stopped working. Turned out to be that the card is just too old now. Logs say "The NVIDIA GeForce GT 710 GPU installed in this system is supported through the NVIDIA 470.xx Legacy drivers." . When i looked into getting these installed they aren't in the nvidia plugin anymore, as confirmed here by @ich777 all was fine when i was on Unraid 6.12.15 but no more. nevermind. That card was just junk i had lying around anyway, so no big deal.

Hi, I've just upgraded from 6.12.15 (or possibly 6.12.14) to 7.1.4 all seemed ok except Plex aint working. The few other Docker containers i've got started ok and are running, i get this when trying to start the Plex container: I removed the container and re-added via the previous apps tab, and get "The command failed" 😭 I backed up the USB before the upgrade so I should be able to roll back, but if anyone could help sort this out it would be very much appreciated. Paul. gromit-diagnostics-20250903-2033.zip

bingo. sorted. Thanks for the help just now and also for everything else you do with the apps and repos. appreciated!

Howdy, just updated to the latest version. worked just fine beforehand but now getting this -> Other docker containers are working as usual. Have disabled and enabled docker service. same. have turned the server off and on again. same. am getting some errors on the logs -> tried removing the container and the image and reinstalling from the previous apps template. seemed to make no difference, but slightly different info in logs:> 2025-01-06 22:38:05,313 INFO Included extra file "/etc/supervisor/conf.d/novnc.conf" during parsing 2025-01-06 22:38:05,314 INFO Set uid to user 0 succeeded 2025-01-06 22:38:05,342 INFO supervisord started with pid 7 2025-01-06 22:38:06,352 INFO spawned: 'start' with pid 94 2025-01-06 22:38:06,354 INFO reaped unknown pid 8 (exit status 0) 2025-01-06 22:38:06,706 DEBG 'start' stderr output: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 2025-01-06 22:38:06,708 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2025-01-06 22:38:06,710 DEBG 'start' stderr output: Xvnc TigerVNC 1.13.1 - built May 25 2024 17:13:24 Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12101013 Mon Jan 6 22:38:06 2025 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 2025-01-06 22:38:07,667 DEBG 'start' stderr output: [mi] mieq: warning: overriding existing handler (nil) with 0x55d6487ab6e0 for event 2 [mi] mieq: warning: overriding existing handler (nil) with 0x55d6487ab6e0 for event 3 2025-01-06 22:38:07,966 DEBG 'start' stderr output: WebSocket server settings: 2025-01-06 22:38:07,968 DEBG 'start' stderr output: - Listen on :6080 - Web server. Web root: /usr/share/webapps/novnc - No SSL/TLS support (no cert file) - proxying from :6080 to localhost:5900 2025-01-06 22:38:07,975 DEBG 'start' stdout output: ObRender-Message: Unable to load the theme 'Adwaita Revisited Dark' 2025-01-06 22:38:07,976 DEBG 'start' stdout output: ObRender-Message: Falling back to the default theme 'Clearlooks' 2025-01-06 22:38:08,456 DEBG 'start' stderr output: ERROR: openbox-xdg-autostart requires PyXDG to be installed 2025-01-06 22:38:10,551 DEBG 'start' stdout output: [info] tint2 not running 2025-01-06 22:38:10,597 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes 2025-01-06 22:38:10,611 DEBG 'start' stderr output: tint2: xRandr: Found crtc's: 1 2025-01-06 22:38:10,611 DEBG 'start' stderr output: 2025-01-06 22:38:10,612 DEBG 'start' stderr output: [1;34mtint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96 2025-01-06 22:38:10,614 DEBG 'start' stderr output: tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc 2025-01-06 22:38:10,619 DEBG 'start' stderr output: tint2: real transparency on... depth: 32 2025-01-06 22:38:10,626 DEBG 'start' stderr output: t 2025-01-06 22:38:10,627 DEBG 'start' stderr output: int2: panel items: TSC tint2: Systray composited rendering on tint2: nb monitors 1, nb monitors used 1, nb desktops 1 tint2: panel 1 uses scale 1 2025-01-06 22:38:10,730 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2025-01-06 22:38:10,746 DEBG 'start' stderr output: tint2: systray window 8388621 2025-01-06 22:38:10,747 DEBG 'start' stderr output: tint2: systray started 2025-01-06 22:38:13,278 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 142 minor 6 serial 501 2025-01-06 22:38:13,279 DEBG 'start' stderr output: error 9: BadDrawable (invalid Pixmap or Window parameter) request 139 minor 4 serial 502 error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0 serial 524 any help would super cool. thanks for looking.

I just shut it down via ssh: It went off on it's own (without me having to hold down the power button). I've switched it back on and extracted more diagnostics, attached.

Good afternoon, Whenever I try to shutdown or reboot the server, it always hangs partway through the process. I always end up having to hold the power button on the front of the machine to finish the shutdown (after waiting 10 mins or so). Interestingly, it doesn't seem to have this issue when using the poweroff or reboot command when SSHing in, or using the console on the web GUI. I try not to go this route though as I'm unsure if this is a good idea or not. Any help in troubleshooting this would be appreciated. I've not really any idea what to look for in the logs. thanks, Paul. gromit-diagnostics-20240725-1314.zip

I didn't know X1 to x16 adapters were a thing. Thanks. Will look at them. And as the task isn't that heavy, and I just want a chip capable of hardware decoding H.265, I don't really want to spend big. Was hoping someone might have been down this road already 😁

Hey, I've only one PCIe x16 slot on my mobo which is being used by my HBA, so I'm looking for a GPU to go into a PCIe X1 slot to decode one or two H.265/X265 streams from Plex. Any suggestions please? 😃

@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.