Perguntas[hard-disk](unix)

Ouvi dizer que o RAID 1+0 é mais dependente de falhas do que o RAID 0+1, porque é mais provável que uma falha na unidade secundária cause perda de dados no RAID 0+1 do que no RAID 1+0.

Na imagem acima, se o “Disco 1” falhar, quais outras falhas de disco causarão perda de dados? O que li parece indicar que a perda de qualquer unidade no "Grupo 2" causará perda de dados, mas o raciocínio por trás disso não está claro para mim. Se perdermos o “Disco 5”, por que isso causaria perda de dados? Parece-me que há informações suficientes para recuperar o estado completo dos dados - combinar "Disco 4" + "Disco 2" + "Disco 3", por exemplo, deve ter todas as informações necessárias para continuar funcionando corretamente sem dados perda.

Nesse caso, por que a perda do “Disco 1” e do “Disco 5” causaria perda de dados?

Desde já, obrigado!

Recebi um aviso devido ao FAILED!estado da verificação SmartCTL.

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- NVM subsystem reliability has been degraded

Colega disse que isso é para monitoramento incorreto da unidade e nada de ruim não aconteceria.

Mas isso não parece ser assim.

A unidade precisa ser substituída?

SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x04
Temperature: 36 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 100%
Data Units Read: 1,688,838,473 [864 TB]
Data Units Written: 1,293,261,847 [662 TB]
Host Read Commands: 5,457,149,587
Host Write Commands: 3,494,810,022
Controller Busy Time: 62,331
Power Cycles: 30
Power On Hours: 19,491
Unsafe Shutdowns: 15
Media and Data Integrity Errors: 0
Error Information Log Entries: 96
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Temperature Sensor 1: 36 Celsius
Temperature Sensor 2: 48 Celsius

O Percentage Used: 100%campo significa que todos os recursos de disco disponíveis (a garantia de estimativa de uso sem problemas) estão esgotados e há necessidade de substituir o disco?

Todos os HDDs modernos são de " Formato Avançado ", por exemplo, por padrão, eles relatam um tamanho de setor lógico/físico de 512/4096.

Por padrão, a maioria das ferramentas de formatação do Linux usam um tamanho de bloco de 4096 bytes (pelo menos esse é o padrão no Debian/EXT4).

Até hoje, pensei que isso estava meio otimizado: Linux/EXT4 envia pedaços de dados 4K para o HDD, que pode lidar com eles de maneira ideal, mesmo que o tamanho do setor lógico seja 512K.

Mas hoje li este post bastante recente (2021) . O cara fez alguns benchmarks de HDD, para verificar se mudar o tamanho do setor lógico de seu HDD de 512e para 4Kn proporcionaria melhores desempenhos. Sua conclusão:

Lembre-se: minha teoria era que o sistema de arquivos usa blocos de 4k e tudo está devidamente alinhado, portanto não deve haver uma diferença significativa.

Isso se sustenta? Bem não. De jeito nenhum. (...) Usando blocos de 4kb… há uma diferença muito grande aqui. Este é um benchmarking de thread único, mas há consistentemente uma grande vantagem indo para o setor de 4k aqui em transferências de blocos de 4kb. (...)

Conclusões: Use Setores 4k!
No que me diz respeito, as conclusões aqui são bastante claras. Se você possui um sistema operacional moderno que pode lidar com setores de 4k e suas unidades suportam a operação como setores de 512 bytes ou 4k, converta suas unidades em setores nativos de 4k antes de fazer qualquer outra coisa. Então siga seu caminho e deixe o sistema operacional cuidar disso.

Basicamente, sua conclusão foi que houve uma grande melhoria de desempenho ao mudar o tamanho do setor lógico do HDD para 4Kn, em comparação com o 512e pronto para uso:

Agora, uma coisa importante a ser observada: esse benchmark específico era de thread único. Ele também fez um benchmark de 4 threads, que não mostrou diferenças significativas entre 512e e 4Kn.

Assim, minhas perguntas:

• Sua conclusão é válida apenas se você tiver processos de thread único que leem/gravam na unidade. O Linux possui esses processos de thread único?
• E assim, você recomendaria definir o tamanho do setor lógico de um HDD para 4Kn?

No momento, estou lidando com um HDD, no qual não consigo gravar, mas não entendo o motivo. Aqui está o que eu observei sobre o problema:

1. A execução de um benchmark somente leitura funciona bem; velocidade de leitura e tempo de acesso parecem bons

2. A execução de um benchmark de gravação não produz resultados e parece "travar"

3. Qualquer aplicativo ou processo que tente gravar no disco trava até ser encerrado, incluindo o gparted ao tentar formatar o disco. Em algum momento durante a tentativa de formatação, foi gerado "Erro de entrada/saída durante a gravação em /dev/sda". A única outra mensagem de erro discernível que vi é algo parecido com Buffer I/O logical block <some_number> lost during async writeo que às vezes é exibido durante o desligamento.

4. A saída Smartctl do autoteste parece boa, levando-me a acreditar que pode não ser um problema físico

5. O comando fdisk -lretorna a seguinte saída para o disco afetado:

Device         Start        End    Sectors   Size Type
/dev/sda1         63     532542     532480   260M EFI System
/dev/sda2     532543  498340557  497808015 237,4G Microsoft basic data
/dev/sda5  498341888 1953519615 1455177728 693,9G Linux filesystem

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.


GPT PMBR size mismatch (4100491 != 15701758) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.

6. Eu ouvi alguns sons semelhantes a arranhões vindos do disco há um tempo atrás.

Portanto, especialmente devido ao ponto 6, estou assumindo que há algo fisicamente quebrado no HDD, mas, novamente, espero que smartctl indique isso. Infelizmente, não tenho muita experiência com esses tipos de problemas, portanto, se alguém tiver uma ideia sobre quaisquer etapas de diagnóstico adicionais que eu possa executar para confirmar se o disco está realmente quebrado, eu agradeceria.

Editar: conforme solicitado, estou adicionando aqui a saída \dmesgao executar um benchmark de gravação. O benchmark em si está travado na primeira amostra, como você pode ver abaixo.

[ 1090.321553] ata5.00: exception Emask 0x0 SAct 0x9801ffff SErr 0x50000 action 0x6 frozen
[ 1090.321562] ata5: SError: { PHYRdyChg CommWake }
[ 1090.321569] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321580] ata5.00: cmd 61/d0:00:40:0d:00/02:00:00:00:00/40 tag 0 ncq dma 368640 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321584] ata5.00: status: { DRDY }
[ 1090.321588] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321598] ata5.00: cmd 61/40:08:10:10:00/05:00:00:00:00/40 tag 1 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321602] ata5.00: status: { DRDY }
[ 1090.321605] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321614] ata5.00: cmd 61/c8:10:50:15:00/02:00:00:00:00/40 tag 2 ncq dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321618] ata5.00: status: { DRDY }
[ 1090.321622] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321630] ata5.00: cmd 61/48:18:18:18:00/05:00:00:00:00/40 tag 3 ncq dma 692224 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321634] ata5.00: status: { DRDY }
[ 1090.321638] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321646] ata5.00: cmd 61/c0:20:60:1d:00/02:00:00:00:00/40 tag 4 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321650] ata5.00: status: { DRDY }
[ 1090.321654] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321662] ata5.00: cmd 61/48:28:20:20:00/05:00:00:00:00/40 tag 5 ncq dma 692224 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321666] ata5.00: status: { DRDY }
[ 1090.321670] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321678] ata5.00: cmd 61/c0:30:68:25:00/02:00:00:00:00/40 tag 6 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321682] ata5.00: status: { DRDY }
[ 1090.321686] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321694] ata5.00: cmd 61/40:38:28:28:00/05:00:00:00:00/40 tag 7 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321698] ata5.00: status: { DRDY }
[ 1090.321701] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321710] ata5.00: cmd 61/c0:40:68:2d:00/02:00:00:00:00/40 tag 8 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321714] ata5.00: status: { DRDY }
[ 1090.321717] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321726] ata5.00: cmd 61/40:48:28:30:00/05:00:00:00:00/40 tag 9 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321730] ata5.00: status: { DRDY }
[ 1090.321733] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321742] ata5.00: cmd 61/c8:50:68:35:00/02:00:00:00:00/40 tag 10 ncq dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321746] ata5.00: status: { DRDY }
[ 1090.321749] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321758] ata5.00: cmd 61/40:58:30:38:00/05:00:00:00:00/40 tag 11 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321762] ata5.00: status: { DRDY }
[ 1090.321765] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321774] ata5.00: cmd 61/c0:60:70:3d:00/02:00:00:00:00/40 tag 12 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321778] ata5.00: status: { DRDY }
[ 1090.321781] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321790] ata5.00: cmd 61/40:68:30:40:00/05:00:00:00:00/40 tag 13 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321794] ata5.00: status: { DRDY }
[ 1090.321797] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321806] ata5.00: cmd 61/c8:70:70:45:00/02:00:00:00:00/40 tag 14 ncq dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321810] ata5.00: status: { DRDY }
[ 1090.321813] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321822] ata5.00: cmd 61/48:78:38:48:00/05:00:00:00:00/40 tag 15 ncq dma 692224 out
                        res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321826] ata5.00: status: { DRDY }
[ 1090.321829] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321838] ata5.00: cmd 61/80:80:80:4d:00/02:00:00:00:00/40 tag 16 ncq dma 327680 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321841] ata5.00: status: { DRDY }
[ 1090.321845] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321854] ata5.00: cmd 61/40:d8:00:00:00/05:00:00:00:00/40 tag 27 ncq dma 688128 out
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321858] ata5.00: status: { DRDY }
[ 1090.321861] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321870] ata5.00: cmd 61/c0:e0:40:05:00/02:00:00:00:00/40 tag 28 ncq dma 360448 out
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321874] ata5.00: status: { DRDY }
[ 1090.321877] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1090.321886] ata5.00: cmd 61/40:f8:00:08:00/05:00:00:00:00/40 tag 31 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1090.321890] ata5.00: status: { DRDY }
[ 1090.321896] ata5: hard resetting link
[ 1090.636674] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1090.646800] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1090.646806] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 1090.646811] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 1090.651025] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1090.651032] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 1090.651036] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 1090.652207] ata5.00: configured for UDMA/100
[ 1090.652755] ata5: EH complete
[ 1121.030386] ata5.00: exception Emask 0x0 SAct 0xfcfffc SErr 0x40000 action 0x6 frozen
[ 1121.030399] ata5: SError: { CommWake }
[ 1121.030408] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030425] ata5.00: cmd 61/40:10:00:08:00/05:00:00:00:00/40 tag 2 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030430] ata5.00: status: { DRDY }
[ 1121.030436] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030451] ata5.00: cmd 61/c0:18:40:05:00/02:00:00:00:00/40 tag 3 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030457] ata5.00: status: { DRDY }
[ 1121.030462] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030471] ata5.00: cmd 61/40:20:00:00:00/05:00:00:00:00/40 tag 4 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030475] ata5.00: status: { DRDY }
[ 1121.030479] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030488] ata5.00: cmd 61/80:28:80:4d:00/02:00:00:00:00/40 tag 5 ncq dma 327680 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030491] ata5.00: status: { DRDY }
[ 1121.030495] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030504] ata5.00: cmd 61/48:30:38:48:00/05:00:00:00:00/40 tag 6 ncq dma 692224 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030507] ata5.00: status: { DRDY }
[ 1121.030511] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030520] ata5.00: cmd 61/c8:38:70:45:00/02:00:00:00:00/40 tag 7 ncq dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030523] ata5.00: status: { DRDY }
[ 1121.030527] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030535] ata5.00: cmd 61/40:40:30:40:00/05:00:00:00:00/40 tag 8 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030539] ata5.00: status: { DRDY }
[ 1121.030543] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030551] ata5.00: cmd 61/c0:48:70:3d:00/02:00:00:00:00/40 tag 9 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030555] ata5.00: status: { DRDY }
[ 1121.030558] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030568] ata5.00: cmd 61/40:50:30:38:00/05:00:00:00:00/40 tag 10 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030571] ata5.00: status: { DRDY }
[ 1121.030575] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030584] ata5.00: cmd 61/c8:58:68:35:00/02:00:00:00:00/40 tag 11 ncq dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030587] ata5.00: status: { DRDY }
[ 1121.030591] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030600] ata5.00: cmd 61/40:60:28:30:00/05:00:00:00:00/40 tag 12 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030603] ata5.00: status: { DRDY }
[ 1121.030607] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030616] ata5.00: cmd 61/c0:68:68:2d:00/02:00:00:00:00/40 tag 13 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030619] ata5.00: status: { DRDY }
[ 1121.030623] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030632] ata5.00: cmd 61/40:70:28:28:00/05:00:00:00:00/40 tag 14 ncq dma 688128 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030635] ata5.00: status: { DRDY }
[ 1121.030639] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030648] ata5.00: cmd 61/c0:78:68:25:00/02:00:00:00:00/40 tag 15 ncq dma 360448 out
                        res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030651] ata5.00: status: { DRDY }
[ 1121.030655] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030664] ata5.00: cmd 61/48:90:20:20:00/05:00:00:00:00/40 tag 18 ncq dma 692224 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030667] ata5.00: status: { DRDY }
[ 1121.030671] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030680] ata5.00: cmd 61/c0:98:60:1d:00/02:00:00:00:00/40 tag 19 ncq dma 360448 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030683] ata5.00: status: { DRDY }
[ 1121.030687] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030696] ata5.00: cmd 61/48:a0:18:18:00/05:00:00:00:00/40 tag 20 ncq dma 692224 out
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030699] ata5.00: status: { DRDY }
[ 1121.030703] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030712] ata5.00: cmd 61/c8:a8:50:15:00/02:00:00:00:00/40 tag 21 ncq dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030715] ata5.00: status: { DRDY }
[ 1121.030719] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030728] ata5.00: cmd 61/40:b0:10:10:00/05:00:00:00:00/40 tag 22 ncq dma 688128 out
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030731] ata5.00: status: { DRDY }
[ 1121.030735] ata5.00: failed command: WRITE FPDMA QUEUED
[ 1121.030743] ata5.00: cmd 61/d0:b8:40:0d:00/02:00:00:00:00/40 tag 23 ncq dma 368640 out
                        res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1121.030747] ata5.00: status: { DRDY }
[ 1121.030753] ata5: hard resetting link
[ 1121.345937] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1121.358873] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1121.358880] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 1121.358884] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 1121.363203] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1121.363209] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 1121.363214] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 1121.364412] ata5.00: configured for UDMA/100
[ 1121.364968] ata5: EH complete
[ 1209.075840] INFO: task gnome-disks:8463 blocked for more than 120 seconds.
[ 1209.075852]       Tainted: P           OE     5.4.0-153-generic #170-Ubuntu
[ 1209.075854] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1209.075858] gnome-disks     D    0  8463   2344 0x00004000
[ 1209.075863] Call Trace:
[ 1209.075878]  __schedule+0x2e3/0x740
[ 1209.075885]  schedule+0x42/0xb0
[ 1209.075891]  io_schedule+0x16/0x40
[ 1209.075899]  __blkdev_direct_IO+0x353/0x450
[ 1209.075906]  ? check_preempt_curr+0x4e/0x90
[ 1209.075911]  blkdev_direct_IO+0x4d/0x70
[ 1209.075919]  generic_file_direct_write+0x9c/0x170
[ 1209.075926]  __generic_file_write_iter+0xbc/0x1d0
[ 1209.075931]  blkdev_write_iter+0xb8/0x160
[ 1209.075940]  new_sync_write+0x125/0x1c0
[ 1209.075949]  __vfs_write+0x29/0x40
[ 1209.075952]  vfs_write+0xb9/0x1a0
[ 1209.075957]  ksys_write+0x67/0xe0
[ 1209.075962]  __x64_sys_write+0x1a/0x20
[ 1209.075975]  do_syscall_64+0x57/0x190
[ 1209.075980]  entry_SYSCALL_64_after_hwframe+0x5c/0xc1
[ 1209.075984] RIP: 0033:0x7efc3d2f132f
[ 1209.075992] Code: Bad RIP value.
[ 1209.075995] RSP: 002b:00007efc32dc59a0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
[ 1209.075999] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007efc3d2f132f
[ 1209.076002] RDX: 0000000000a00000 RSI: 00007efc313c4000 RDI: 000000000000000b
[ 1209.076004] RBP: 000055a1a5d5d010 R08: 0000000000000000 R09: 0000000000000423
[ 1209.076005] R10: 00007ffdf2cc2090 R11: 0000000000000293 R12: 000000000000000b
[ 1209.076007] R13: 00007efc313c4000 R14: 0000000000001000 R15: 00007efc32dc5a50
[ 1213.183836] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x40000 action 0x6 frozen
[ 1213.183845] ata5: SError: { CommWake }
[ 1213.183852] ata5.00: failed command: WRITE DMA EXT
[ 1213.183865] ata5.00: cmd 35/00:c8:68:35:00/00:02:00:00:00/e0 tag 17 dma 364544 out
                        res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1213.183869] ata5.00: status: { DRDY }
[ 1213.183876] ata5: hard resetting link
[ 1213.498788] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1213.501523] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1213.501530] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 1213.501534] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 1213.505634] ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
[ 1213.505640] ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[ 1213.505645] ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
[ 1213.506879] ata5.00: configured for UDMA/100
[ 1213.507257] ata5: EH complete

Benchmark travado na primeira amostra:

Tenho recebido as seguintes mensagens de erro todos os dias há vários meses e não sei como parar de receber essas mensagens.

CurrentPendingSector

This message was generated by the smartd daemon running on:

   host name:  myhost
   DNS domain: [Empty]

The following warning/error was logged by the smartd daemon:

Device: /dev/sda [SAT], 6 Currently unreadable (pending) sectors

Device info:
KingFast, S/N:03112222C0002, FW:U0803A0, 256 GB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
The original message about this issue was sent at Fri Feb  3 19:41:29 2023 PST
Another message will be sent in 24 hours if the problem persists.

OfflineUncorrectableSector

This message was generated by the smartd daemon running on:

   host name:  myhost
   DNS domain: [Empty]

The following warning/error was logged by the smartd daemon:

Device: /dev/sda [SAT], 3 Offline uncorrectable sectors

Device info:
KingFast, S/N:03112222C0002, FW:U0803A0, 256 GB

For details see host's SYSLOG.

You can also use the smartctl utility for further investigation.
The original message about this issue was sent at Fri Feb  3 19:41:29 2023 PST
Another message will be sent in 24 hours if the problem persists.

smartctl -a /dev/sda

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.19.0-46-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     KingFast
Serial Number:    03112222C0002
Firmware Version: U0803A0
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jul  8 15:44:59 2023 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                    was completed without error.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:        (  120) seconds.
Offline data collection
capabilities:            (0x11) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    No Selective Self-test supported.
SMART capabilities:            (0x0002) Does not save SMART data before
                    entering power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:    (   2) minutes.
Extended self-test routine
recommended polling time:    (  10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       6
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       3335
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       440
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       3
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       86
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       26
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       79004
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       481
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       6
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       114
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       5050
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       98
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       6
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       88
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       35
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       3
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       3
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       86
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       168900
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       815543
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       191939

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      3329         -
# 2  Short offline       Completed without error       00%      3325         -
# 3  Short offline       Completed without error       00%      3321         -
# 4  Short offline       Completed without error       00%      3313         -
# 5  Short offline       Completed without error       00%      3309         -
# 6  Short offline       Completed without error       00%      3306         -
# 7  Extended offline    Completed without error       00%      3250         -
# 8  Extended offline    Completed without error       00%      3232         -
# 9  Extended offline    Completed without error       00%      3229         -
#10  Extended offline    Completed without error       00%       976         -
#11  Extended offline    Completed without error       00%       968         -

Selective Self-tests/Logging not supported

Eu tentei ignorar os erros 197e com198/etc/smartd.conf

/dev/sda -d removable -n standby -H -l error -l selftest -f -t -I 197 -I 198 -s (S/../.././(01|09|17)|L/../../3/11) -m root -M exec /usr/share/smartmontools/smartd-runner

para nenhum proveito.

Também não vejo nenhum LBA_of_first_errorna seção de autoteste.

Para mim, parece que SMART overall-health self-assessment test result: PASSED está saudável e os autotestes não retornam erros. Meu entendimento atual é que o disco parece estar íntegro, mas ainda está enviando essas mensagens erroneamente.

Há algo que estou perdendo?

A /dev/sdaunidade é um SSD KingFast de 256 GB e não tenho certeza se isso seria relevante, pois não consegui encontrar nada online para esta unidade ou fabricante específico.

Como eu poderia parar de receber essas mensagens, mas ainda ter o monitoramento SMART para outros problemas genuínos na unidade e como corrigir o problema se essa mensagem de erro realmente indicar algum problema com a unidade?

Obrigado!

Editar:

Depois de correr smartctl -t long /dev/sda, eu tenho

smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.19.0-46-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     KingFast
Serial Number:    03112222C0002
Firmware Version: U0803A0
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jul  9 10:05:33 2023 PDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x03) Offline data collection activity
                    is in progress.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 241) Self-test routine in progress...
                    10% of test remaining.
Total time to complete Offline 
data collection:        (  600) seconds.
Offline data collection
capabilities:            (0x11) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    No Selective Self-test supported.
SMART capabilities:            (0x0002) Does not save SMART data before
                    entering power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:    (   2) minutes.
Extended self-test routine
recommended polling time:    (  10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0032   100   100   050    Old_age   Always       -       0
  5 Reallocated_Sector_Ct   0x0032   100   100   050    Old_age   Always       -       6
  9 Power_On_Hours          0x0032   100   100   050    Old_age   Always       -       3341
 12 Power_Cycle_Count       0x0032   100   100   050    Old_age   Always       -       441
160 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       3
161 Unknown_Attribute       0x0033   100   100   050    Pre-fail  Always       -       86
163 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       26
164 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       79553
165 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       482
166 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       6
167 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       115
168 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       5050
169 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       98
175 Program_Fail_Count_Chip 0x0032   100   100   050    Old_age   Always       -       0
176 Erase_Fail_Count_Chip   0x0032   100   100   050    Old_age   Always       -       0
177 Wear_Leveling_Count     0x0032   100   100   050    Old_age   Always       -       0
178 Used_Rsvd_Blk_Cnt_Chip  0x0032   100   100   050    Old_age   Always       -       6
181 Program_Fail_Cnt_Total  0x0032   100   100   050    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   100   100   050    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       88
194 Temperature_Celsius     0x0022   100   100   050    Old_age   Always       -       46
195 Hardware_ECC_Recovered  0x0032   100   100   050    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   100   100   050    Old_age   Always       -       3
197 Current_Pending_Sector  0x0032   100   100   050    Old_age   Always       -       6
198 Offline_Uncorrectable   0x0032   100   100   050    Old_age   Always       -       3
199 UDMA_CRC_Error_Count    0x0032   100   100   050    Old_age   Always       -       0
232 Available_Reservd_Space 0x0032   100   100   050    Old_age   Always       -       86
241 Total_LBAs_Written      0x0030   100   100   050    Old_age   Offline      -       170468
242 Total_LBAs_Read         0x0030   100   100   050    Old_age   Offline      -       815560
245 Unknown_Attribute       0x0032   100   100   050    Old_age   Always       -       193199

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      3337         -
# 2  Short offline       Completed without error       00%      3329         -
# 3  Short offline       Completed without error       00%      3325         -
# 4  Short offline       Completed without error       00%      3321         -
# 5  Short offline       Completed without error       00%      3313         -
# 6  Short offline       Completed without error       00%      3309         -
# 7  Short offline       Completed without error       00%      3306         -
# 8  Extended offline    Completed without error       00%      3250         -
# 9  Extended offline    Completed without error       00%      3232         -
#10  Extended offline    Completed without error       00%      3229         -
#11  Extended offline    Completed without error       00%       976         -
#12  Extended offline    Completed without error       00%       968         -

Selective Self-tests/Logging not supported

O teste off-line estendido nº 12 Completed without error, então não tenho certeza do que devo fazer a partir daqui.

Edição nº 2:

Também executei o seguinte, que acredito indicar que não há erros na unidade:

badblocks -sv /dev/sda
Checking blocks 0 to 250059095
Checking for bad blocks (read-only test): done                                                 
Pass completed, 0 bad blocks found. (0/0/0 errors)

dd if=/dev/sda of=/dev/null bs=64K conv=noerror
3907173+1 records in
3907173+1 records out
256060514304 bytes (256 GB, 238 GiB) copied, 485.648 s, 527 MB/s

Eu tenho uma unidade nova que quero testar antes de usar. Apenas instalei, não formatei/particionei, nem criei um sistema de arquivos nele ainda. A primeira coisa que fiz foi verificar as estatísticas do smartctl e, em seguida, iniciar um teste longo cativo .

Depois de esperar as 12 horas necessárias, percebo que o teste foi interrompido e um erro foi registrado. Eu começo o teste mais duas vezes e um erro é registrado imediatamente a cada teste iniciado . Veja as estatísticas smartctl abaixo:

smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-150-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     ST8000NM017B-2TJ103
Serial Number:    WWZ2AFQF
LU WWN Device Id: 5 000c50 0e71315e1
Firmware Version: SN01
User Capacity:    8,001,563,222,016 bytes [8.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sat Jun 10 08:08:32 2023 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Enabled.
Self-test execution status:      (  41) The self-test routine was interrupted
                                        by the host with a hard or soft reset.
Total time to complete Offline
data collection:                (  567) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        ( 702) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x70bd) SCT Status supported.
                                        SCT Error Recovery Control supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   100   044    Pre-fail  Always       -       9402
  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   100   253   045    Pre-fail  Always       -       21867
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       17
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       1
 18 Unknown_Attribute       0x000b   100   100   050    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   253   000    Old_age   Always       -       12885098499
190 Airflow_Temperature_Cel 0x0022   067   066   000    Old_age   Always       -       33 (Min/Max 24/34)
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       39
194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always       -       33 (0 24 0 0 0)
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       0 (137 91 0)
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       0
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       9402

SMART Error Log Version: 1
ATA Error Count: 3
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 3 occurred at disk power-on lifetime: 17 hours (0 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      17:21:46.602  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      17:20:45.112  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 00 00      17:20:45.112  SMART READ DATA
  ec 00 01 00 00 00 00 00      17:20:45.105  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 00      17:20:45.104  IDENTIFY DEVICE
Error 2 occurred at disk power-on lifetime: 17 hours (0 days + 17 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      17:15:48.188  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      17:14:46.401  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 00 00      17:14:46.400  SMART READ DATA
  ec 00 01 00 00 00 00 00      17:14:46.392  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 00      17:14:46.391  IDENTIFY DEVICE

Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
  When the command that caused the error occurred, the device was in an unknown state.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  04 51 00 00 00 00 00  Error: ABRT

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  00 00 00 00 00 00 00 ff      00:08:36.002  NOP [Abort queued commands]
  b0 d4 00 82 4f c2 00 00      00:07:34.853  SMART EXECUTE OFF-LINE IMMEDIATE
  b0 d0 01 00 4f c2 00 00      00:07:34.814  SMART READ DATA
  ec 00 01 00 00 00 00 00      00:07:34.806  IDENTIFY DEVICE
  ec 00 01 00 00 00 00 00      00:07:34.805  IDENTIFY DEVICE

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended captive    Interrupted (host reset)      90%        17         -
# 2  Extended captive    Interrupted (host reset)      90%        17         -
# 3  Extended captive    Interrupted (host reset)      90%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

As taxas de erro de leitura/busca brutas também são bastante altas, mas nunca tenho certeza sobre o formato de smartctl e se esses valores são apenas codificados ...

O Smartctl não requer uma unidade/unidade formatada com um sistema de arquivos para funcionar corretamente, correto? Este é um resultado inesperado? Em caso afirmativo, existem outros testes que devo executar antes do RMA ? Obrigado por sua ajuda com antecedência!

É possível desativar o disco usando a linha de comando? Recebi spam assim:

[2245922.091035] ata3: EH complete
[2245922.150696] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[2245922.150701] ata3.00: irq_stat 0x40000001
[2245922.150703] ata3.00: failed command: FLUSH CACHE EXT
[2245922.150704] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 18
                          res 71/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[2245922.150708] ata3.00: status: { DRDY DF ERR }
[2245922.150709] ata3.00: error: { ABRT }
[2245922.151027] ata3.00: configured for UDMA/33
[2245922.151030] ata3.00: device reported invalid CHS sector 0
[2245922.151034] ata3: EH complete
[2245922.238686] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[2245922.238692] ata3.00: irq_stat 0x40000001
[2245922.238696] ata3.00: failed command: FLUSH CACHE EXT
[2245922.238697] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 24
                          res 71/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[2245922.238701] ata3.00: status: { DRDY DF ERR }
[2245922.238702] ata3.00: error: { ABRT }
[2245922.239043] ata3.00: configured for UDMA/33
[2245922.239047] ata3.00: device reported invalid CHS sector 0
[2245922.239053] sd 2:0:0:0: [sdd] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[2245922.239056] sd 2:0:0:0: [sdd] tag#24 Sense Key : Illegal Request [current]
[2245922.239058] sd 2:0:0:0: [sdd] tag#24 Add. Sense: Unaligned write command
[2245922.239060] sd 2:0:0:0: [sdd] tag#24 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[2245922.239063] I/O error, dev sdd, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 3

o disco problemático não montado e já removido de/etc/fstab

sdd             8:48   0 223.6G  0 disk
├─sdd1          8:49   0   1.9G  0 part
├─sdd2          8:50   0     1K  0 part
└─sdd5          8:53   0 221.7G  0 part

# 256GB GALAX SSD
#UUID=48c76170-0392-44ce-a8c6-f790673c8f32 /media/asd/galax250 ext4 noatime,user 0 0

não reiniciei, pois ainda estou usando o PC. Isso torna tudo um pouco lento.

Eu tenho um Toshiba HDD com um sistema de arquivos ext4 que tenho usado extensivamente até ontem. De repente, tornou-se um sistema de arquivos somente leitura e, quando executo fdisk -l, ele mostra o tipo como HPFS/NTFS/exFAT.

O sistema de leitura de arquivos tornou-se repentinamente somente leitura; como depurar isso? , eu tentei dmesge, entre outras linhas mostra (como sugerido nas respostas lá)

  367.274847] EXT4-fs error (device sdb1): ext4_validate_block_bitmap:390: comm nextcloud: bg 7398: bad block bitmap checksum
[  367.285558] Aborting journal on device sdb1-8.
[  367.297425] EXT4-fs (sdb1): Remounting filesystem read-only
[  513.153456] EXT4-fs (sdb1): error count since last fsck: 5
[  513.153491] EXT4-fs (sdb1): initial error at time 1685397473: ext4_validate_block_bitmap:390
[  513.153509] EXT4-fs (sdb1): last error at time 1685418194: ext4_validate_block_bitmap:390

e é verdade que não o desmontei corretamente, provavelmente da última vez que funcionou.

Como posso resolver isso?

ATUALIZAR

Saída de sudo smartctl -a /dev/sdbé

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.0-23-amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Toshiba 2.5" HDD MQ04UBF... (USB 3.0)
Device Model:     TOSHIBA MQ04UBF100
Serial Number:    Z0IKT0JIT
LU WWN Device Id: 0 000000 000000000
Firmware Version: JU003U
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      2.5 inches
Zoned Device:     Device managed zones
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.3, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Tue May 30 16:22:45 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Status not supported: Incomplete response, ATA output registers missing
SMART overall-health self-assessment test result: PASSED
Warning: This result is based on an Attribute check.

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
Total time to complete Offline 
data collection:        (  120) seconds.
Offline data collection
capabilities:            (0x5b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:    (   2) minutes.
Extended self-test routine
recommended polling time:    ( 175) minutes.
SCT capabilities:          (0x003d) SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       2455
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       5725
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       2976
 10 Spin_Retry_Count        0x0033   214   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       960
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       17
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       120
193 Load_Cycle_Count        0x0032   099   099   000    Old_age   Always       -       13534
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       26 (Min/Max 15/57)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   100   100   000    Old_age   Always       -       182
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       280
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      1003         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Saída defdisk -l

Disk /dev/sdb: 931.51 GiB, 1000204883968 bytes, 1953525164 sectors
Disk model: External USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x558ebb3c

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1  *     2048 1953522863 1953520816 931.5G  7 HPFS/NTFS/exFAT

Eu uso o Ubuntu 20.04, em uma máquina que possui uma unidade de sistema limitada.

Encontrei um script de construção que verifica o tamanho disponível em /tmp, e ele se recusa a ser executado se não encontrar 12 GB disponíveis, que não tenho na unidade do sistema.

No entanto, tenho outra unidade NTFS nesta máquina; como é NTFS, não posso usá-lo diretamente, mas posso criar uma imagem de disco.

Então, pensei em criar uma imagem ext3 de 16 GB na partição NTFS e montá-la como /tmp.

Então, eu tentei:

dd if=/dev/zero of=tmp16.img bs=16M count=0 seek=1024
mkfs.ext3 ./tmp16.img
fdisk -l ./tmp16.img
e2label ./tmp16.img tmp16

Até agora, tudo bem - tudo isso funcionou; mas depois tento montar:

$ sudo mount -o remount /path/to/ntfs/tmp16.img /tmp
mount: /tmp: mount point not mounted or bad option.

Ups, deve ser uma memória antiga minha de algum lugar, que /tmpé uma montagem separada - acontece que, nesta máquina, /tmpnão é uma montagem separada:

$ mount | grep tmp
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=3970256k,nr_inodes=992564,mode=755)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=802768k,mode=755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=802768k,mode=755)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=802764k,mode=700,uid=1000,gid=1000)
tmpfs on /run/netns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=802768k,mode=755)

Bem ... existe alguma maneira de eu usar esta imagem de disco como /tmpnesta máquina - e existe uma maneira de fazer isso, sem ter que reiniciar a máquina (o que seria necessário, eu acho, se algo tiver que ser feito int /etc/fstab?)

Se não, existe alguma outra maneira de aproveitar o espaço NTFS disponível e usá-lo como /tmp- de preferência, sem precisar reiniciar a máquina?

Eu tenho um HDD externo Intenso de 1 TB 2,5" aqui. Ele está com algum defeito (desconecta aleatoriamente no Windows), então decidi executar este comando para verificar:

dd if=/dev/sdb of=/dev/null bs=4M status=progress

A saída durante a execução se parece com isto:

715099471872 Bytes (715 GB, 666 GiB) kopiert, 16115 s, 44,4 MB/s

Além disso, 44,4 MB/s é muito lento para um disco USB3, o estranho é que o relógio está marcando apenas a cada 12s. ("16115 s" é o relógio dd.) Ao executar o mesmo comando em um disco saudável, ele marca a cada segundo.

Tentei stracever por que está bloqueando por tanto tempo, mas parece ler o disco pelo mapeamento de memória, então não consigo ver nada.

Também não é possível que o disco simplesmente bloqueie 12s durante a leitura. Porque a velocidade é de 44,4 MB/s e o tamanho do bloco é de 4 MB. Portanto, dd tem 11 chances por segundo de atualizar o relógio.

Então, o que está acontecendo aqui exatamente?

(Não estou interessado no que há de errado com o disco, mas, em vez disso, quero saber por que o relógio dd está correndo tão devagar. Portanto, espero estar certo no SE Unix.)