Провел эксперимент на своем тестовом SMG:
извлек SATA HDD на ходу и вернул его в ТОТ ЖЕ карман
при извлечении диска в dmesg
Код: Выделить всё
[867472.451072] ata1: SError: { 10B8B Dispar }
[867472.455283] ata1: hard resetting link
[867472.808676] ata1: SATA link down (SStatus 0 SControl F300)
[867477.808674] ata1: hard resetting link
[867478.158682] ata1: SATA link down (SStatus 0 SControl F300)
[867478.164298] ata1: limiting SATA link speed to 1.5 Gbps
[867483.158681] ata1: hard resetting link
[867483.508687] ata1: SATA link down (SStatus 0 SControl F310)
[867483.514298] ata1.00: disabled
[867483.517383] ata1: EH complete
[867483.520472] sd 0:0:0:0: rejecting I/O to offline device
[867483.525804] sd 0:0:0:0: [sda] killing request
[867483.530278] sd 0:0:0:0: rejecting I/O to offline device
[867483.535674] sd 0:0:0:0: [sda] Unhandled error code
[867483.540585] sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00
[867483.547062] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 34 18 00 19 00 00 08 00
[867483.554474] end_request: I/O error, dev sda, sector 873988121
[867483.560337] Buffer I/O error on device sda1, logical block 109248515
[867483.566808] lost page write due to I/O error on sda1
[867483.571950] ata1.00: detaching (SCSI 0:0:0:0)
[867483.578235] EXT2-fs (sda1): error: ext2_get_inode: unable to read inode block - inode=27312150, block=109248515
[867483.588507] EXT2-fs (sda1): previous I/O error to superblock detected
[867483.588514]
[867483.597336] EXT2-fs (sda1): previous I/O error to superblock detected
[867483.597342]
[867483.616379] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[867483.621824] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
[867483.628310] sd 0:0:0:0: [sda] Stopping disk
[867483.632680] sd 0:0:0:0: [sda] START_STOP FAILED
[867483.637476] sd 0:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
При возврате диска в ТОТ ЖЕ карман в dmesg
Код: Выделить всё
[867531.683863] ata1: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen
[867531.691402] ata1: edma_err_cause=00000010 pp_flags=00000000, dev connect
[867531.698216] ata1: SError: { PHYRdyChg DevExch }
[867531.702881] ata1: hard resetting link
[867534.228687] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[867534.268718] ata1.00: ATA-8: HGST HTS545050A7E680, GR2OA3N0, max UDMA/133
[867534.275539] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[867534.338714] ata1.00: configured for UDMA/133
[867534.343102] ata1: EH complete
[867534.346517] scsi 0:0:0:0: Direct-Access ATA HGST HTS545050A7 GR2O PQ: 0 ANSI: 5
[867534.359447] sd 0:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[867534.367058] sd 0:0:0:0: [sdb] 4096-byte physical blocks
[867534.372689] sd 0:0:0:0: [sdb] Write Protect is off
[867534.377588] sd 0:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[867534.382869] sd 0:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[867534.415593] sdb: sdb1
[867534.419803] sd 0:0:0:0: [sdb] Attached SCSI disk
[867534.601553] EXT2-fs (sdb1): warning: mounting unchecked fs, running e2fsck is recommended
То есть был sda стал sdb и это нормально для linux. После перезагрузки SMG Ваш hdd снова будет смонитрован как sda.
У Вас есть возможность выяснить проводились какие-либо манипуляции с Вашим HDD в SMG в момент появления проблемы?