alt text

All issues which began on the 12th of November 2017 have been resolved.

The affected services are back online. The reason for this outage was a physical defect of an HDD as well as a simultaneous failure of an SSD in our server HV01.

For the technical folks this is what the servers sata controller threw into the kernel log:

Nov 11 21:43:35 hv01-de-fs kernel: [7126302.696057] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Nov 11 21:43:35 hv01-de-fs kernel: [7126302.745078] ata4.00: failed command: SMART Nov 11 21:43:35 hv01-de-fs kernel: [7126302.769558] ata4.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 2 pio 512 in Nov 11 21:43:35 hv01-de-fs kernel: [7126302.769558] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Nov 11 21:43:35 hv01-de-fs kernel: [7126302.866348] ata4.00: status: { DRDY } Nov 11 21:43:35 hv01-de-fs kernel: [7126302.890274] ata4: hard resetting link Nov 11 21:43:37 hv01-de-fs kernel: [7126304.764062] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 11 21:43:37 hv01-de-fs kernel: [7126304.765199] ata4.00: configured for UDMA/133 Nov 11 21:43:37 hv01-de-fs kernel: [7126304.765218] ata4: EH complete Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060380] sd 3:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060382] sd 3:0:0:0: [sdb] tag#24 Sense Key : Illegal Request [current] Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060384] sd 3:0:0:0: [sdb] tag#24 Add. Sense: Unaligned write command Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060386] sd 3:0:0:0: [sdb] tag#24 CDB: Read(16) 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Nov 11 21:44:09 hv01-de-fs kernel: [7126335.060389] blk_update_request: I/O error, dev sdb, sector 0

this error has been thrown over and over again fatally crashing the controller in the end. We have resolved the issue with the help of Hetzner’s technicians which did replace the affected disks within a few hours. Great support as always!

Icon: “Cloud Synced by ✦ Shmidt Sergey ✦ from the Noun Project”

@Administrators @Global-Moderators @Greenhorn @Novus

First it was internal server errors, now its the remote host. [Solved]