I/O Error 700

Gorgone

Member
Feb 7, 2018
11
0
6
53
hi seit einiger zeit bekomme ich nun folgende meldungen für meinen neuen pool
Bash:
[243848.656296] sd 6:0:3:0: [sdg] tag#2785 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[243848.656301] sd 6:0:3:0: [sdg] tag#2785 CDB: Read(16) 88 00 00 00 00 03 0a b3 e7 30 00 00 00 08 00 00
[243848.656304] print_req_error: I/O error, dev sdg, sector 13064464176 flags 700
[243848.656334] zio pool=storage vdev=/dev/disk/by-id/ata-WDC_WD80PURZ-85YNPY0_R6G988ZY-part1 error=5 type=1 offset=6689004609536 size=4096 flags=180980
[243858.698200] sd 6:0:2:0: [sdf] tag#2793 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[243858.698205] sd 6:0:2:0: [sdf] tag#2793 CDB: Read(16) 88 00 00 00 00 03 0a b3 e7 30 00 00 00 08 00 00
[243858.698207] print_req_error: I/O error, dev sdf, sector 13064464176 flags 700
[243858.698238] zio pool=storage vdev=/dev/disk/by-id/ata-WDC_WD80PURZ-85YNPY0_R6G9BNYY-part1 error=5 type=1 offset=6689004609536 size=4096 flags=180980
[252476.260737] sd 6:0:3:0: [sdg] tag#2778 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[252476.260744] sd 6:0:3:0: [sdg] tag#2778 CDB: Read(16) 88 00 00 00 00 02 f6 7c 96 20 00 00 00 08 00 00
[252476.260748] print_req_error: I/O error, dev sdg, sector 12725294624 flags 700
[252476.260804] zio pool=storage vdev=/dev/disk/by-id/ata-WDC_WD80PURZ-85YNPY0_R6G988ZY-part1 error=5 type=1 offset=6515349798912 size=4096 flags=180880
[252486.289845] sd 6:0:2:0: [sdf] tag#2786 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[252486.289850] sd 6:0:2:0: [sdf] tag#2786 CDB: Read(16) 88 00 00 00 00 02 f6 7c 96 20 00 00 00 08 00 00
[252486.289853] print_req_error: I/O error, dev sdf, sector 12725294624 flags 700
[252486.289883] zio pool=storage vdev=/dev/disk/by-id/ata-WDC_WD80PURZ-85YNPY0_R6G9BNYY-part1 error=5 type=1 offset=6515349798912 size=4096 flags=180880
[252496.187214] sd 6:0:1:0: [sde] tag#2794 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK
[252496.187219] sd 6:0:1:0: [sde] tag#2794 CDB: Read(16) 88 00 00 00 00 03 6a b7 18 e8 00 00 00 08 00 00
[252496.187221] print_req_error: I/O error, dev sde, sector 14675286248 flags 700
[252496.187252] zio pool=storage vdev=/dev/disk/by-id/ata-WDC_WD80PURZ-85YNPY0_R6G9GNRY-part1 error=5 type=1 offset=7513745510400 size=4096 flags=180880
die platten sind nagel neu inclusive der log-ssd

die 4 Platten hängen an einem LSI SAS2008 im IT Mode
jeden tag bekomme ich nun
Code:
        NAME                                   STATE     READ WRITE CKSUM
        storage                                ONLINE       0     0     0
          raidz1-0                             ONLINE       7     0     0
            ata-WDC_WD80PURZ-85YNPY0_R6G988ZY  ONLINE       7     0     0
            ata-WDC_WD80PURZ-85YNPY0_R6G9BNYY  ONLINE       6     0     0
            ata-WDC_WD80PURZ-85YNPY0_R6G9GNRY  ONLINE       4     0     0
        logs
          sdd2                                 ONLINE       0     0     0


übersehe ich irgendwas ?
 
Dass neue HDDs Probleme machen kann passieren, dass es gerade alle sind ist weniger wahrscheinlich und das Problem wird wahrscheinlich irgendwo davor liegen.

Ich würde folgendes ausprobieren:
  • Firmware des HBAs aktualisieren
  • Anderen HBA Controller ausprobieren
  • Kabel zwischen HBA und HDDs wechseln
 
Code:
[    1.699459] mpt3sas version 27.101.00.00 loaded
[    1.699970] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (24590028 kB)
[    1.758730] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
[    1.758742] mpt2sas_cm0: MSI-X vectors supported: 1, no of cores: 4, max_msix_vectors: -1
[    1.758856] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 42
[    1.758858] mpt2sas_cm0: iomem(0x00000000fea40000), mapped(0x(____ptrval____)), size(65536)
[    1.758859] mpt2sas_cm0: ioport(0x000000000000e000), size(256)
[    1.816816] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
[    1.816820] mpt2sas_cm0: sending message unit reset !!
[    1.818516] mpt2sas_cm0: message unit reset: SUCCESS
[    1.859031] mpt2sas_cm0: Allocated physical memory: size(1687 kB)
[    1.859033] mpt2sas_cm0: Current Controller Queue Depth(3364),Max Controller Queue Depth(3432)
[    1.859034] mpt2sas_cm0: Scatter Gather Elements per IO(128)
[    1.906938] mpt2sas_cm0: overriding NVDATA EEDPTagMode setting
[    1.907371] mpt2sas_cm0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
[    1.907372] mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    1.914187] mpt2sas_cm0: sending port enable !!
[    3.499858] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x5000000080000000), phys(8)
[    9.628062] mpt2sas_cm0: port enable: SUCCESS
Code:
[    9.748702] scsi 4:0:0:0: Direct-Access     ATA      WDC WD80PURZ-85Y 0A80 PQ: 0 ANSI: 6
[    9.748711] scsi 4:0:0:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x0000000000000000)
[    9.748712] scsi 4:0:0:0: enclosure logical id (0x5000000080000000), slot(0)
[    9.748843] scsi 4:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   10.003986] scsi 4:0:1:0: Direct-Access     ATA      KINGSTON SA400S3 0102 PQ: 0 ANSI: 6
[   10.003995] scsi 4:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x0000000000000000)
[   10.003996] scsi 4:0:1:0: enclosure logical id (0x5000000080000000), slot(3)
[   10.004126] scsi 4:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   10.248092] scsi 4:0:2:0: Direct-Access     ATA      WDC WD80PURZ-85Y 0A80 PQ: 0 ANSI: 6
[   10.248100] scsi 4:0:2:0: SATA: handle(0x000a), sas_addr(0x4433221102000000), phy(2), device_name(0x0000000000000000)
[   10.248102] scsi 4:0:2:0: enclosure logical id (0x5000000080000000), slot(1)
[   10.248198] scsi 4:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   10.498128] scsi 4:0:3:0: Direct-Access     ATA      WDC WD80PURZ-85Y 0A80 PQ: 0 ANSI: 6
[   10.498137] scsi 4:0:3:0: SATA: handle(0x000b), sas_addr(0x4433221101000000), phy(1), device_name(0x0000000000000000)
[   10.498139] scsi 4:0:3:0: enclosure logical id (0x5000000080000000), slot(2)
[   10.498256] scsi 4:0:3:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
Neuste Firmware -> check
Anderer HBA -> check
Neuer Kabelsatz -check

-bringt alles nichts wenn die platten aus dem sleep kommen mucken die rum
 

Attachments

Last edited:
Hatte mal ein ähnliches Problem mit meiner neuen Hardware. Damals waren alle SAS Kabel defekt.
 
naja wenn ich sleep deaktiviere läuft es ja fehlerfrei nur ist das für ne nas die 90% nicht HOT ist
da muss irgendwie der sheduler nicht richtig getimed sein sonst kämen die fehler ja nicht so schnell
die zugriffe laufen ja auch problemlos nachdem die platten hochgedreht sind

so lasse ich die ruhen mit systemd da wo jetzt 0 steht ist normalerweise der sleep timer also 20 minuten zb
 

Attachments

  • shot.png
    shot.png
    18.2 KB · Views: 8

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!