fsck an lvm volume?

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

fsck an lvm volume?

Post by jaymot » Tue Oct 09, 2018 6:05 am

I installed Mint 19 Cinnamon with full disk encryption (an encrypted LVM.). Now GSmartControl is reporting an error at a particular LBA address. I think I should probably run fsck on the disk to try to correct this but I heard that fscking an encrypted volume might corrupt it and render the system unbootable. What's the correct procedure that I should follow?

Thanks.
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

User avatar
WharfRat
Level 20
Level 20
Posts: 11727
Joined: Thu Apr 07, 2011 8:15 pm

Re: fsck an lvm volume?

Post by WharfRat » Tue Oct 09, 2018 9:58 am

The easiest way to run fsck is to sudo touch /forcefsck in the terminal then reboot :wink:
ImageImage

jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

Re: fsck an lvm volume?

Post by jaymot » Tue Oct 09, 2018 8:50 pm

Thanks for the suggestion. I tried that but nothing seemed to happen when I rebooted.

FYI:

Code: Select all

System:    Host: jay-UX303UB Kernel: 4.15.0-34-generic x86_64
           bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30) Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: ASUSTeK product: UX303UB v: 1.0 serial: N/A
           Mobo: ASUSTeK model: UX303UB v: 1.0 serial: N/A
           UEFI: American Megatrends v: UX303UB.206 date: 03/02/2016
Battery    BAT0: charge: 42.3 Wh 97.8% condition: 43.2/50.1 Wh (86%)
           model: ASUSTeK ASUS status: Discharging
CPU:       Dual core Intel Core i7-6500U (-MT-MCP-) 
           arch: Skylake rev.3 cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10368
           clock speeds: max: 3100 MHz 1: 500 MHz 2: 500 MHz 3: 500 MHz
           4: 500 MHz
Graphics:  Card-1: Intel HD Graphics 520 bus-ID: 00:02.0
           Card-2: NVIDIA GM108M [GeForce 940M] bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.01hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
           version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.15.0-34-generic
Network:   Card-1: Intel Wireless 7265 driver: iwlwifi bus-ID: 02:00.0
           IF: wlp2s0 state: up mac: <filter>
           Card-2: Atmel usb-ID: 001-004
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: 1000.2GB (53.8% used)
           ID-1: /dev/sda model: HGST_HTS541010A7 size: 1000.2GB
Partition: ID-1: / size: 904G used: 490G (58%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 705M used: 223M (35%) fs: ext4 dev: /dev/sda2
           ID-3: swap-1 size: 12.65GB used: 0.00GB (0%)
           fs: swap dev: /dev/dm-2
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 47.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 2200
Info:      Processes: 219 Uptime: 15 min Memory: 1858.2/11787.5MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56
Last edited by WharfRat on Tue Oct 09, 2018 9:18 pm, edited 1 time in total.
Reason: Added code tag
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

User avatar
WharfRat
Level 20
Level 20
Posts: 11727
Joined: Thu Apr 07, 2011 8:15 pm

Re: fsck an lvm volume?

Post by WharfRat » Tue Oct 09, 2018 9:20 pm

An fsck can be very quick if there are no problems.

To check if it was done paste back sudo tune2fs -l /dev/mapper/mint--vg-root|egrep 'Mount\ count|Maximum\ mount'
ImageImage

jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

Re: fsck an lvm volume?

Post by jaymot » Tue Oct 09, 2018 10:20 pm

Mount count: 28
Maximum mount count: -1

Does it show the fsck while in progress or does it take place behind the splash screen? If it did it it was very fast, faster than I would have expected on a 1 terabyte drive.
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

Re: fsck an lvm volume?

Post by jaymot » Tue Oct 09, 2018 10:24 pm

When I click on the drive in GSmartControl is says basic health check passed but when I run the short tests it says
"Test #","Type","Status","% Completed","Lifetime hours","LBA of the first error"
1,"Short offline","Completed with read failure","10%","4,273","1940867712"
2,"Short offline","Completed with read failure","10%","4,262","1940867712"
3,"Short offline","Completed with read failure","10%","4,249","1940867712"
4,"Short offline","Completed with read failure","10%","3,641","1940867712"
5,"Short offline","Completed with read failure","10%","3,619","1940867712"
6,"Short offline","Completed without error","100%","761","-"

Full details of the tests:

Code: Select all

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.15.0-34-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     HGST Travelstar Z5K1000
Device Model:     HGST HTS541010A7E630
Serial Number:    S00001SSJR5S4F
LU WWN Device Id: 5 000cca 756e644be
Firmware Version: SE0OA4H0
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:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Oct 10 10:22:38 2018 +08
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
ATA Security is:  Disabled, frozen [SEC2]

=== 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:      ( 121)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		(   45) 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: 	 ( 226) 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          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     PO-R--   100   100   062    -    65536
  2 Throughput_Performance  P-S---   160   160   040    -    125
  3 Spin_Up_Time            POS---   197   197   033    -    1
  4 Start_Stop_Count        -O--C-   099   099   000    -    3063
  5 Reallocated_Sector_Ct   PO--CK   100   100   005    -    0
  7 Seek_Error_Rate         PO-R--   100   100   067    -    0
  8 Seek_Time_Performance   P-S---   132   132   040    -    34
  9 Power_On_Hours          -O--C-   091   091   000    -    4273
 10 Spin_Retry_Count        PO--C-   100   100   060    -    0
 12 Power_Cycle_Count       -O--CK   100   100   000    -    954
191 G-Sense_Error_Rate      -O-R--   099   099   000    -    2
192 Power-Off_Retract_Count -O--CK   100   100   000    -    149
193 Load_Cycle_Count        -O--C-   100   100   000    -    7458
194 Temperature_Celsius     -O----   157   157   000    -    38 (Min/Max 25/53)
196 Reallocated_Event_Count -O--CK   100   100   000    -    0
197 Current_Pending_Sector  -O---K   100   100   000    -    8
198 Offline_Uncorrectable   ---R--   100   100   000    -    0
199 UDMA_CRC_Error_Count    -O-R--   200   200   000    -    0
223 Load_Retry_Count        -O-R--   100   100   000    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      1  Comprehensive SMART error log
0x03       GPL     R/O      1  Ext. Comprehensive SMART error log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  SATA NCQ Queued Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 3
	CR     = Command Register
	FEATR  = Features Register
	COUNT  = Count (was: Sector Count) Register
	LBA_48 = Upper bytes of LBA High/Mid/Low Registers ]  ATA-8
	LH     = LBA High (was: Cylinder High) Register    ]   LBA
	LM     = LBA Mid (was: Cylinder Low) Register      ] Register
	LL     = LBA Low (was: Sector Number) Register     ]
	DV     = Device (was: Device/Head) Register
	DC     = Device Control Register
	ER     = Error register
	ST     = Status register
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 [2] occurred at disk power-on lifetime: 3624 hours (151 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 73 af 4a 80 03 00  Error: UNC at LBA = 0x73af4a80 = 1940867712

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 18 00 00 73 af 4a 80 40 00     03:23:57.662  READ FPDMA QUEUED
  ef 00 10 00 02 00 00 00 00 00 00 a0 00     03:23:57.661  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 00 00 00 00 00 e0 00     03:23:57.661  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 00 00 00 00 00 a0 00     03:23:57.660  IDENTIFY DEVICE
  ef 00 03 00 46 00 00 00 00 00 00 a0 00     03:23:57.660  SET FEATURES [Set transfer mode]

Error 2 [1] occurred at disk power-on lifetime: 3624 hours (151 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 00 08 00 00 73 af 4a 80 03 00  Error: UNC at LBA = 0x73af4a80 = 1940867712

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 00 08 00 e8 00 00 73 af 4a 80 40 00     03:23:53.636  READ FPDMA QUEUED
  60 00 08 00 e0 00 00 73 af 4a 78 40 00     03:23:53.636  READ FPDMA QUEUED
  60 00 08 00 d8 00 00 73 af 4a 70 40 00     03:23:53.636  READ FPDMA QUEUED
  60 00 08 00 d0 00 00 73 af 4a 68 40 00     03:23:53.636  READ FPDMA QUEUED
  60 00 08 00 c8 00 00 73 af 4a 60 40 00     03:23:53.636  READ FPDMA QUEUED

Error 1 [0] occurred at disk power-on lifetime: 3624 hours (151 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER -- ST COUNT  LBA_48  LH LM LL DV DC
  -- -- -- == -- == == == -- -- -- -- --
  40 -- 51 03 80 00 00 73 af 4a 80 03 00  Error: UNC at LBA = 0x73af4a80 = 1940867712

  Commands leading to the command that caused the error were:
  CR FEATR COUNT  LBA_48  LH LM LL DV DC  Powered_Up_Time  Command/Feature_Name
  -- == -- == -- == == == -- -- -- -- --  ---------------  --------------------
  60 0a 00 00 88 00 00 73 af 44 00 40 00     03:23:49.525  READ FPDMA QUEUED
  60 0a 00 00 80 00 00 73 af 3a 00 40 00     03:23:49.501  READ FPDMA QUEUED
  60 0a 00 00 78 00 00 73 af 30 00 40 00     03:23:49.477  READ FPDMA QUEUED
  60 0a 00 00 70 00 00 73 af 26 00 40 00     03:23:49.452  READ FPDMA QUEUED
  60 0a 00 00 68 00 00 73 af 1c 00 40 00     03:23:49.428  READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       90%      4273         1940867712
# 2  Short offline       Completed: read failure       90%      4262         1940867712
# 3  Short offline       Completed: read failure       90%      4249         1940867712
# 4  Short offline       Completed: read failure       90%      3641         1940867712
# 5  Short offline       Completed: read failure       90%      3619         1940867712
# 6  Short offline       Completed without error       00%       761         -

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.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
SCT Support Level:                   1
Device State:                        Active (0)
Current Temperature:                    38 Celsius
Power Cycle Min/Max Temperature:     29/38 Celsius
Lifetime    Min/Max Temperature:     25/53 Celsius
Lifetime    Average Temperature:        38 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Temperature History Version:     2
Temperature Sampling Period:         1 minute
Temperature Logging Interval:        1 minute
Min/Max recommended Temperature:      0/60 Celsius
Min/Max Temperature Limit:           -40/65 Celsius
Temperature History Size (Index):    128 (64)

Index    Estimated Time   Temperature Celsius
  65    2018-10-10 08:15    36  *****************
 ...    ..(  2 skipped).    ..  *****************
  68    2018-10-10 08:18    36  *****************
  69    2018-10-10 08:19    35  ****************
  70    2018-10-10 08:20    35  ****************
  71    2018-10-10 08:21    36  *****************
 ...    ..( 11 skipped).    ..  *****************
  83    2018-10-10 08:33    36  *****************
  84    2018-10-10 08:34    37  ******************
  85    2018-10-10 08:35    37  ******************
  86    2018-10-10 08:36    38  *******************
  87    2018-10-10 08:37    38  *******************
  88    2018-10-10 08:38    37  ******************
 ...    ..(  7 skipped).    ..  ******************
  96    2018-10-10 08:46    37  ******************
  97    2018-10-10 08:47    38  *******************
 ...    ..(  2 skipped).    ..  *******************
 100    2018-10-10 08:50    38  *******************
 101    2018-10-10 08:51    37  ******************
 102    2018-10-10 08:52    38  *******************
 ...    ..(  7 skipped).    ..  *******************
 110    2018-10-10 09:00    38  *******************
 111    2018-10-10 09:01    37  ******************
 112    2018-10-10 09:02    38  *******************
 ...    ..(  4 skipped).    ..  *******************
 117    2018-10-10 09:07    38  *******************
 118    2018-10-10 09:08    37  ******************
 ...    ..( 11 skipped).    ..  ******************
   2    2018-10-10 09:20    37  ******************
   3    2018-10-10 09:21    38  *******************
   4    2018-10-10 09:22    37  ******************
 ...    ..( 41 skipped).    ..  ******************
  46    2018-10-10 10:04    37  ******************
  47    2018-10-10 10:05    38  *******************
  48    2018-10-10 10:06    37  ******************
  49    2018-10-10 10:07    37  ******************
  50    2018-10-10 10:08    37  ******************
  51    2018-10-10 10:09    38  *******************
  52    2018-10-10 10:10    37  ******************
 ...    ..(  3 skipped).    ..  ******************
  56    2018-10-10 10:14    37  ******************
  57    2018-10-10 10:15    38  *******************
  58    2018-10-10 10:16    37  ******************
 ...    ..(  4 skipped).    ..  ******************
  63    2018-10-10 10:21    37  ******************
  64    2018-10-10 10:22    38  *******************

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  2            0  Command failed due to ICRC error
0x0002  2            0  R_ERR response for data FIS
0x0003  2            0  R_ERR response for device-to-host data FIS
0x0004  2            0  R_ERR response for host-to-device data FIS
0x0005  2            0  R_ERR response for non-data FIS
0x0006  2            0  R_ERR response for device-to-host non-data FIS
0x0007  2            0  R_ERR response for host-to-device non-data FIS
0x0009  2            7  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2            5  Device-to-host register FISes sent due to a COMRESET
0x000b  2            0  CRC errors within host-to-device FIS
0x000d  2            0  Non-CRC errors within host-to-device FIS
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

User avatar
WharfRat
Level 20
Level 20
Posts: 11727
Joined: Thu Apr 07, 2011 8:15 pm

Re: fsck an lvm volume?

Post by WharfRat » Tue Oct 09, 2018 10:32 pm

jaymot wrote:
Tue Oct 09, 2018 10:20 pm
Mount count: 28
Maximum mount count: -1

Does it show the fsck while in progress or does it take place behind the splash screen? If it did it it was very fast, faster than I would have expected on a 1 terabyte drive.
I'm not sure if it would show as I disable the splash screen, but I can see it didn't work unless you restarted 28 times since then.

If you want to do it manually it will have to be from the installation media's terminal with sudo fsck -fvCy /dev/mapper/mint--vg-root

Another thing you can do is to set the Maximum mount count say to 30 so that it will run fsck after the filesystem is mounted 30 times with sudo tune2fs -c30 /dev/mapper/mint--vg-root

You can run the tune2fs command within your running system,
ImageImage

jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

Re: fsck an lvm volume?

Post by jaymot » Tue Oct 09, 2018 10:58 pm

Thanks. I restarted it right after scheduling a fsck on next boot and once more after that when I shut down before I went to bed. I took your advice and scheduled the fsck after 30 boots. We'll see what happens.

I don't think fsck can actually repair a bad block, can it? It just moves whatever's on it elsewhere if it can and marks the block as "do not use"?

I'm just a tad worried that the hard drive in this machine isn't long for this world bcause, it being an ultrabook, it has to be taken to a shop to have the drive replaced as there are no access panels on the bottom for the hdd and ram like there are with regular laptops, so it isn't something I can do myself. If it's in a shop it will take them 2 to 3 weeks, judging by experience, or even longer if they don't have a drive in stock and have to order one.

Question: the only difference between a mobile HDD and a regular one is the mobile drives have a lower RPM to save power when running on battery, right? So theoretically I could replace this 1TB mobile drive with a regular 2TB or larger drive (I don't think I can get mobile HDDs larger than 1TB here)? I only run the machine on AC anyway because I don't travel very much so the only thing I use the battery for is power-filtering and as a built-in UPS.
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

User avatar
WharfRat
Level 20
Level 20
Posts: 11727
Joined: Thu Apr 07, 2011 8:15 pm

Re: fsck an lvm volume?

Post by WharfRat » Tue Oct 09, 2018 11:58 pm

If you want to invoke badblocks from fsck then the "-c" would need to be added.

I'm not sure if anything is moved, but if bad blocks are found, they are added to the bad block inode to prevent them from being allocated.

You might wan to install smartmontools and gsmartcontrol to check on the health of the disk.

GSmartControl is the gui for smartctl.

I can't speak to the type of HDDs you can use for the ultrabook as I've never had one.
ImageImage

jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

Re: fsck an lvm volume?

Post by jaymot » Wed Oct 17, 2018 1:14 am

It went past the max mount count of 30 and it's now back to #6. I never saw it running fsck.

I booted from the installation USB stick and tried
sudo fsck -fvCy /dev/mapper/mint--vg-root
but it said it couldnt find /dev/mapper/mint--vg-root. When I looked in /dev/mapper all that was there was a file named "control". When I rebooted back into my main Mint installation on the hard drive, entered my encryption password, logged in then browser /dev/mapper on the hard drive it contains control, mint--vg-root, mint--vg-swap and sda3_crypt.

What prompted me to want to run fsck in the first place is that I already have smartmontools and gsmartcontrol installed, and gsmartcontrol is reporting an error 10% of the way into the quick test, which then fails.
"Short offline","Completed with read failure","10%","4,273","1940867712"
I already posted the entire error message that's in gsmartcontrol.
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

User avatar
WharfRat
Level 20
Level 20
Posts: 11727
Joined: Thu Apr 07, 2011 8:15 pm

Re: fsck an lvm volume?

Post by WharfRat » Wed Oct 17, 2018 8:55 am

jaymot wrote:
Tue Oct 09, 2018 6:05 am
I installed Mint 19 Cinnamon with full disk encryption (an encrypted LVM.).
You have an encrypted system so you would first need to open the LUKS container from the installation USB to expose the filesystem with

sudo /sbin/cryptsetup luksOpen /dev/sda5 sda5_crypt # sda5 matches the encrypted partition

Then sudo fsck -fvCy /dev/mapper/mint--vg-root
ImageImage

jaymot
Level 2
Level 2
Posts: 67
Joined: Thu Apr 12, 2018 11:22 pm

Re: fsck an lvm volume?

Post by jaymot » Fri Oct 19, 2018 7:02 am

WharfRat wrote:
Wed Oct 17, 2018 8:55 am
jaymot wrote:
Tue Oct 09, 2018 6:05 am
I installed Mint 19 Cinnamon with full disk encryption (an encrypted LVM.).
You have an encrypted system so you would first need to open the LUKS container from the installation USB to expose the filesystem with

sudo /sbin/cryptsetup luksOpen /dev/sda5 sda5_crypt # sda5 matches the encrypted partition

Then sudo fsck -fvCy /dev/mapper/mint--vg-root
OK, thank you. I'll try that.
Mint 19 Tara Cinnamon, Asus Zenbook UX303UB, 12GiB 1.6GHz DDR3 RAM, 1TiB HD, Intel Skylake & GeForce 940M GPUs, Intel Core i7 mobile CPU

User avatar
manu73
Level 1
Level 1
Posts: 5
Joined: Tue Jul 21, 2015 9:15 am

Re: fsck an lvm volume?

Post by manu73 » Fri Oct 19, 2018 9:15 am

i fixed the vg--root etc.. in another way.
i boot with a live usb, than decripted the hd volume, then by DISKS app i select the volume and select "repair file system".
rebot and no more vg--root....... error.
Image

Post Reply

Return to “Hardware Support”