sgibbers17

Thanks, I think there is a trend to have more pcie and the new 12v GPU connectors on PSUs, the old seasonic power supplys 520w/750w had 4/5 sata/molex ports and 4/6 pcie/CPU ports. As for the 5v header not being enough according to the data sheets that I found for my HDD and the seasonic email there is enough head room for me to not worry about.

Will unRAID notify me or will I have to watch it?

Is that a normal SAS drive thing or is that a limitation of unRAID? I just finished a long self test and these are the results. It looks fine to me but I don't know much about smart data other than look for sector problems and I don't see any references to that in the data and I don't see any problems in the error section. What should I keep an eye out for and will unRAID notify me if there is a problem? I would have went with a SATA drive but the SAS drive was significantly cheaper and my server is SAS capable so I figured I would give it a try. This is also my first time purchasing a recertified drive so I am more leary than normal. smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.12.54-Unraid] (local build) Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: WDC Product: WUH721414AL4204 Revision: C400 Compliance: SPC-4 User Capacity: 14,000,519,643,136 bytes [14.0 TB] Logical block size: 4096 bytes LU is fully provisioned Rotation Rate: 7200 rpm Form Factor: 3.5 inches Logical Unit id: 0x5000cca25846b994 Serial number: 9JH7WT8T Device type: disk Transport protocol: SAS (SPL-4) Local Time is: Wed Jan 14 11:23:27 2026 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Enabled Read Cache is: Enabled Writeback Cache is: Enabled === START OF READ SMART DATA SECTION === SMART Health Status: OK Format status indicates no format since manufacture Current temperature = 34 Lifetime maximum temperature = 41 Lifetime minimum temperature = 22 Maximum temperature since power on = 34 Minimum temperature since power on = 22 Manufactured in week 06 of year 2025 Specified cycle count over device lifetime: 50000 Accumulated start-stop cycles: 2 Specified load-unload count over device lifetime: 600000 Accumulated load-unload cycles: 4 Elements in grown defect list: 0 Error counter log: Errors Corrected by Total Correction Gigabytes Total ECC rereads/ errors algorithm processed uncorrected fast | delayed rewrites corrected invocations [10^9 bytes] errors read: 0 0 0 0 1209 14146.051 0 write: 0 0 0 0 4 64.425 0 verify: 0 0 0 0 27 0.000 0 Non-medium error count: 0 SMART Self-test log Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ] Description number (hours) # 1 Background long Completed - 51 - [- - -] # 2 Background short Completed - 28 - [- - -] Long (extended) Self-test duration: 95340 seconds [26.5 hours] Background scan results log Status: scan is active Accumulated power on time, hours:minutes 51:43 [3103 minutes] Number of background scans performed: 0, scan progress: 3.03% Number of background medium scans performed: 0 General statistics and performance log page: General access statistics and performance: Number of read commands: 53634455 Number of write commands: 144939 number of logical blocks received: 15728697 number of logical blocks transmitted: 3453625643 read command processing intervals: 0 write command processing intervals: 0 weighted number of read commands plus write commands: 0 weighted read command processing plus write command processing: 0 Idle time: Idle time intervals: 2281490 in seconds: 114074.500 in hours: 31.687 Protocol Specific port log page for SAS SSP relative target port id = 1 generation code = 1 number of phys = 1 phy identifier = 0 attached device type: SAS or SATA device attached reason: power on reason: unknown negotiated logical link rate: phy enabled; 12 Gbps attached initiator port: ssp=1 stp=1 smp=1 attached target port: ssp=0 stp=0 smp=0 SAS address = 0x5000cca25846b995 attached SAS address = 0x500605b00d445880 attached phy identifier = 4 Invalid DWORD count = 0 Running disparity error count = 0 Loss of DWORD synchronization count = 0 Phy reset problem count = 0 relative target port id = 2 generation code = 1 number of phys = 1 phy identifier = 1 attached device type: no device attached attached reason: unknown reason: power on negotiated logical link rate: phy enabled; unknown attached initiator port: ssp=0 stp=0 smp=0 attached target port: ssp=0 stp=0 smp=0 SAS address = 0x5000cca25846b996 attached SAS address = 0x0 attached phy identifier = 0 Invalid DWORD count = 0 Running disparity error count = 0 Loss of DWORD synchronization count = 0 Phy reset problem count = 0

A Seasonic engineer told me via email that the peripheral ports can't handle that amperage but the pcie port can for my specific PSU. They gave me a amperage per pin on each of the different ports. This was mentioned in a previous post.

It isn't a matter of how many molex/sata cables I have, it's a matter of how many 12v amps on that the peripheral ports on the PSU can handle. It seems that the peripheral PSU ports can't hand the 12v amps but the GPU/pcie ports can but don't supply 5v. So I would have to make a custom cable that takes the 12v rail from the pcie port and the 5v from the peripheral port. I have not done that yet but will when I expand my array.

The preclear I started showed no smart data is that expected and how would I be able to tell if a SAS drive is failing? This is my first SAS drive.

I just purchased a Manufacturer Recertified WD Ultrastar DC HC530 SAS drive from serverpartdeals.com and went to preclear it to test the drive and it is not showing smart data. I have tried every SMART controller type when no success. I have uploaded screenshots of the smart data screen and the preclear screen that does not show the expected smart data like reallocated or pending sectors.. I ran a short SMART test and currently running an extended. I also downloaded the smart data from the drive after the short test and uploaded it here. Can someone please help me get the smart data displayed correctly so I can make sure the drive is operating correctly and I will get notifications when it starts to go bad? I am using a 45drives av15 case with a LSI HBA SAS Controller 9400-16i. WUH721414AL4204_9JH7WT8T_35000cca25846b994-20260113-1227.txt

Its not the 5V I'm worried about. According to Seasonic the peripherals are only good for 5 amps for the 12v pin each. That's not enough when each drive is >1 amp at 12v. It looks Like I'm going to have to make a custom cable using the 12v from the PCIe cables and 5v from the molex. Seasonic told me that each pin on the PCIe connector is good for 8 amps and on my PS there are 3 unused CPU/PCIe connectors with 4 12v pins each. That makes 96 amps at 12v. Since I am not going to have a GPU that requires power I can use those connectors.

I have a NORCO RPC-4224 with a "01 SAS 12Gb v1.3" backplane and a 1000w seasonic power supply but only has 3 peripheral sata/molex connectors on the back that according to seagate only can handle 5 amps each and 15 amps in total. If I want to fill this case with 24 drives that will not be enough. I know that on my 45drives av15 backplane only has 12v supplied to it. Does the NORCO RPC-4224 require the 5V pin on the molex connector? I was thinking if the backplanes do not require 5 volts and only need 12 volts I could make custom cables using the PCIe/CPU connectors.

I currently have an unRAID server and am adding a TrueNAS server for long term storage/backup for my unRAID server that will eventually be in another building. My unRAID server currently has a Threadripper 1900x with a nvida t400 for plex docker transcodes. My unRAID server is only used for file storage and serving media via plex. I am upgrading my PC and will be using the old hardware to build another server. The other hardware will be a ryzen 5950x. My question is what MB/CPU should I put in the unRAID server and the TrueNAS server? Keep the Threadripper 1900x in the unRAID server or install the ryzen 5950x and use the 1900x with TrueNAS? The TrueNAS server will only be for file storage and probably only be turned on for adding files to it. I've read that the the zfs file system could benefit from a better CPU. If there are people other there that run both unRAID and TrueNAS please let me know your opinion.

The first thing that I can think of is are you sure you have the correct IP address. If your server has more than one Ethernet jack and you plugged it into a different jack you will have a different IP address.

I am currently running a 2 sata drive BTRFS raid0 for my cache and a 2 nvme drive BTRFS mirror for my dockers and VMs. I keep having issues with nvme drives on my server and not sure what is causing it, it might be the motherboard. So I am switching out the NVME drives for sata and bought 2 1TB drives. Now I have 4 identical sata drives and am wondering what would be faster now that I am using SATA instead of nvme. My options are. 2 drive stripped for cache and 2 drive mirror for Dockers and VMs Or 4 drive ZFS raidz1 for cache, Dockers and VMs on one pool. I'm leaning towards this one.

The alarm came back in with no writes or reads happening since I did the erase and clear and no changes to START attributes. Here is a screen shot of the thumbs down and the smart attributes that was asked for. It seams that acknowledge the alarm does not permanently acknowledge it. It re-alarmed when I stopped my array the drive is an unassigned drive and not connected to the array, pool, mounted, or formated. I saw a setting in the SMART setting that may help "SMART notification tolerance level" it looks like that might work but if I understand it if the threshold is 10 it just adds a percentage to that so to get the new threshold to 17 sectors I would need to set the threshold to 70% but the highest is 50%. I started and stopped my array to see if I could reproduce the error and it did come in twice in a row. I started with 5% and I haven't had the alarm come in so I guess I don't understand the setting. It also looks like its for all the attributes so I don't want to set it too high and mask another attribute problem.

I had performed an extended SMART test and I could not get the alarm to come back. I did take a screenshot of the last alarm that was in the notifications. I have uploaded both the screenshot and the last SMART test report. ST6000VN0033-2EE110_ZAD7AD6B-20250903-0919.txt

I'll see if it is back in when I get home but it hasn't come back since I finished the 3x preclear. It came in during the 3x preclear a few times but when I did the erase and clear it did not come in at all.

Here is a copy of my SMART report with a preclear log for 3 cycles and an erase and clear log. I don't see anything that says failing now, but I have acknowledged the alarm multiple times with no changes to attributes that I can tell. ST6000VN0033-2EE110_ZAD7AD6B-20250902-1145.txt preclear_report_ZAD7AD6B_2025.08.30_18.34.49.txt preclear_report_ZAD7AD6B_2025.09.02_05.18.23.txt

Thanks. Fluke wasn't the best word for it, but it was easier to say I don't think the drive is in immediate failure and probably won't get worse for a while. It would be nice to be able to put a new threshold in just like the temperature. I definitely don't want to disable the alarm notification because as I don't think the drive is bad now but in a few months down the road it might.

The alarm comes back in with out the reallocated sectors changing, the alarm comes in when the drives reports that the reallocated have passed the threshold. Thumbs up/down button only acknowledges the alarm temporarily and comes back in. Once again the the thumbs up/down button does not work. There are no changes in my SMART values. I am looking for a way to change or override the threshold for reallocated sectors in such a way that if they continue to rise it will tell me. As it is now I will alarm every time the drive spins up regardless of any changes in SMART values. I believe that the reallocated sectors were a fluke as the drive has gone through multiple full clears with no changes to reallocated sectors. I don't know if the problem was caused by a bad cable connection, interference, corrupt data, or maybe even actual bad sectors but it seems to be an isolated incident.

I have done that it comes back every time the drive reports SMART status.

I have a 6TB Seagate drive that had 8 reallocated sectors during a full metadata download on my jellyfin server and then an 8 additional when I copied the data off that drive so 16 in total. Both these operations were only reads off the drive. I did a parity check after moving all the data of the drive and then decided to stress test the drive by running 3 pre-clears on it and had no changes to pending or reallocated sectors (stayed at 16 reallocated sectors) so I believe this may have been a fluke. The SMART Threshold for the drive is 10 sectors. Is there a way to change or override the Threshold to lets say 17 so I can still use the drive and get a warning if they increase? I have tried just acknowledging the alarm but it re-alarms when the drive is spun up. I am running an additional erase and clear now to see if there is any change with a random write and a clear.

Step 15 "The data drive rebuild begins. Parity is now valid, and the array is started." "Once again, you can patiently watch the progress, takes a long time too! All of the contents of the old data drive are now being reconstructed on what used to be your parity drive, but is now assigned as the replacement data drive." The way I read that is that the my old 6TB parity driver will be reconstructed with the data from the old data drive. If I don't plan on using the old 6TB drives should I just do a new config with changing the 2 parity drives and the empty data drive and doing a fresh parity calc. I don't have anything stored on my server that can't be replaced.

Unless I'm misunderstanding the parity swap process you are moving the old parity drive to be a new data drive by reconstructing the data on the old parity drive. I don't want my old parity drives part of the array after upgrade. I'm looking to replace 3 of my 6TB drives with 3 18TB drives. Is there a process for copying the parity drive without reconstructing the data drive.

I just recently purchased 3x 18TB drives to increase my storage capacity. I'm lucky I did because while preclearing the drives on of my data drive had the reallocated sector count increase from 0 to 8 while jellyfin was doing a full refresh of meta data. Preemptively I moved the data off that drive until the preclears were done. While moving data the reallocated sector count remained at 8. I started a parity check and the sector count increased again to 16. I have 9 total drives at 6TB each including 2 parity drives. My plan was to replace the 2 parity drives and 1 data drive with the 18TB buy replacing the parity drives 1 at a time first then add the data drive while doing parity checks in-between the replacements. But now I have this failing drive and was wondering if I should still proceed with my plan or should I change it. The failing drive has no data on it.

I don't mean that Seagate itself was involved only that the majority of the drives that were used drives were Seagate drives. I even read articles about drives bought from reputable retail stores being also used drives.

Right now I have a mix of HGST Deskstar NAS, and Iron Wolf Pro all 6TB drives. I am looking to upgrade add 12 TB or larger drives and with the recent Seagate scandal of used drives being sold as new and HGST now part of WD and the WD Gold drives being basically rebranded HGST drives, I would buy WD Red Pros or Golds. I was looking to get the fastest speed drives that are NAS or Enterprise drives I could because parity checks will take even longer with 12 TB drives. Also Price is a factor since I will need to purchase 3 drives just to make use of all 12 TB because I am using 2 parity drives. I also am running at 15 drive 45drives case with a LSI 9305-24i SAS card so I could use 12GB/s SAS drives. Would there be a benefit to using SAS over SATA? I just checked my order history and the HGST drives have been installed since 2015 and 2016. The Iron Wolf Dives have been installed since 2019. That's a pretty good run with no errors that I could remember.