다음 오류가 발생합니다.
[root@mediaserv ~]# mount /dev/mapper/media1 /media
mount: /media: can't read superblock on /dev/mapper/media1.
이것은 Fedora 33입니다. 저는 Adaptec 7805Q RAID 컨트롤러에서 실행되는 8x 8TB WD Red 드라이브의 RAID5를 가지고 있습니다. 이것은 /dev/sdc입니다. XFS 파일 시스템을 사용하는 LUKSv2로 암호화된 GPT 파티션 /dev/sdc1이 하나 있습니다.
[root@mediaserv ~]# lsblk /dev/sdc
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdc 8:32 1 50.9T 0 disk
└─sdc1 8:33 1 50.9T 0 part
└─media1 253:0 0 50.9T 0 crypt
[root@mediaserv ~]#
RAID가 성능 저하 모드로 종료되었습니다. 아마도 새 팬을 설치할 때 첫 번째 드라이브에 케이블이 부딪혔을 것입니다. 어쨌든, 부팅한 후 몇 시간 동안 성능 저하 모드로 실행한 후 발견했습니다. 시스템을 종료하고 복구 이미지에서 단일 사용자 모드로 부팅한 다음 이를 실행하여 어레이를 재구축했습니다. 약 14시간이 걸렸습니다.
백업으로 부팅하면 파티션의 LUK 비밀번호를 묻는 메시지가 표시되지만 그대로 유지됩니다. 백그라운드에서 뭔가 수정되고 있는지 확실하지 않은 상태에서 약 8시간 동안 실행했습니다.
나는 다시 구조에서 부팅했습니다. 파일 시스템을 주석 처리했으며 /etc/crypttab마운트 된 파일 시스템 /etc/fstab없이 시스템에 로그인할 수 있습니다 /media.
나는 성공적으로 달릴 수 있었습니다 cryptsetup luksOpen /dev/sdc1 media1. 파티션이 오류 없이 해독되는 것 같습니다.
위의 mount 명령을 실행하면 다음이 표시됩니다 /var/log/messages.
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#340 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#340 Sense Key : Hardware Error [current]
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#340 Add. Sense: Internal target failure
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#340 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 10:23:00 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#341 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#341 Sense Key : Hardware Error [current]
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#341 Add. Sense: Internal target failure
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#341 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 10:23:00 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 5 10:23:00 mediaserv kernel: Buffer I/O error on dev dm-0, logical block 0, async page read
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#342 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#342 Sense Key : Hardware Error [current]
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#342 Add. Sense: Internal target failure
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#342 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 10:23:00 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 5 10:23:00 mediaserv kernel: EXT4-fs (dm-0): unable to read superblock
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#343 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#343 Sense Key : Hardware Error [current]
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#343 Add. Sense: Internal target failure
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#343 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 10:23:00 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 5 10:23:00 mediaserv kernel: EXT4-fs (dm-0): unable to read superblock
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#344 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#344 Sense Key : Hardware Error [current]
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#344 Add. Sense: Internal target failure
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#344 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 10:23:00 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 5 10:23:00 mediaserv kernel: EXT4-fs (dm-0): unable to read superblock
Jan 5 10:23:00 mediaserv kernel: ISOFS: unsupported/invalid hardware sector size 4096
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#345 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#345 Sense Key : Hardware Error [current]
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#345 Add. Sense: Internal target failure
Jan 5 10:23:00 mediaserv kernel: sd 12:0:0:0: [sdc] tag#345 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 10:23:00 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 5 10:23:00 mediaserv kernel: FAT-fs (dm-0): unable to read boot sector
실행을 시도했지만 아직 옵션 xfs_repair을 시도하지 않았습니다 -L.
[root@mediaserv ~]# xfs_repair /dev/mapper/media1
Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval -1
fatal error -- Remote I/O error
다음에 어디로 가야할지 확신할 수 없고, 잘못된 명령을 실행하여 더 많은 피해를 입힐까 봐 걱정됩니다. 어떤 도움이라도 감사하겠습니다.
감사해요!
-마이크
편집하다:
좀 더 조사한 결과 슈퍼블록 문제는 아닌 것 같습니다. 해당 오류는 mount 명령에서 파일 시스템 유형을 지정하지 않았기 때문에 발생했다고 생각합니다. 좀 더 적절하게 다시 실행하면 다음과 같은 결과를 얻습니다.
[root@mediaserv ~]# mount -t xfs /dev/mapper/media1 /media
mount: /media: mount(2) system call failed: Remote I/O error.
내 항목에 다음이 포함됩니다 /var/log/messages.
Jan 5 12:15:43 mediaserv kernel: sd 12:0:0:0: [sdc] tag#838 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Jan 5 12:15:43 mediaserv kernel: sd 12:0:0:0: [sdc] tag#838 Sense Key : Hardware Error [current]
Jan 5 12:15:43 mediaserv kernel: sd 12:0:0:0: [sdc] tag#838 Add. Sense: Internal target failure
Jan 5 12:15:43 mediaserv kernel: sd 12:0:0:0: [sdc] tag#838 CDB: Read(16) 88 00 00 00 00 00 00 00 11 00 00 00 00 01 00 00
Jan 5 12:15:43 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 34816 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0
Jan 5 12:15:43 mediaserv kernel: XFS (dm-0): SB validate failed with error -121.
나는 그것을 어떻게 해석해야할지 모르겠습니다. 34816 섹터부터 잘못된 데이터가 시작됩니까?
편집 #2:
RAID 어레이 상태에 관해. 앞서 언급한 대로 드라이브가 손실되어 성능 저하 모드로 들어갔습니다. RAID를 재구축하는 동안 서비스를 중단하고 단일 사용자 모드로 전환했습니다. 다음은 재구축 후 Adaptec 도구의 출력입니다(덜 장황하게 정리했습니다).
arcconf getconfig 1
----------------------------------------------------------------------
Controller information
----------------------------------------------------------------------
Controller Status : Optimal
Controller Mode : RAID (Expose RAW)
Controller Model : Adaptec ASR7805Q
Performance Mode : Big Block Bypass
--------------------------------------------------------
RAID Properties
--------------------------------------------------------
Logical devices/Failed/Degraded : 1/0/0
Copyback : Disabled
Automatic Failover : Enabled
Background consistency check : Disabled
Background consistency check period : 0
----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical Device number 0
Logical Device name : media
Block Size of member drives : 4K Bytes
RAID level : 5
Status of Logical Device : Optimal
Size : 53387257 MB
Parity space : 7626751 MB
Stripe-unit size : 1024 KB
Interface Type : Serial ATA
Device Type : HDD
Read-cache setting : Enabled
Read-cache status : On
Write-cache setting : On when protected by battery/ZMM
Write-cache status : On
maxCache read cache setting : Enabled
maxCache read cache status : Off
maxCache write cache setting : Disabled
maxCache write cache status : Off
Partitioned : Yes
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : Yes
Power settings : Disabled
----------------------------------------------------------------------
Physical Device information
----------------------------------------------------------------------
Device #0
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #1
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #2
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #3
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #4
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #5
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #6
Device is a Hard drive
State : Online
Block Size : 4K Bytes
Device #7
Device is a Hard drive
State : Online
Block Size : 4K Bytes
다음은 어레이에 있는 각 드라이브의 SMART 상태입니다.
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,0" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,1" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,2" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,3" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,4" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,5" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,6" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
[root@mediaserv ~]# smartctl -a -d "aacraid,0,0,7" /dev/sdc | grep health
SMART overall-health self-assessment test result: PASSED
그러나 몇 시간 전에 로그를 뒤져보니 다음과 같은 내용이 발견되었습니다.
Jan 4 08:25:25 mediaserv kernel: sd 12:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=9s
Jan 4 08:25:25 mediaserv kernel: sd 12:0:0:0: [sdc] tag#0 Sense Key : Hardware Error [current]
Jan 4 08:25:25 mediaserv kernel: sd 12:0:0:0: [sdc] tag#0 Add. Sense: Internal target failure
Jan 4 08:25:25 mediaserv kernel: sd 12:0:0:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 01 60 2f 5c bf 00 00 00 20 00 00
Jan 4 08:25:25 mediaserv kernel: blk_update_request: critical target error, dev sdc, sector 47269471736 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0
위의 5개 항목은 여전히 로그에 계속 남아 있으며 다음 항목은 동시에 시스템에서 파일 시스템을 손실합니다.
Jan 4 08:26:32 mediaserv kernel: aacraid: Host adapter abort request.#012aacraid: Outstanding commands on (12,0,0,0):
Jan 4 08:26:32 mediaserv kernel: aacraid: Host adapter abort request.#012aacraid: Outstanding commands on (12,0,0,0):
Jan 4 08:26:32 mediaserv kernel: aacraid: Host adapter abort request.#012aacraid: Outstanding commands on (12,0,0,0):
Jan 4 08:26:55 mediaserv kernel: aacraid: Host adapter abort request.#012aacraid: Outstanding commands on (12,0,0,0):
Jan 4 08:26:55 mediaserv kernel: aacraid: Host bus reset request. SCSI hang ?
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: outstanding cmd: midlevel-0
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: outstanding cmd: lowlevel-0
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: outstanding cmd: error handler-0
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: outstanding cmd: firmware-56
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: outstanding cmd: kernel-0
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: Controller reset type is 3
Jan 4 08:26:55 mediaserv kernel: aacraid 0000:02:00.0: Issuing IOP reset
Jan 4 08:27:30 mediaserv kernel: aacraid 0000:02:00.0: IOP reset succeeded
Jan 4 08:27:30 mediaserv kernel: aacraid: Comm Interface type2 enabled
Jan 4 08:27:56 mediaserv kernel: aacraid 0000:02:00.0: Scheduling bus rescan
흥미로운 점은 어레이가 성능 저하 모드로 전환된 후 10시간 15분 후에 위와 같은 상황이 발생했다는 것입니다. 따라서 어레이 문제와 xfs 파일 시스템 문제는 몇 시간 간격으로 발생했습니다. 지금은 어레이와 드라이브가 정상이라고 보고하지만아직위의 "FAILED Result" 블록을 수신합니다.