Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
i have so much problems with my (virtual) disks.
i see articles from virtual box
ext4 and kvm going error?
i need to set the Host IO ?
But i don't understand?
Is there a solution?
2 x
quad core super micro.
32GB
RAID5 6TB (4TB)
Buffer I/O error on device sdc1, logical block 65273728
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273729
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273730
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273731
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273732
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273733
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273734
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273735
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273736
lost page write due to I/O error on sdc1
Buffer I/O error on device sdc1, logical block 65273737
lost page write due to I/O error on sdc1
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
JBD2: Detected IO errors while flushing file data on sdc1-8
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.01: failed command: WRITE DMA EXT
ata2.01: cmd 35/00:00:3f:fc:cf/00:04:1f:00:00/f0 tag 0 dma 524288 out
res 40/00:01:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata2.01: status: { DRDY }
ata2: soft resetting link
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: READ DMA
ata1.01: cmd c8/00:08:c7:10:68/00:00:00:00:00/f4 tag 0 dma 4096 in
res 40/00:01:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata1.01: status: { DRDY }
ata1: soft resetting link
ata2.01: configured for MWDMA2
ata2.01: device reported invalid CHS sector 0
ata2: EH complete
ata1.00: configured for MWDMA2
ata1.01: configured for MWDMA2
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
sd 0:0:1:0: [sdb] Unhandled error code
sd 0:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
sd 0:0:1:0: [sdb] CDB: Read(10): 28 00 04 95 55 3f 00 01 00 00
ata2: lost interrupt (Status 0x50)
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
sd 1:0:1:0: [sdc] Unhandled error code
sd 1:0:1:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
sd 1:0:1:0: [sdc] CDB: Write(10): 2a 00 00 00 00 87 00 00 08 00
__ratelimit: 118 callbacks suppressed
Buffer I/O error on device sdc1, logical block 9
ata1.01: failed command: READ DMA EXT
ata1.01: cmd 25/00:00:67:e7:89/00:01:27:00:00/f0 tag 0 dma 131072 in
res 40/00:01:00:00:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata1.01: status: { DRDY }
ata1: soft resetting link
lost page write due to I/O error on sdc1
ata1.00: configured for MWDMA2
ata1.01: configured for MWDMA2
ata1.01: device reported invalid CHS sector 0