f3, fio etc.Yeah, that was epic.
Very good tips! Thanks so much! I think this is indeed a solid plan and i will go straight to researching on how exactly i need to accomplish all of this.That would work, but is not the best solution. Two things to consider:
Proxmox itself has a certain IO load (more when updates are running), which is very low compared to the load of VMs, but it is there (which is why I literally burn up cheap SSDs for this, they are good enough for this). If you only have VMs on one mirror, then they have the full performance for themselves. This is the weaker argument, but it explains the principle. The stronger argument is that you might want a second 512G cheap/medium. Then you can make two mirrors. The 2x512G <- on it Proxmox, 2x2T <- VMs.
This way you have it cleanly separated and if something breaks at some point during an update or operating error in Proxmox, then you don't have to restore everything at once or laboriously take it apart. You then just delete the 2x512G mirror, reinstall Proxmox and import the 2x2T again. This means you have distributed the IO load sensibly (and the endurance as well), a disk can fail in both mirrors, both are cleanly separated and if something really bad goes wrong, you only have to restore one ZFS pool from your backup (time saving).
So that would be my tip... get another 512G (always check the firmware there too), then install proxmox fresh and then set it up accordingly.
Of course, you can also use each disk individually as storage. This gives you more available storage overall, but then no redundancy. It's never enough...
Aboslutely I don't mind. However I never did this before but I can try. Is this purely to understand whether SSDs are legit/not deffective in some way or you just want to understand how S4610 performs in general?
It is always good practice (and especially when purchasing from an unknown second-hand source) to test-drive the medium you will be becoming to rely on in the future. It is better to discover now something isn't right with that medium, than later. Trust me! Initial testing probably won't cover eventual long-time endurance, but it will cover the basics. All professional system admins perform some form of testing before committing medium to production use. You may be running some home lab, but in light of the price you paid, I personally would not use those disks until I tested them.
I don't want to cause unnecessary caution, and smartctl data can be a mixed bunch (& usually unreliable) but I've never seen a disk that has 4 power cycles but no power on hours. New disks usually have some power on hours, this comes from the regular factory testing & setup. Possibly this disk was tested for under an hour (under 30 mins?) - IDK. Probably ignore this concern if the above testing I suggested goes through without a hitch.
Good to know! What tools would you recommend me to run? Is there a good guide to follow to perform these initial tests?
I posted above
f3 & fio, probably enough for your job. Search online on how to use.apt & on my current, fully updated Proxmox node they both exist (although you may have to install):f3/stable 8.0-2 amd64
test real flash memory capacity
fio/stable 3.33-3 amd64
flexible I/O tester
# See also:
fio-examples/stable 3.33-3 all
flexible I/O tester - example job filesThanks for sharing!
root@mylab:~# badblocks -b 4096 -c 65535 -wsv /dev/sdc > badblocks_jan7_2025.log
Checking for bad blocks in read-write mode
From block 0 to 468843605
Testing with pattern 0xaa: done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Pass completed, 0 bad blocks found. (0/0/0 errors)f3read /ssd_pool/ | tee f3read_log.txt
Data OK: 1.68 TB (3604108301 sectors)
Data LOST: 0.00 Byte (0 sectors)
Corrupted: 0.00 Byte (0 sectors)
Slightly changed: 0.00 Byte (0 sectors)
Overwritten: 0.00 Byte (0 sectors)
Average reading speed: 358.85 MB/sblkdiscard -f -v /dev/sd$ CAUTION THAT DESTROYS THE DATA ON IT and only takes some seconds I am probably overlooking something obvious but i can't figure out how to update the firmware on D3-S4610... I am following this as per your tip, so first thing I need to install Intel® Memory and Storage Tool CLI. I thought I'll run on my Ubuntu LXC since it's supported on it and I have it ready.
intelmas show -intelssdAh I see now! It does seem to be a bit combersome, but I guess FW updates on SSDs is not something very commonly done.
Solved. At the top of the thread, choose the Edit thread button, then from the (no prefix) dropdown choose Solved.