Не пойму проблема в ФС или в винте. Винт на террабайт Hitachi HUA722010CLA630. Cистема монтруется только в ro. Как починить?
bash-4.3# badblocks -vv /dev/sda
Checking blocks 0 to 976762583
Checking for bad blocks (read-only test): 125960% done, 0:03 elapsed. (0/0/0 errors)
125970% done, 0:09 elapsed. (1/0/0 errors)
125980% done, 0:12 elapsed. (2/0/0 errors)
125990% done, 0:15 elapsed. (3/0/0 errors)
done
Pass completed, 4 bad blocks found. (4/0/0 errors)
bash-4.3# jfs_fsck -afvv /dev/sda1
jfs_fsck version 1.1.15, 04-Mar-2011
processing started: 10/12/2017 18:34:25
The current device is: /dev/sda1
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 244190390
**Phase 0 - Replay Journal Log
LOGREDO: Log record for Sync Point at: 0x07863ee4
LOGREDO: Beginning to update the Inode Allocation Map.
LOGREDO: Done updating the Inode Allocation Map.
LOGREDO: Beginning to update the Block Map.
ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 11849728
LOGREDO: Read Block Map data extents failed.
LOGREDO: Write Block Map control page failed in UpdateMaps().
LOGREDO: Unable to update map(s).
logredo failed (rc=-271). fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
File system object DF4835102 has corrupt data (3).
**Phase 2 - Count links
Inode F180292 has incorrect link count.
Incorrect link counts have been detected. Will correct.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
Fileset object DF4835102: No paths found.
cannot repair the data format error(s) in this directory.
cannot repair DF4835102. Will release.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
Superblock marked dirty because repairs are about to be written.
Link count for inode F180292 has been adjusted/corrected.
Storage allocated to inode F4835102 has been cleared.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
ujfs_rw_diskblocks: read 12288 of 16384 bytes at offset 11837440
Unrecoverable error reading M from /dev/sda1. CANNOT CONTINUE.
Fatal error (-10093,30) accessing the filesystem (1,11837440,16384,16384).
**** Filesystem was modified. ****
processing terminated: 10/12/2017 19:05:52 with return code: -10093 exit code: 4.
bash-4.3# jfs_fsck -afvv /dev/sda1
jfs_fsck version 1.1.15, 04-Mar-2011
processing started: 10/12/2017 18:34:25
The current device is: /dev/sda1
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 244190390
**Phase 0 - Replay Journal Log
LOGREDO: Log record for Sync Point at: 0x07863ee4
LOGREDO: Beginning to update the Inode Allocation Map.
LOGREDO: Done updating the Inode Allocation Map.
LOGREDO: Beginning to update the Block Map.
ujfs_rw_diskblocks: read 0 of 4096 bytes at offset 11849728
LOGREDO: Read Block Map data extents failed.
LOGREDO: Write Block Map control page failed in UpdateMaps().
LOGREDO: Unable to update map(s).
logredo failed (rc=-271). fsck continuing.
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
File system object DF4835102 has corrupt data (3).
**Phase 2 - Count links
Inode F180292 has incorrect link count.
Incorrect link counts have been detected. Will correct.
**Phase 3 - Duplicate Block Rescan and Directory Connectedness
**Phase 4 - Report Problems
Fileset object DF4835102: No paths found.
cannot repair the data format error(s) in this directory.
cannot repair DF4835102. Will release.
**Phase 5 - Check Connectivity
**Phase 6 - Perform Approved Corrections
Superblock marked dirty because repairs are about to be written.
Link count for inode F180292 has been adjusted/corrected.
Storage allocated to inode F4835102 has been cleared.
**Phase 7 - Rebuild File/Directory Allocation Maps
**Phase 8 - Rebuild Disk Allocation Maps
ujfs_rw_diskblocks: read 12288 of 16384 bytes at offset 11837440
Unrecoverable error reading M from /dev/sda1. CANNOT CONTINUE.
Fatal error (-10093,30) accessing the filesystem (1,11837440,16384,16384).
**** Filesystem was modified. ****
processing terminated: 10/12/2017 19:05:52 with return code: -10093 exit code: 4.
bash-4.3# smartctl -i /dev/sda
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.4.75-smp] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Hitachi HUA722010CLA630
Serial Number: JPW9J0N2121NDC
LU WWN Device Id: 5 000cca 3a8cf0678
Firmware Version: JP4OA55B
User Capacity: 1 000 204 886 016 bytes [1,00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
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 2.6, 6.0 Gb/s
Local Time is: Thu Oct 12 19:41:26 2017 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
bash-4.3# smartctl -i /dev/sda
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.4.75-smp] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Hitachi HUA722010CLA630
Serial Number: JPW9J0N2121NDC
LU WWN Device Id: 5 000cca 3a8cf0678
Firmware Version: JP4OA55B
User Capacity: 1 000 204 886 016 bytes [1,00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
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 2.6, 6.0 Gb/s
Local Time is: Thu Oct 12 19:41:26 2017 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
bash-4.3# smartctl -H /dev/sda
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.4.75-smp] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
bash-4.3# smartctl -H /dev/sda
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.4.75-smp] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
bash-4.3# smartctl -A /dev/sda
smartctl 6.5 2016-05-07 r4318 [i686-linux-4.4.75-smp] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
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 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 106 106 054 Pre-fail Offline - 208
3 Spin_Up_Time 0x0007 124 124 024 Pre-fail Always - 306 (Average 305)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1181
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 140 140 020 Pre-fail Offline - 30
9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 7115
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1181
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1198
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1198
194 Temperature_Celsius 0x0002 122 122 000 Old_age Always - 49 (Min/Max 19/62)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 6
bash-4.3# mount /dev/sda1 /mnt -t jfs
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
