Darkguy

Thanks for your help so far. I hit "Zero Log" on both devices, let it finish, then stopped the maintenance-mode-array and restarted it properly. Both disks/emulated disks mount fine now. I can browse the emulated disk2 and see its contents. disk 12 shows up as 153GB used and 7.85TB free; however, when I browse disk 12 (in the Unraid GUI or via mc in the terminal), there it shows up as completely empty. Unfortunately I can not quickly determine if anything is missing - the disk has been in use for about 8 months, so I would guess something should have been on there. Should I stop the array, remove it and try to restore anything on it with Linux tools on another machine? Also, Disk12 still shows up as disabled/content emulated. Can I reactivate it or is it safer to RMA it and swap it out for a new one?

So press the "Zero Log" button and do not attempt to mount the disks first? I always like to understand what is happening - so what exactly happens when pressing the Zero Log button and how does this correspond to "Mount the filesystem to replay the log, and unmount it before re-running xfs_repair"?

I put the array in maintenance mode, ran the XFS Check on disk12 with this output: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. XFS check on disk2 with this output: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap inode pointer to 97 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary inode pointer to 98 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. Should I stop the array and start it in regular mode or press the "Zero Log" button next?

diagnostics-20251104-1339.zipDiagnostics after reboot

Hi, I have a twelve disk array with dual parity (14 disks in total), plus two caches (2 TB and 525 GB). The two parity drives are 8 TB each, disks in the array are a mix of sizes up to that capacity. I had one relatively old 1 TB disk fail a few days ago, ordered an 8 TB replacement which arrived today. I then did the following steps: removed the failed 1 TB disk (disk2) from the server removed another failed 4 TB disk from the server (this one failed months ago and had been replaced by a disk in another bay, I just forgot to remove it originally) ran "Force Smart + DB" in the Disk Location plugin, added locations for three new disks I had added/replaced a few months ago but forgot to update in Disk Location added the new 8 TB drive into the original slot of the failed 1 TB disk ran "Force Smart + DB" in the Disk Location plugin again, as I was prompted Was about to start to pre-clear the new disk, when I noticed a total of three unassigned devices on the dashboard - the new 8TB Seagate disk I was about to pre-clear and two disks that are also part of the array. Those still showed up in the array, but were also shown here, using different device designators (disk9 as sdj and disk 12 as sdn in the array, but as sdk and sdt in unassigned devices). I stopped the array, set disk2 to empty (I planned on replacing disk2 with the new 8 TB drive after pre-clearing and rebuilding the contents there) and noticed that disk12 now also was disabled. I left the failed disk in the disk12 slot for now and restarted the array. The array right now is running but obviously is fully depending on the two parity disks it seems. Maybe this was just some sort of controller snafu that re-initialized the disks? Besides not understanding what happened with the disks getting new device designations I am somewhat nervous about the state of my array right now. It is working for now and all data seems to be there. I plan on preclearing the new disk and replacing the original failed disk with it, then getting another new drive ASAP and replacing the reportedly failed other disk (I believe this is one of the newer ones I got a few months ago, so I should be able to RMA it). Can I easily copy the contents off the emulated disks, or should I leave anything as is? The Unbalanced plugin shows disks 2 and 12 as empty right now, but I guess it bypasses the array layer? Addition info: Case/backplanes: Inter-Tech IPC 4U-4724 Controller: Broadcom SAS 9305-24i Cables: SilverStone CPS06, Slimline miniSAS HD SFF-8643 to miniSAS SFF-8087 View of the array with the three unassigned devices: View of the array now: diagnostics-20251104-1138.zip

Hey everyone, I am currently planning to build a new server and was initially set on using a Ryzen 9 7900. I decided to look at Intel as well and found the Core i7-14700 to possibly be a viable alternative. This new machine will probably be in use for the next 7-10 years, so I want it to have enough power to run a number of VMs and containers without having to worry too much about resources. I will probably run at least two or three Windows VMs (an "on-the-go" semi-production Windows I can access through Guacamole, another one for a Mac-Only relative who needs to run some Windows software for his business) and a few Linux VMs (server and client machines, possibly including Nextcloud AiO) and some homelab-stuff to fool around with. I might also run VMs for Home Assistant (currently on an Odroid N2+), Frigate with a Coral TPU, a backup/failover OPNsense machine and other stuff down the line. The Ryzen has 12 cores, 24 threads with a 65W TDP and up to 88W "max socket power". The i7 has 8 "power cores", 12 "efficiency cores" and a total of 28 threads at 65W TDP and up to 219W "maximum turbo power". The Intel has lower frequencies on all cores in base/turbo mode than the AMD, but I would guess the difference would rarely be detectable in everyday use cases. There is also the i7-14900 with four more efficiency cores and slightly higher frequencies, but at 1.5× the price of the 14700. The Intel iGPU seems to have better support for transcoding in Jellyfin (not using Plex), but then again I also never had the need for transcoding (currently only streaming inside my own LAN/WLAN 99% of the time) and the iGPU would possibly be attached to a VM anyway, so that is not a main concern. What worries me is the 219W vs. 88W max turbo/max socket power draw. I am running my current server on an ancient Phenom X4 9950 (125W TDP) and would like for the new system to draw less power/produce less heat. As a mainboard, I would go with the latest AM5/LGA1700 Supermicro workstation-class boards with ECC support and IPMI (AMD: Supermicro H13SAE-MF; Intel: Supermicro X13SAE-F), RAM would be 4×32 GB ECC Kingston Server Premium (DDR5-5600 for AMD, DDR4-4800 for Intel) The rest of the hardware would look like this: Cache/VM Storage drives: 2× Samsung 990 Pro, 2 TB (M.2, PCIe 4.0 x4); 2× Crucial Crucial MX300 525GB (2,5", re-used from my current server) HDDs: re-use from my current server, a mix of 10× 2.5/3.5" drives ranging from 1 TB to 8 TB (dual-parity); possibly add 2× 16/18/20 TB parity drives early in order to add the current 8 TB parity drives to the main storage pool HBA: Broadcom SAS 9305-24i (PCIe 3.0 x8, SAS3224 chipset, 6× SFF-8643 for a total of 24 SAS/SATA drives over two backplanes), 6× breakout cables SFF-8643 to SFF-8087 Chassis: Inter-Tech IPC 4U-4724 (4U, 24× 2.5"/3.5" Hot-Swap, plus 2× internal 2.5"), plus rails for my 19" rack PSU: be quiet! Pure Power 850 W Fans: 3× Noctua NF-A12 120mm PWM, 2× Noctua NF-A8 80mm PWM CPU Cooler: Noctua NH-D15 (still have to check if the height fits the chassis) UPS: TBD; currently using an APC Back-UPS (950VA/480W), that recently received a new battery The price differences in CPU, mainboard and RAM pretty much even each other out for AMD and Intel configs, coming in at about €3.200 here in Central Europe, including value added tax. Any thought from people who have experience running either or similar CPUs? Any alternate suggestions for my use case?

Hi, I am looking to replace my current server, which was mostly built from used hardware back in early 2017. It's still running well, but power consumption is high and resources are getting low, I am only running one Ubuntu server VM and a few selected Docker containers right now. The new machine would also host a number of VMs (both Windows and Linux, including some production machines for myself and others) and a far larger collection of Docker containers to self-host most of the services I use or would like to use in the future. I would migrate all of my original HDDs (28.5 TB over 10 disks, plus 2×8 TB parity), but renew the cache drives from 2×2.5 SATA SSDs to 2×M.2 PCIe SSDs. I would either try and sell off the old hardware (including a Dell PERC H310 and H200 in IT mode), or keep it around as a backup target (turn it off by WoL and shut it down via script) with a few drives in another part of the house or with a relative. This is my proposed hardware, I am mostly looking for compatibility issues or better options for some components: CPU: AMD Ryzen 9 7900 (12C/24T; 65W TDP; 3.70.5.40 GHz) RAM: 4×32 GB (128 GB total) Kingston Server Premium, DDR5-5600, ECC (unbuffered), CL46-45-45 [48 GB modules with the same specs are also available, but are still a bit expensive when compared to the 32 GB ones] Mainboard: ASUS ProArt B560-Creator (has ECC support and 3× PCIE 4.0 ports at x16/x8/x4 each) - this would run the PCIe 3.0 x8 HBA, 2× PCIe 4.0 x4 M.2 SSDs and possibly a PCIe 2.1 x4 Intel I350 T4 NIC (4× 1 GBit/sec) I have lying around HBA: Broadcom SAS 9305-24i (PCIe 3.0 x8, SAS3224 chipset, 6× SFF-8643 for a total of 24 SAS/SATA drives over two backplanes), 6× breakout cables SFF-8643 to SFF-8087 Cache drives: 2× Samsung 990 Pro, 2 TB (M.2, PCIe 4.0 x4) Chassis: Inter-Tech IPC 4U-4724 (4U, 24× 2.5"/3.5" Hot-Swap, plus 2× internal 2.5"), plus rails for my 19" rack PSU: be quiet! Pure Power 850 W Fans: 3× Noctua NF-A12 120mm PWM, 2× Noctua NF-A8 80mm PWM CPU Cooler: Noctua NH-D12L (still have to check if the height fits the chassis) I might also add 2× 16/18/20 TB HDDs early on as new parity drives and add the two current 8 TB parity drives to the array for additional storage. Happy and grateful for all feedback/questions/discussion. Thanks!

Currently running a Dell PERC H310 and a Dell H200 (both PCIe 2.0 x8) in IT Mode on my current setup. Both allow for 8 drives, each I have a total of 7 (SATA drives) connected to each right now, which is the maximum possible in the case I use. I'm thinking about switching over to a case with 24 bays (plus 2x 2.5" internal drives), so I would either have to get another HBA (the board I'm looking at has 3x PCIe 4.0 x16 slots, so it would fit) or use an SAS expander. The question I'm asking myself is what is the best option for me here: 1.) H310 AND H200 AND another HBA; connect 8 drives each? 2.) H310 AND H200 AND an SAS expander; connect 16 drives to one HBA and 8 to the other? 3.) H310 OR H200 AND an SAS expander; connect all 24 drives to one HBA and ditch the other one? (or do I just aimlessly sacrifice bandwith here, if I have a second HBA on hand anyway) What SAS expander should I be looking into, especially if I were to run all 24 drives off a single Dell H200/H310? Drives currently are a mix of old and new 2.5" and 3.5" (all SATA3), ranging from 500 GB to 8 TB CPU would be a Ryzen APU, so integrated iGPU and no need for a video card to use up a slot.

You mean another PC to create the drive from?

Restarting this thread: I had to replace my flash drive again this weekend (the previous one I used showed read/write errors). I opted for a new, factory sealed SanDisk USB 2.0 drive this time around. There still seems to be some problem with the super.dat file/storage of disk slots: if I merely stop and restart the array, everything is file; disks keep their assignments and I can start the array without problems as soon as I change anything in the list of disks (right now, I'd like to replace disk5 as described here and set disk5 to "no device"), all disk assignments are lost; there is a corresponding entry in the log: Sep 26 08:49:53 Tower kernel: read_file: error 2 opening /boot/config/super.dat Sep 26 08:49:53 Tower kernel: md: could not read superblock from /boot/config/super.dat The super.dat file is fine up to this point, and can also be read and restored from backup. What I am trying to achieve is: replace disk5 by disabling the array, setting disk5 to be emulated by parity, insert a new disk, preclear the new disk using the Unassigned Devices Preclear script, then use the new disk in the disk5 slot repeat the whole procedure for disk3 Log attached, anything else I can try? Slowly running out of space and I have disks lying around to increase storage space by a total of 4.5 TB which I currently cannot use. darkrack-diagnostics-20220926-1006.zip

That's basically what I did to create the current flash drive a few days ago.

Seems I fixed the error, unplugged all SATA cables to the bay in question and reattached them. The error seems to be gone now, I copied the whole contents from the ddrescue-image of the original disk back over to the new disk and no more UDMA CRC errors. There still seems to be a problem with the super.dat file though - all drives lose assignments on a reboot (but no longer on a stop/start array action). There also is no new super.dat created in /boot - there was the first time I started off the new flash drive, but I still had the error about it in the syslog, deleted it and it doesn't get created now. Current diagnostics attached. darkrack-diagnostics-20220622-1925.zip

New diags attached, thanks darkrack-diagnostics-20220619-1146.zip

Update, starting to think there is some underlying issue with the server, either the drive bay, a cable or the LSI controller: First of all, the flash drive was damaged to some extent, which explained the super.dat issue. I could not reboot off of it, but was able to copy the config-folder onto another flash drive on my Windows workstation, boot off it, replace the license and set up the array. Parity is rebuilding now, BUT I get a ton of UDMA CRC errors (about 15,000 over the past 12 hours) for the new replacement drive in the old slot of disk6. I also popped the old disk6 (the one with all the read errors) into an external bay on my Widows workstation and cloned it in an Ubuntu VM (in Hyper-V) using ddrescue. Drive was cloned without issue in around 9 hours and without a single error, I mounted the image (in the VM) and all data seems to be there. Any suggestions in which order I should check components? Cable, bay, controller?

Presuming parity is invalid now anyway, could I just remove disk 6 (and try to get data off it on another system) shut the system down, fix the issue with the flash drive put in the new disk build a new config with the new disk in the slot of disk6 rebuild parity then go on to replace the other two disks and rebuild them from parity?