- Joined
- Jul 6, 2021
stickers should be disabled for everyone except HHH and @secret watcherTotal Sticker Death.
and every post should just get an Islamic Content rating by default
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
stickers should be disabled for everyone except HHH and @secret watcherTotal Sticker Death.
Ya cunt I was about to post that myself ya culture stealing bastard! Gonna come to your house and wipe my hairy bawsack all over your door handles.They may take our drives, but they'll never take our STIIIIICKERS!!!
ya fucking this . i've been in computer IT for 20+ years. unless your controller is corrupting the drive and killing them this shit just doesnt happen.How likely is it that 4 disks can break simultaneously?![]()
No checking Kiwifarms is like checking the morning paper but every now and thenChecking Kiwifarms is like checking the morning paper but every now and then the paper randomly catches fire.
Every WD drive I had died on me, tho with enough time to move everything.They're WD M.2 1.6TB enterprise drives
The controller might have started to identify as tranny and is now 41% itself.ya fucking this . i've been in computer IT for 20+ years. unless your controller is corrupting the drive and killing them this shit just doesnt happen.
I have the exact opposite experience. From time to time I decide to listen to people claiming WDs are the most reliable and Seagates are shit. So I replace the Seagate for a WD and it dies within days (4 times this has happened), or it plain out refuses to work at all (one occurrence). So I tuck my tail between my legs and go back to Seagate, which all work well beyond their supposed lifespan. I won't shit on WD tho, because it works for other people. But at this point I stopped trying. The universe has decided it's how it has to be and I won't fight itEvery WD drive I had died on me, tho with enough time to move everything.
Meanwhile every seagate drive I had completely shat the bed without warning including a fucking backup seagate HDD that died while copying stuff being recovered from another dead seagate drive.
Meanwhile I got 15-year old HGST drives that plain refuses to die, but HGST sold out to WD and doesn't exists anymore.
No idea which SSD brand is the most reliable right now.
It's not very comparable because WD's SSD business was actually acquired from SanDisk and has only been relevant in maybe the last 5 years since they basically ignored the market in its nascent state. HDDs are such a crapshoot it's unreal, everyone has their favorite brand to hate but Toshibas have been the most unreliable in my experience, which is interesting as they're well regarded by Backblaze.Meanwhile I got 15-year old HGST drives that plain refuse to die, but HGST sold out to WD and doesn't exists anymore.
SSDs really do appear to operate on black magic nowadays. The amount of batshit insane failure modes that keep cropping up lately really beggars belief and this brave new world of UEFI seems to have made everything unbelievably complicated. I've got a pair of 3.84 TB SN630s in one of my boxes and now I'm just hoping I don't get felted too.At best a firmware bug, at worse, the drives sudoku'd.
You sound like you’re from Reddit. I don’t like Reddit niggers.Made an account to clarify things. I'm the dude that helps Null with this stuff when he needs it. No, I don't monitor the server cause it's Null's. But maybe I'll setup some stuff for Null to monitor stuff including drive health.
The storage on the server use ZFS pools. The SATA SSD array (SNEED Pool) bypasses the RAID Controller and is entirely JBOD passthrough.
The 4 x NVMe drives are U.2 drives in the front and are in FEED ZFS Pool. The backplane handles SATA, SAS, and U.2. U.2 has it's own area for those drives and connects to the motherboard with a OCuLink cable to a JNVMe header.
The 4 x 1.6TB WD Ultrastar DC SN620 NVMe U.2 drives disappeared from the server last night. But before that, the kernel reported write errors to one of them.
There are a few reasons this could have happened, from most likely to less likely:
- BIOS/UEFI Firmware stopped communicating with the NVMe drives. This happened with a certain BIOS setting when it was initially setup
- The drives actually died from the workload. Unlikely considering these can handle 1.7 Drive Writes per day. But very feasible. These are 2nd hand enterprise drives
- The backplane/JNVMe headers exploded. Super unlikely
The drives are likely still alive, and the server's firmware probably took a shit.
We need to inspect the server's BIOS settings or possibly even update the firmware. Then we can determine if the drives are toast or useless.
There was no foul play at hand here. At best a firmware bug, at worse, the drives sudoku'd.
WD are far from the most reliable, all I was saying is that at least that WD drive gave me a warning instead of just assploding itself with my data on it like the seagate drives did several times.From time to time I decide to listen to people claiming WDs are the most reliable and Seagates are shit.
Never had or even seen a 3.5 Toshiba drive, only 2.5 be it from laptops or portable drives, but none failed on me. Frankly I wouldn't be surprised if that division has dropped the ball in terms of quality since the main company is not doing well. Or maybe they are pulling a seagate and doing shit drives on purpose so you'll have to buy a new one.Toshibas have been the most unreliable in my experience, which is interesting as they're well regarded by Backblaze.
https://kiwifarms.st/members/ (future readers, substitute in the link of choice if .st is ever Dong'd)I thought Chris had the highest reaction score from when a mod set his to like a billion as a goof? Was it undone?