HDD - Проблемы при загрузке ноутбука - предположительно сбой HDD

Ответить
Аватара пользователя
mkreine

HDD - Проблемы при загрузке ноутбука - предположительно сбой HDD

Сообщение mkreine »

Всем привет!



Есть ноут, купленный 2 года назад. Всегда нормально загружался, а сейчас при загрузке стал выдавать какие-то проблемы с инициализацией свопа, но, тем не менее, загрузился. Я проанализировал хард смартом. Что можете сказать? Инфа под спойлером.





Скрытый текст

[spoiler][root@localhost dev]# smartctl /dev/sda -a

smartctl 6.5 2016-05-07 r4318 [x86_64-linux-3.10.0-862.2.3.el7.x86_64] (local build)

Copyright (C) 2002-16, Bruce Allen, Christian Franke,
www.smartmontools.org




=== START OF INFORMATION SECTION ===

Model Family: HGST Travelstar 5K1000

Device Model: HGST HTS541010A9E680

Serial Number: JD1009DMG64U8K

LU WWN Device Id: 5 000cca 828c2cc4d

Firmware Version: JA0OA710

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

Device is: In smartctl database [for details use: -P show]

ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6

SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)

Local Time is: Tue Jun 26 16:08:25 2018 CEST

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: (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: ( 45) seconds.

Offline data collection

capabilities: (0x51) 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.

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: ( 209) 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 0x002f 100 100 062 Pre-fail Always - 0

2 Throughput_Performance 0x0025 100 100 040 Pre-fail Offline - 0

3 Spin_Up_Time 0x0023 176 100 033 Pre-fail Always - 1

4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 440

5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0

7 Seek_Error_Rate 0x002f 100 100 067 Pre-fail Always - 0

8 Seek_Time_Performance 0x0025 100 100 040 Pre-fail Offline - 0

9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1089

10 Spin_Retry_Count 0x0033 100 100 060 Pre-fail Always - 0

12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 440

183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0

184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0

187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 65536

188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0

190 Airflow_Temperature_Cel 0x0022 075 056 045 Old_age Always - 25 (Min/Max 22/25)

191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 91

192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 983055

193 Load_Cycle_Count 0x0032 084 084 000 Old_age Always - 164677

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 0x0036 100 100 000 Old_age Always - 0

223 Load_Retry_Count 0x002a 100 099 000 Old_age Always - 0



SMART Error Log Version: 1

No Errors Logged



SMART Self-test log structure revision number 1

No self-tests have been logged. [To run self-tests, use: smartctl -t]



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.



[root@localhost dev]#[/spoiler]
Аватара пользователя
mkreine

Re: HDD - Проблемы при загрузке ноутбука - предположительно сбой HDD

Сообщение mkreine »

Добавлю:



в boot.log такое:





boot.log

[spoiler][ TIME ] Timed out waiting for device dev-mapper-centos_192\x2dswap.device.

[DEPEND] Dependency failed for /dev/mapper/centos_192-swap.

[DEPEND] Dependency failed for Swap.

[FAILED] Failed to start udev Wait for Complete Device Initialization.

See 'systemctl status systemd-udev-settle.service' for details.[/spoiler]






далее...





systemctl status systemd-udev-settle.service

[spoiler][root@localhost log]# systemctl status systemd-udev-settle.service

● systemd-udev-settle.service - udev Wait for Complete Device Initialization

Loaded: loaded (/usr/lib/systemd/system/systemd-udev-settle.service; static; vendor preset: disabled)

Active: failed (Result: exit-code) since Вт 2018-06-26 16:04:55 CEST; 19min ago

Docs: man:udev(7)

man:systemd-udevd.service(8)

Process: 530 ExecStart=/usr/bin/udevadm settle (code=exited, status=1/FAILURE)

Main PID: 530 (code=exited, status=1/FAILURE)



июн 26 16:02:54 localhost.localdomain systemd[1]: Starting udev Wait for Complete Device Initialization...

июн 26 16:04:55 localhost.localdomain systemd[1]: systemd-udev-settle.service: main process exited, code=exited, status=1/FAILURE

июн 26 16:04:55 localhost.localdomain systemd[1]: Failed to start udev Wait for Complete Device Initialization.

июн 26 16:04:55 localhost.localdomain systemd[1]: Unit systemd-udev-settle.service entered failed state.

июн 26 16:04:55 localhost.localdomain systemd[1]: systemd-udev-settle.service failed.

[root@localhost log]#



что вообще происходит? если я его перезагружу, он перезагрузится нормально?[/spoiler]






И ещё в логах такое есть (приведен только фрагмент, это отображалось при загрузке):



^[[0m^[[31m* ^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (11s / 2min 54s)

^[[K[^[[1;31m*^[[0m^[[31m* ^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (12s / 2min 54s)

^[[K[^[[31m*^[[1;31m*^[[0m^[[31m* ^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (12s / 2min 54s)

^[[K[ ^[[31m*^[[1;31m*^[[0m^[[31m* ^[[0m] (2 of 2) A start job is running for dev-mapper-centos_192\x2dswap.device (19s / 1min 30s)

^[[K[ ^[[31m*^[[1;31m*^[[0m^[[31m* ^[[0m] (2 of 2) A start job is running for dev-mapper-centos_192\x2dswap.device (19s / 1min 30s)

^[[K[ ^[[31m*^[[1;31m*^[[0m^[[31m*^[[0m] (2 of 2) A start job is running for dev-mapper-centos_192\x2dswap.device (20s / 1min 30s)

^[[K[ ^[[31m*^[[1;31m*^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (14s / 2min 54s)

^[[K[ ^[[31m*^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (15s / 2min 54s)

^[[K[ ^[[31m*^[[1;31m*^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (15s / 2min 54s)

^[[K[ ^[[31m*^[[1;31m*^[[0m^[[31m*^[[0m] (2 of 2) A start job is running for dev-mapper-centos_192\x2dswap.device (22s / 1min 30s)

^[[K[ ^[[31m*^[[1;31m*^[[0m^[[31m* ^[[0m] (2 of 2) A start job is running for dev-mapper-centos_192\x2dswap.device (22s / 1min 30s)

^[[K[ ^[[31m*^[[1;31m*^[[0m^[[31m* ^[[0m] (2 of 2) A start job is running for dev-mapper-centos_192\x2dswap.device (23s / 1min 30s)

^[[K[^[[31m*^[[1;31m*^[[0m^[[31m* ^[[0m] (1 of 2) A start job is running for udev Wait for Complete Device Initialization (17s / 2min 54s)
Аватара пользователя
Jula0071

Re: HDD - Проблемы при загрузке ноутбука - предположительно сбой HDD

Сообщение Jula0071 »

mkreine, у диска состояние поганенькое. Очень много для его возраста 193 Load_Cycle_Count 0x0032 084 084 000 Old_age Always - 164677, также 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 65536 (последняя цифра очень не нравится круглостью - счётчик переполнился?) и 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 983055 нехорошо.



Диск я бы заменил, причём, на SSD. Бекапы есть? Изображение



По логической структуре, судя по всему, вы используете LVM, ну вот и покажите выхлоп команд pvs, vgs, lvs. Ну и содержимое /etc/fstab
Аватара пользователя
mkreine

Re: HDD - Проблемы при загрузке ноутбука - предположительно сбой HDD

Сообщение mkreine »

Скрытый текст

[spoiler][root@localhost kis]# pgs

bash: pgs: команда не найдена...

[root@localhost kis]# vgs

VG #PV #LV #SN Attr VSize VFree

centos_192 1 3 0 wz--n- 930,31g 4,00m

[root@localhost kis]# lgs

bash: lgs: команда не найдена...

[root@localhost kis]#[/spoiler]








/etc/fstab

[spoiler][root@localhost kis]# cat /etc/fstab



#

# /etc/fstab

# Created by anaconda on Thu Mar 8 12:09:33 2018

#

# Accessible filesystems, by reference, are maintained under '/dev/disk'

# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info

#

/dev/mapper/centos_192-root / xfs defaults 0 0

UUID=75cdb1e7-d2d9-49f4-a8ce-2f6b84b36641 /boot xfs defaults 0 0

UUID=DBAD-78F5 /boot/efi vfat umask=0077,shortname=winnt 0 0

/dev/mapper/centos_192-home /home xfs defaults 0 0

/dev/mapper/centos_192-swap swap swap defaults 0 0

[root@localhost kis]#[/spoiler]






Что, прям так срочно заменять?
Ответить

Вернуться в «Накопители (SSD, HDD, USB Flash)»