Eu tenho um Inspiron 3521 que veio pré-instalado com o Windows 8.1. Decidi inicializar duas vezes o Windows e o Ubuntu, e estava funcionando bem. Mas, ao usar o Ubuntu, ouvi muito barulho no meu laptop enquanto usava o Windows, estava quase silencioso. Além disso, após cerca de duas a três semanas de uso do Ubuntu, não consegui usar o Windows, pois ele se tornou muito lento. Agora estou substituindo meu disco rígido, pois está falhando. Então, instalar o Ubuntu e usá-lo está destruindo o meu disco rígido? Porque antes de instalá-lo, o Windows estava funcionando bem, mas depois disso, tornou-se quase inutilizável. Portanto, devo instalar o Ubuntu no meu novo disco ou devo me abster dele. Por favor, ajudem porque eu gosto mais do Ubuntu do que do Windows, mas não posso arriscar comprar novos HDs repetidamente. Além disso, remover completamente o Windows não é uma opção.
Por favor, deixe-me saber se devo instalar o Ubuntu ao lado?
Saída de smartctl -a /dev/sda::
=== START OF INFORMATION SECTION ===
Device Model: ST500LT012-1DG142
Serial Number: W3P8Y9MR
LU WWN Device Id: 5 000c50 07c643db0
Firmware Version: 0001SDM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Feb 17 15:58:15 2015 IST
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: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 0) 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: ( 97) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1035) SCT Status 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 117 080 006 Pre-fail Always - 158207928
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 414
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 16
7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 38678857862
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 772 (87 233 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 384
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1465
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 059 052 045 Old_age Always - 41 (Min/Max 29/43)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 195
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 14
193 Load_Cycle_Count 0x0032 096 096 000 Old_age Always - 8566
194 Temperature_Celsius 0x0022 041 048 000 Old_age Always - 41 (0 17 0 0 0)
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 8
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 8
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 100 000 Old_age Offline - 276333900858102
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2960885917
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 5374462826
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2175 (device log contains only the most recent five errors)
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 2175 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 20 19 56 00 Error: UNC at LBA = 0x00561920 = 5642528
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 00 ff ff ff 4f 00 00:15:34.369 READ FPDMA QUEUED
61 00 68 ff ff ff 4f 00 00:15:34.369 WRITE FPDMA QUEUED
61 00 10 ff ff ff 4f 00 00:15:34.369 WRITE FPDMA QUEUED
60 00 08 20 19 56 40 00 00:15:34.368 READ FPDMA QUEUED
60 00 40 ff ff ff 4f 00 00:15:34.368 READ FPDMA QUEUED
Error 2174 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 20 19 56 00 Error: UNC at LBA = 0x00561920 = 5642528
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 20 19 56 40 00 00:15:31.814 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:15:31.814 READ FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:15:31.813 WRITE FPDMA QUEUED
ea 00 00 00 00 00 a0 00 00:15:31.813 FLUSH CACHE EXT
27 00 00 00 00 00 e0 00 00:15:31.787 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 2173 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 20 19 56 00 Error: WP at LBA = 0x00561920 = 5642528
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 10 ff ff ff 4f 00 00:15:29.177 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:15:29.177 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:15:29.177 WRITE FPDMA QUEUED
60 00 08 20 19 56 40 00 00:15:29.176 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:15:29.176 READ FPDMA QUEUED
Error 2172 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 20 19 56 00 Error: WP at LBA = 0x00561920 = 5642528
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 08 ff ff ff 4f 00 00:15:26.514 WRITE FPDMA QUEUED
61 00 18 ff ff ff 4f 00 00:15:26.513 WRITE FPDMA QUEUED
60 00 08 20 19 56 40 00 00:15:26.513 READ FPDMA QUEUED
60 00 40 ff ff ff 4f 00 00:15:26.513 READ FPDMA QUEUED
61 00 08 ff ff ff 4f 00 00:15:26.513 WRITE FPDMA QUEUED
Error 2171 occurred at disk power-on lifetime: 758 hours (31 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 20 19 56 00 Error: UNC at LBA = 0x00561920 = 5642528
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 40 ff ff ff 4f 00 00:15:18.647 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:15:18.641 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:15:18.629 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:15:18.619 READ FPDMA QUEUED
60 00 20 ff ff ff 4f 00 00:15:18.607 READ FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 760 5642528
# 2 Short offline Completed: read failure 90% 759 5642528
# 3 Short offline Completed: read failure 90% 759 5642528
# 4 Short offline Completed: read failure 90% 758 5642528
# 5 Short offline Completed: read failure 90% 756 5642528
# 6 Short offline Completed: read failure 90% 752 5642528
# 7 Extended offline Completed: read failure 90% 752 5642528
# 8 Short offline Completed: read failure 90% 752 5642528
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.
Nota: O teste acima é do antigo HDD, que acho que foi destruído por coincidência durante a execução do Ubuntu.
Saída de sudo parted --list:
Model: ATA ST500LT012-1DG14 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 316MB 315MB ntfs Basic data partition hidden, diag
2 316MB 419MB 104MB fat32 EFI system partition boot
3 419MB 554MB 134MB Microsoft reserved partition msftres
4 554MB 237GB 236GB ntfs Basic data partition msftdata
10 237GB 289GB 52.4GB ext4
7 289GB 293GB 4096MB linux-swap(v1)
8 293GB 314GB 20.5GB ext4
9 314GB 342GB 27.9GB ext4
5 342GB 395GB 53.7GB ntfs Basic data partition msftdata
6 395GB 500GB 105GB ntfs Basic data partition msftdata
dual-boot
hard-drive
LakshyaAg
fonte
fonte
Respostas:
TL; DR
Não, o Ubuntu não está destruindo seu disco rígido! :-)
A resposta longa:
Os HDDs sofrem uma morte lenta e dolorosa como o câncer, enquanto os SSDs de repente param de funcionar como um ataque cardíaco : você pode diagnosticar os dois usando a tecnologia SMART .
Por que você ouviu os ruídos no Ubuntu e não no Windows é porque o Windows foi instalado primeiro, portanto ele reside no lado interno do seu disco rígido na região mais densa, enquanto o Ubuntu foi instalado nas regiões externas onde os ruídos são mais pronunciados devido a procurar.
E posso deduzir tudo isso apenas a partir da descrição dos sintomas, sem ter examinado a tabela de partições do disco rígido nem saber como você instalou o sistema ...
fonte
Que tipo de som ele faz? Se você ouvir um clique, seu sistema operacional pode estar realmente destruindo seu disco rígido . O problema é antigo e envolve o recurso Gerenciamento Avançado de Energia, que estaciona / desparafusa o disco com muita agressividade. Tente usar o hdparm para verificar o valor do APM (-B param). Se for menor que 254, defina-o como 254 e verifique se isso ajuda com o ruído. Se isso acontecer, verifique se o valor permanece 254 o tempo todo. Uma boa maneira de garantir isso no Linux é usar tlp. Para constar, eu já vi esse problema ocorrer no Windows, bem como em alguns modelos de laptop, mas é muito mais comum no Linux.
fonte
Você tem (pelo menos) um bloco inválido (LBA 5642528) que está causando erros repetidos. Você pode tentar:
ou
Atualização # 1:
Para testar seu HDD quanto a blocos defeituosos ...
sudo e2fsck -fcky /dev/sdXX# teste somente leituraou
sudo e2fsck -fccky /dev/sdXX# teste não destrutivo de leitura / gravação (recomendado)O -k é importante, porque salva a tabela anterior de blocos defeituosos e adiciona quaisquer novos blocos defeituosos a essa tabela. Sem -k, você perde todas as informações anteriores sobre blocos defeituosos.
O parâmetro -fccky ...
fonte