sannitig

It used to be part of the array and I replaced it with a larger 6TB disk. Then I bought the SATA controller and added the disk back into the server. Added it to the array and Unraid began wiping it (took like 24 hrs). Once complete it shows as unmountable. I thought the wiping of the disk was the same as formatting. I need to run the format?

Looks like the drive is part of the array now but after the pre-clear of the drive it is unmountable. How to fix this. If it is not fixable how can I remove this drive from the array and toss it?

Thanks. Sent you a small token for helping me out lately. I will add this disk to the array and keep an eye out for new errors. The fact that the SMART passed OK means they were there before? They may have been....This drive has been pulled out of the array for over a year so I do not remember.

I just installed a MZHOU 2 SATA Expansion Card, PCI-E 3.0 GEN3 JMICRON + JMB582 Chip (https://www.amazon.ca/dp/B099ZCXJLQ?psc=1&ref=ppx_yo2ov_dt_b_product_details) I then reinstalled a drive I had sitting on a shelf that used to be part of the array and the moment I spun up the server the drive has a SMART Error: 187 Reported uncorrect 0x0032094094000 Old age Always Never 6 I have not yet assigned this disk because of this error, I came straight to the forum. How serious is this? How can I tell if it the drive or the controller I just installed? I also have two other drives with the: 199 UDMA CRC error count 0x000a200200000 Old age Always Never 2 I have read that these are generally not a concern and are due to bad sata cables (my motherboard is approx 15 years old though), I have just changed both of those cables. SMART test on the dev1 drive has completed without error attched. I don't understand how that is possible since we know there is an error ST4000DM000-1F2168_Z300G774-20240417-2027.txt

Excellent. That being said, would be be unwise to over provision your PCIe x1 throughput by adding more disks than you have throughput? for example using a 4 port SATA controller on PCI 1.0. If you leave your parity drive on MOBO dedicated SATA and your cache on MOBO dedicated SATA, one would believe it is fine to over provision or am I missing something? I am trying to think of a scenario where all disks are read/writing at once; then over provisioning would be unwise. Parity check perhaps?

TY! I believe my MOBO may be using PCIe 1.0 (250MB/s). My question is, when you use a SATA controller how are the lanes split? Are the lanes split evenly even if only one port is in use? Or are they split only if you use more than one SATA port? Another way of putting it: I install a 2 port sata controller, does each port receive 125MB/s dedicated or if I decide to only install one disk and only use one port will it receive the full 250MB/s while other port with no disk currently uses 0MB/s?

Are we still recommending this controller for Unraid as of today? I am in need of an extra SATA port (or two) for my PCIe 1x slot. MOBO GA-MA785GM-UD2H-rev-10, very old but solid as a rock and I assume the PCIe x1 is ver 1.0, hence a 2 port controller is sufficient.

About to watch the video but want to ask 'why use SAS expander if you are using SATA drives?' What is the purpose of this and not just use a SATA expander? If the SATA drive has a read/write of 120MB/s, what does using a SAS HBA vs a SATA HBA on SATA drives do?

Bump. Should I get a SATA expander? If so, where do the extra power cables come from? How do people normally power 14 HDD with your average PSU? I have not seen a PSU with 14 HDD cables. Clearly I would love some assistance with rejigging my rig

Rebuilding my 14 yr old unraid server because I don't want to keep upgrading my drives (running GIGABYTE AM2 MOBO with only 5 SATA ports, built to last!). Rather, I would like to start expanding my array with more drives. Wondering what the best option would be in terms of upgrading for minimum 10 drives. Should I just get a new case/MOBO/CPU etc? Seems like over kill since everything is working well. What would you guys do?

Is there any way to see the activity so I can determine what I just deleted?

But what is the point of "High Water Table > Automatically split any directory as required'? I thought that meant unraid will figure out the data allocation

Thanks JorgeB. Two follow up questions: 1. Will this cause the disk to "Become full" and the torrent will fail or will unraid be smart enough to divide it up and start a new disk once disk2 is full? 2. If the former happens and the torrent fails, how do I try again without having this limitation?

Hello can somebody explain the behavior that I am seeing? I have a large 3.5TB torrent downloading but for some reason disk2 keeps filling up. I still have 1.75TB left to download and I am concerned disk2 will fill right up and the torrent will fail. Should the writing not have switched to disk3 already with 1.15TB left to create a more equalized data distribution?

wtf is the point of a server then? Don't have users with R/W, don't expose it to the internet. Why not just say, don't build an unraid server. There, problem solved.