Arch Linux

Evergreen

Member

Registered: 2016-08-14

Posts: 16

Archlinux booting in emergency mode

When booting arch, I am getting some error messages and then the system goes in emergency mode. The error messages during boot are as follows:

ata1.00:   exception Emask 0x0 SAct 0x60000 SErr 0x0 action 0x0
ata1.00:   irq_stat 0x40000008
ata1.00:   failed command : READ FPDMA QUEUED
ata1.00:   cmd 60/08:88:00:80:54/00:00:3f:00:00/40 tag 17 ncq dma 4096 in
                res   43/40:08:00:80:54/00:00:3f:00:00/00 Emask 0x408 (media error) . <F>
ata1.00:   status:   {DRDY SENSE ERR}
ata1.00:   error:     { UNC }
print_req_error:   I/O error, dev sda, sector 1062502400
Buffer I/O error on dev sda8, logical block 256, async page read
.
.
.
[TIME]   Timed out waiting for device dev-disk-by\x2duuid-64cc27ed\x2d56ec\x2d4bd7\x2d878d\x2d9eaaa41519c8.device
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/64cc27ed-56ec-4bd7-878d-9eaaa41519c8
[DEPEND] Dependency failed for/home
[DEPEND] Dependency failed for Local File Systems

Both dmesg and journalctl -xb outputs are very long. But they have some lines marked in red. However these are exactly those given above. So I am not listing their output separately.
If they are necessary, please tell that in your reply and I'll do my best to provide them.

blkid

/dev/sda1: UUID="7458-EF20" TYPE="vfat" PARTLABEL="EFI system Partition" PARTUUID="fcdcd89e-9f6f-46b1-b51f-5922871bf933"
/dev/sda2: LABEL="Recovery" UUID="01D1EE439A9C2940" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="0008d437-1080-7bb3-42fe-f9016ea81100"
/dev/sda4: UUID="01D1EE40BE516CE0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9de849B5-e572-4494-b704-35f38ecfb451"
/dev/sda5: UUID="8EEEE986EEE96745"  TYPE="ntfs" PARTUUID="186e5ed8-f29a-4270-b724-da6ee8b306cb"
/dev/sda6: UUID="b41de791-b2d6-4ecf-8507-5555d62565aa" TYPE="ext4" PARTUUID="86d0f097-64b2-4de8-8aee-d9cea1c78b79"
/dev/sda7: UUID="b25822da-20e5-4af4-8263-a3d9edf4d222" TYPE="ext4" PARTUUID="bd66aa64-612c-4769-a040-60251421cf45"
/dev/sda9: UUID="20225ca2-1fd6-46f2-b9ea-3a5234abf7f7"    TYPE="swap" PARTUUID="979c7f00-46cc-4b1e-a07a-415953214c79"
/dev/sda10: UUID="cdb93b18-e9be-4fa8-a2ef-264ce158c1dc" TYPE="ext4" PARTUUID="faef03ba-3a48-4174-bf5e-707312520fc0"
/dev/sda3: PARTLABEL="Basic data partition" PARTUUID="785758f0-ee42-01d1-7828-2b3c21f7e800"

bootctl status

System:
      Firmware: UEFI 2.31 (American Megatrends 4.654)
      Secure Boot: disabled
      Setup Mode: setup

Current Loader:
      Product: systemd-boot 231
      ESP: /dev/disk/by-partuuid/fcdcd89e-9f6f-b6b1-b51f-5922871bf933
      File: /EFI/systemd/systemd-bootx64.efi

Boot Loader Binaries:
      ESP: /boot (/dev/disk/by-partuuid/fcdcd89e-9f6f-b6b1-b51f-5922871bf933)
      File: /EFI/systemd/systemd-bootx64.efi (systemd-boot 231)
      File: /EFI/BOOT/bootx64.efi  (systemd-boot 231)

Boot Loader Binaries in EFI Variables:
      Title: Linux Boot Manager
      ID: 0x0001
      Status: active, boot-order
      Partition: /dev/disk/by-partuuid/fcdcd89e-9f6f-46b1-b51f-5922871bf933
      File: /EFI/systemd/systemd-bootx64.efi

Default Boot Entry:
      title: Arch Linux
      linux: /vmlinuz-linux
      initrd: /intel-ucode.img  /initramfs-linux.img
      options: root=PARTUUID=86d0f097-64b2-4de8-8aee-d9cea1c78b79 rw

pacman version is v5.1.1 - libalpm v11.0.1
linux version is 4.18.6 (both uname -r and pacman -Qi linux)

Any help will be appreciated. Thanks.

PS -The issue started a lot earlier than now. I had gone home in September last year, came back after a month and the machine booted in emergency mode. I was too busy at that time to give time to fix it, so I am posting now.

Last edited by Evergreen (2019-01-17 18:54:10)

bugsmanagement

Member

Registered: 2017-04-21

Posts: 201

Re: Archlinux booting in emergency mode

Hello there,

This post looks like a failing drive to me, have you run smartctl -a on that device? From that output, couldn't tell which device it is.

Regards

bluetechgirl

Member

Registered: 2019-01-14

Posts: 18

Re: Archlinux booting in emergency mode

This could be either the drive is going bad or one of the partitions is severely corrupt. Boot from a live Linux OS and run fsck while the drives are unmounted to detect file system errors in addition to running smartctl -a like bugsmanagement said. I had to deal with both issues and found I/O errors could mean either is possible.

bugsmanagement

Member

Registered: 2017-04-21

Posts: 201

Re: Archlinux booting in emergency mode

I/O errors could mean either is possible.

Interesting, I've had multiple failed drives in my experience (eg. drops). Though at the 'ata' level? Failed drive doesn't necessarily mean bad sectors, could be a bad controller? However, I'll definitely keep that in mind.

Regards

bluetechgirl

Member

Registered: 2019-01-14

Posts: 18

Re: Archlinux booting in emergency mode

I/O errors could mean either is possible.

Interesting, I've had multiple failed drives in my experience (eg. drops). Though at the 'ata' level? Failed drive doesn't necessarily mean bad sectors, could be a bad controller? However, I'll definitely keep that in mind.

Regards

I/O errors are always drive related, but not always a drive failure and not always partition corruption. Sometimes it is a bad controller, although I have yet to experience that. I have had partition corruption that caused file corruption instead of file system corruption, but sometimes it does in fact cause bad sectors. I had issues where a failed windows 10 update that caused boot failure that meant using a restore point, installing the bad update again so it would allow me to block it, then uninstalling the update again would sometimes cause minor file corruption in Linux when I was dual booting. Also had times where more power cycling than usual would caused minor file system corruption that could still be recovered from. There was one time where I was very reckless in resizing my partitions and that caused a lot of irrecoverable damage. Recently I had a drive failure that didn't cause any corruption at all, but instead caused my computer to crash when reading from it even while in Linux (Linux was installed to my SSD), in addition to reading from it it would cause load screeching noises when doing so. I keep getting really good examples of the importance of backups, which luckily I keep.

The best thing to do in this case is to check for the smart status in addition to non hardware related corruption and also to check if the controller is bad (IDK how to do that since again I have yet to run into a bad controller).

Evergreen

Member

Registered: 2016-08-14

Posts: 16

Re: Archlinux booting in emergency mode

smartctl -a /dev/sda
https://paste.pound-python.org/show/zPT … cWCPaGhLk/

smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.20.0-arch1-1-ARCH] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.14 (AF)
Device Model:     ST1000DM003-1ER162
Serial Number:    S4Y2CQ31
LU WWN Device Id: 5 000c50 0803a083d
Firmware Version: CC45
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Form Factor:      3.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Jan 18 12:39:57 2019 UTC
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: 		(   80) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No 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: 	 ( 101) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x1085)	SCT Status 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   095   084   006    Pre-fail  Always       -       23543186
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   099   099   020    Old_age   Always       -       1435
  5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   079   060   030    Pre-fail  Always       -       91013258
  9 Power_On_Hours          0x0032   081   081   000    Old_age   Always       -       16719
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   020    Old_age   Always       -       1434
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       3059
188 Command_Timeout         0x0032   100   099   000    Old_age   Always       -       0 2 3
189 High_Fly_Writes         0x003a   095   095   000    Old_age   Always       -       5
190 Airflow_Temperature_Cel 0x0022   070   058   045    Old_age   Always       -       30 (Min/Max 22/31)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1
193 Load_Cycle_Count        0x0032   025   025   000    Old_age   Always       -       150718
194 Temperature_Celsius     0x0022   030   042   000    Old_age   Always       -       30 (0 18 0 0 0)
197 Current_Pending_Sector  0x0012   035   035   000    Old_age   Always       -       10792
198 Offline_Uncorrectable   0x0010   035   035   000    Old_age   Offline      -       10792
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       9833h+34m+45.334s
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       15554341122
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       174975903770

SMART Error Log Version: 1
ATA Error Count: 3060 (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 3060 occurred at disk power-on lifetime: 16719 hours (696 days + 15 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 ff ff ff 4f 00      01:30:46.926  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      01:30:46.925  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      01:30:46.924  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      01:30:46.924  IDENTIFY DEVICE
  ef 03 46 00 00 00 a0 00      01:30:46.924  SET FEATURES [Set transfer mode]

Error 3059 occurred at disk power-on lifetime: 16719 hours (696 days + 15 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 ff ff ff 4f 00      01:30:43.270  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      01:30:43.211  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      01:30:43.210  READ FPDMA QUEUED
  60 00 68 88 47 4b 40 00      01:30:43.184  READ FPDMA QUEUED
  60 00 80 00 47 4b 40 00      01:30:43.184  READ FPDMA QUEUED

Error 3058 occurred at disk power-on lifetime: 16719 hours (696 days + 15 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 f8 ff ff ff 4f 00      01:30:37.098  READ FPDMA QUEUED
  60 00 68 88 e7 15 40 00      01:30:37.072  READ FPDMA QUEUED
  60 00 80 00 e7 15 40 00      01:30:37.072  READ FPDMA QUEUED
  60 00 f8 00 e6 15 40 00      01:30:37.071  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      01:30:37.054  READ FPDMA QUEUED

Error 3057 occurred at disk power-on lifetime: 16719 hours (696 days + 15 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 f8 ff ff ff 4f 00      01:30:33.395  READ FPDMA QUEUED
  60 00 78 ff ff ff 4f 00      01:30:33.395  READ FPDMA QUEUED
  60 00 30 ff ff ff 4f 00      01:30:33.395  READ FPDMA QUEUED
  60 00 10 ff ff ff 4f 00      01:30:33.395  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      01:30:33.395  READ FPDMA QUEUED

Error 3056 occurred at disk power-on lifetime: 16719 hours (696 days + 15 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 53 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455

  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 38 08 33 40 00      01:27:53.321  READ FPDMA QUEUED
  61 00 10 ff ff ff 4f 00      01:27:53.320  WRITE FPDMA QUEUED
  60 00 08 18 08 33 40 00      01:27:53.319  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      01:27:53.319  READ FPDMA QUEUED
  60 00 68 ff ff ff 4f 00      01:27:53.319  READ FPDMA QUEUED

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.

fsck /dev/sda1

fsck from util-linux 2.33
fsck.fat 4.1 (2017-01-24)
/dev/sda1:  204 files, 17224/178846 clusters

fsck /dev/sda2 . Also same output for  /dev/sda4 and /dev/sda5 and /dev/sda9.

fsck from util-linux 2.33

fsck /dev/sda3

fsck from util-linux 2.33
e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superlock invalid, trying backup blocks...
fsck.etx2: bad magic number in super-block while trying to open /dev/sda3

The superblock could notbe read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem ( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
   e2fsck -b 8193 <device>
or
   e2fsck -b 32768 <device>

fsck /dev/sda6

fsck fro util-linux 2.33
e2fsck 1.44.5 (15-Dec-2018)
/dev/sda6: clean, 296502/2444624 files, 2015442/9765632 blocks

fsck /dev/sda7

fsck fro util-linux 2.33
e2fsck 1.44.5 (15-Dec-2018)
/dev/sda7: clean, 4683/732960 files, 2292023/2929664 blocks

fsck /dev/sda8

ata1.00:   exception Emask 0x0 SAct 0x60000 SErr 0x0 action 0x0
ata1.00:   irq_stat 0x40000008
ata1.00:   failed command : READ FPDMA QUEUED
ata1.00:   cmd 60/08:88:00:80:54/00:00:3f:00:00/40 tag 17 ncq dma 4096 in
                res   43/40:08:00:80:54/00:00:3f:00:00/00 Emask 0x408 (media error) . <F>
ata1.00:   status:   {DRDY SENSE ERR}
ata1.00:   error:     { UNC }
print_req_error:   I/O error, dev sda, sector 1062502400
Buffer I/O error on dev sda8, logical block 256, async page read

there were some interactive questions like "ignore error" and "force rewrite". I mistakenly pressed yes for both, only wanted to say yes for the first. But somehow it took yes for both questions and now, it's no longer asking those questions. Instead towards the end it's saying

e2fsck 1.44.5 . (15-Dec-2018)
/dev/sda8: clean, 118722/21364736 files, 56996340/85449216 blocks

but the ata errors keep on coming.

fsck /dev/sda10

fsck from util-linux 2.33
e2fsck 1.44.5 (15-Dec-2018)
/dev/sda10: clean, 11/6119424 files, 432107/24463872 blocks

I am running a dual boot windows 10 on this system and that is running fine for now. Since the hdd looks like a single device, is it possible it is failing in the linux installation while the windows installation has shown no such faults?

I'll take a data backup. Sorry I didn't mention that I haven't done it yet. Hopefully I did not overwrite stuff by answering yes in the fsck "force rewrite?" interactive question.

Edit: Not able to mount /home. So how do I take data backup?

Last edited by Evergreen (2019-01-18 10:32:44)

dmartins

Member

Registered: 2006-09-23

Posts: 360

Re: Archlinux booting in emergency mode

It looks like that disk is failing, or at least has some bad sectors where sda8 lives.

Run SMART tests on the disk. Start with a short test, and then if it passes, a long test:
smartctl -t short /dev/sda
smartctl -t long /dev/sda

The progress of the test can be seen with smartctl -l selftest /dev/sda (smartctl -a also shows it)

Check out the testdisk utility. It may provide some useful information. It may even be able to repair the partition or pull some files off of it.

I supposed to could be a bad cable, connector, or power supply, but it doesn't seem likely as the error is on the same sector each time. If you want to rule this out, connect the drive to another computer - don't use the same SATA cable.

Good luck!

frostschutz

Member

Registered: 2013-11-15

Posts: 1,658

Re: Archlinux booting in emergency mode

197 Current_Pending_Sector  0x0012   035   035   000    Old_age   Always       -       10792
198 Offline_Uncorrectable   0x0010   035   035   000    Old_age   Offline      -       10792

This drive is dying or dead already. Get a new one. If you still need to backup data, ddrescue is your only hope. (Don't do fsck, badblocks, smart selftest anymore... you already know it's a goner.)

Evergreen

Member

Registered: 2016-08-14

Posts: 16

Re: Archlinux booting in emergency mode

Thanks everyone. I am away right now and shall be able to try ddrescue  and other things next week. I'll update when I have tried.