Search results

I was able to borrow another Kingston A400 running firmware v. SBFKB1H5 from a coworker. I exchanged this for the drive running v.SA400S30009, reconfigured RAID 10, and reinstalled proxmox. After 72 hours of uptime, there have been no filesystem errors. Seems to have been a firmware problem.

Update: I pulled the array out of the R210 II and used the Kingston SSD manager (which unfortunately can only be run over a Windows client) to check for (1) firmware updates and (2) errors on each drive. They are at full health (according to Kingston, at least; if you have any better drive...

@dcsapak here are the relevant (and abridged, as the rsyslog error repeats for some time) journal logs: Mar 05 10:31:34 pve1a kernel: sd 0:1:0:0: [sda] tag#2404 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mar 05 10:31:34 pve1a kernel: sd 0:1:0:0: [sda] tag#2404 Sense Key : Not Ready...

Absolutely, give me an hour or so and I'll post the log outputs.

I am running proxmox on a Dell R210 II, which I recently upgraded to use four Kingston A400 SSDs running in RAID 10 using the H200 RAID controller. After this machine ran for a few hours, it encountered an error and fell back into a read-only root filesystem (I've seen some answers that suggest...