-
spartanooof started following Upgrading both parity disks, best way with minimal downtime?
-
Upgrading both parity disks, best way with minimal downtime?
I currently have 2x14 TB drives as parity, I'm bumping both of those to 24TB so I can start to add 24 TB drives down the road instead of 14s. Now how can I go about this without days of downtime. Since it's dual parity I'm guessing I can swap 1 new drive in for one and let it do its thing and add parity info to the new disk then swap the other 14 TB drive. Question is will the array be able to operate during this time? Does prefill/clear help here? Better suggestions? Thanks
-
Removing a drive from BTRFS cache pool
So I originally got a little too excited when I got new cache equipment and rushed them all into service into a single pool. I now want to split it so I can have downloads to one and another as a content cache. So currently I have 3 drives in my cache a 1 TB, 2 TB and 4 TB. I want to remove the 4 TB from the pool. From what I have read it seems I could just remove it from the pool then spin up and let the cache fix itself and then after that's done create a new pool with just the 4 TB drive in it. Is this correct? I don't want to lose data from the cache as it's currently got the appdata folders sitting on it with no backup sync. Thank you
-
[Plugin] NUT v2 - Network UPS Tools
After looking through some more things im leaning towards the UPS USB port actually being bad. Attached is the debug zip nut-debug-20240829110532.zip
-
[Plugin] NUT v2 - Network UPS Tools
Hello. I have a rack mounted cyber power unit and whenever I try to start the NUT driver I get: Aug 27 17:48:52 Domain rc.nut: libusb1: Could not open any HID devices: insufficient permissions on everything I have tried different ports, cables & restarts. This also started as soon as I switched UPS, so it was working just fine.
-
[6.12.3] SAS drives not mountable
I have recently moved my Unraid setup to using an LSI 9300-16i while also adding 2 SAS drives. All the legacy SATA drives came up and were recognized by Unraid. The 2 new SAS drives are under "Unassigned Disk Devices" but both have their mount button grayed out. I assumed this was because they are likely in 520 instead of 512 format. So I proceeded to run `sg_scan -I` and grabbed the disk id from there. But then running `sg_format --format --size=512 --fmtpinfo=0 -v /dev/sg2` results in `device not ready` so I ran `scsi_ready -vvv /dev/sg2` and got the following: sg_turs -vvv /dev/sg2 open /dev/sg2 with flags=0x800 test unit ready cdb: [00 00 00 00 00 00] duration=0 ms test unit ready: Descriptor format, current; Sense key: Not Ready Additional sense: Logical unit not ready, power cycle required Descriptor type: Field replaceable unit code: 0x1 Descriptor type: Vendor specific [0x80] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Raw sense data (in hex), sb_len=28, calculated_len=28 72 02 04 22 00 00 00 14 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 device not ready Completed 1 Test Unit Ready commands with 1 errors Same result for the second drive as well. So then I figured maybe the card needs to be flashed to a newer firmware and set to IT mode so I flashed it to the latest version and then checked in the bios and confirmed both chips on the card are set to IT mode. Now im kinda at a loss on how to proceed. I doubt both drives(new) arrived dead. Thanks for the help
spartanooof
Members
-
Joined
-
Last visited