Мои полномочия файлов изменяются спонтанно на только для чтения
Это очень распространено, я делал свои вещи когда мои полномочия файлов, измененные на read-only. Я сразу перезагружаю свой ПК, и это не запустится, так перезагрузка снова ПК с неправильным путем, затем я пишу fsck /dev/sda2 -y. Где проблема? Почему это всегда происходит? ПК восемь месяцев.
Вывод sudo smartctl -a /dev/sda2 после sudo smartctl -t long /dev/sda2 :
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.3.0-46-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: TOSHIBA MQ04ABF100
Serial Number: X8JBP3K2T
LU WWN Device Id: 5 000039 8d268714d
Firmware Version: JU001J
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: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA >3.2 (0x1ff), 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Apr 14 22:33:42 2020 -04
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: ( 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: ( 172) 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 - 1294
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 636
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 095 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 1743
10 Spin_Retry_Count 0x0033 112 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 451
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 1359
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 23
193 Load_Cycle_Count 0x0032 095 095 000 Old_age Always - 50104
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 35 (Min/Max 13/45)
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 200 000 Old_age Always - 0
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 0
222 Loaded_Hours 0x0032 097 097 000 Old_age Always - 1533
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 - 264
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 1096 hours (45 days + 16 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
-- -- -- -- -- -- --
04 31 00 02 59 d7 a9
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 a0 00 05:01:42.830 FLUSH CACHE EXT
61 58 30 38 f9 20 40 00 05:01:42.830 WRITE FPDMA QUEUED
61 08 80 08 f9 1b 40 00 05:01:42.829 WRITE FPDMA QUEUED
61 08 78 a0 b8 52 40 00 05:01:42.788 WRITE FPDMA QUEUED
61 30 70 58 0c 50 40 00 05:01:42.788 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 1743 -
# 2 Extended offline Completed without error 00% 1728 -
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.
0
задан El borito
15 April 2020 в 05:43
поделиться
1 ответ
ОС повторно монтирует Ваш корневой раздел как только для чтения, когда это обнаружило проблему файловой системы в течение времени начальной загрузки или во время времени выполнения, если доступ к диску был потерян для больше, чем определенное время. Вывод smartctl Вы показали (еще), не указывает на проблемы на дисковых счетчиках, но УМНЫЕ журналы показывают проблему доступа к диску в не до сих пор мимо.
Попытайтесь осуществить полную УМНУЮ проверку своего диска: smartctl -t long /dev/sda. Если это ничего не находит, необходимо загрузить Живой Linux (например, Knoppix, Linux Mint, и т.д.) и выполнить a fsck -f на Вашем неподсоединенном внешнем диске.
Потеря доступа к диску в большинстве случаев вызывается неисправным диском, а тем более вызывается дефектным кабелем SATA или контроллером.
3
ответ дан
25 April 2020 в 10:48
поделиться