Chciałbym prosić o pomoc. Dzisiaj po restarcie mojego serwera dostałem takie komunikaty.
Kod: Zaznacz cały
May 7 19:07:01 espons kernel: [ 63.855529] ata4.00: failed command: READ DMA
May 7 19:07:01 espons kernel: [ 63.855829] ata4.00: cmd c8/00:c0:b0:0b:44/00:00:00:00:00/e9 tag 0 dma 98304 in
May 7 19:07:01 espons kernel: [ 63.855830] res 51/84:c0:b0:0b:44/84:00:12:00:00/e9 Emask 0x30 (host bus error)
May 7 19:07:01 espons kernel: [ 63.856637] ata4.00: status: { DRDY ERR }
May 7 19:07:01 espons kernel: [ 63.857122] ata4.00: error: { ICRC ABRT }
May 7 19:07:01 espons kernel: [ 63.857625] ata4: soft resetting link
May 7 19:07:01 espons kernel: [ 64.036917] ata4.00: configured for UDMA/33
May 7 19:07:01 espons kernel: [ 64.036932] ata4: EH complete
May 7 19:07:01 espons kernel: [ 64.631372] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
May 7 19:07:01 espons kernel: [ 64.631760] ata4.00: BMDMA stat 0x26
May 7 19:07:01 espons kernel: [ 64.632062] ata4.00: failed command: READ DMA
May 7 19:07:01 espons kernel: [ 64.632362] ata4.00: cmd c8/00:c0:b0:0b:44/00:00:00:00:00/e9 tag 0 dma 98304 in
May 7 19:07:01 espons kernel: [ 64.632364] res 51/84:c0:b0:0b:44/84:00:12:00:00/e9 Emask 0x30 (host bus error)
May 7 19:07:01 espons kernel: [ 64.633154] ata4.00: status: { DRDY ERR }
May 7 19:07:01 espons kernel: [ 64.633650] ata4.00: error: { ICRC ABRT }
May 7 19:07:01 espons kernel: [ 64.634149] ata4: soft resetting link
May 7 19:07:01 espons kernel: [ 64.812452] ata4.00: configured for UDMA/33
May 7 19:07:01 espons kernel: [ 64.812467] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
May 7 19:07:01 espons kernel: [ 64.812472] sd 3:0:0:0: [sdb] Sense Key : Aborted Command [current] [descriptor]
May 7 19:07:01 espons kernel: [ 64.812479] Descriptor sense data with sense descriptors (in hex):
May 7 19:07:01 espons kernel: [ 64.812482] 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
May 7 19:07:01 espons kernel: [ 64.812496] 09 44 0b b0
May 7 19:07:01 espons kernel: [ 64.812502] sd 3:0:0:0: [sdb] Add. Sense: Scsi parity error
May 7 19:07:01 espons kernel: [ 64.812510] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 09 44 0b b0 00 00 c0 00
May 7 19:07:01 espons kernel: [ 64.812523] end_request: I/O error, dev sdb, sector 155454384
May 7 19:07:01 espons kernel: [ 64.812957] Buffer I/O error on device sdb5, logical block 19431542
May 7 19:07:01 espons kernel: [ 64.813255] Buffer I/O error on device sdb5, logical block 19431543
May 7 19:07:01 espons kernel: [ 64.813550] Buffer I/O error on device sdb5, logical block 19431544
May 7 19:07:01 espons kernel: [ 64.813842] Buffer I/O error on device sdb5, logical block 19431545
May 7 19:07:01 espons kernel: [ 64.814263] Buffer I/O error on device sdb5, logical block 19431546
May 7 19:07:01 espons kernel: [ 64.814725] Buffer I/O error on device sdb5, logical block 19431547
May 7 19:07:01 espons kernel: [ 64.815183] Buffer I/O error on device sdb5, logical block 19431548
May 7 19:07:01 espons kernel: [ 64.815636] Buffer I/O error on device sdb5, logical block 19431549
May 7 19:07:01 espons kernel: [ 64.816091] Buffer I/O error on device sdb5, logical block 19431550
May 7 19:07:01 espons kernel: [ 64.816516] Buffer I/O error on device sdb5, logical block 19431551
Kod: Zaznacz cały
fdisk -l
Device Boot Start End Blocks Id System
/dev/sda1 * 1 4864 39061504 83 Linux
/dev/sda2 4864 121602 937698305 5 Extended
/dev/sda5 4864 4876 96256 82 Linux swap / Solaris
/dev/sda6 4876 121602 937601024 83 Linux
/etc/fstab
Kod: Zaznacz cały
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda1 during installation
UUID=4d29248f-724b-4895-b949-d2be31c20f3d / ext4 errors=remount-ro 0 1
# /home was on /dev/sda6 during installation
UUID=912fe33a-05f1-4c2a-8a67-f03475c29748 /home ext4 defaults,usrquota,grpquota 0 2
# /mnt/backup was on /dev/sdb5 during installation
UUID=4d063052-9ae6-4e16-9354-5f4acd04d08c /mnt/backup ext4 defaults 0 2
/dev/sda5 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
Czyli to pewnie problem z dyskiem na moje kopie zapasowe.
Jak mogę spróbować naprawić sda5?
