How to pause/unpause Linux/zorin os boot screen in Asus Laptops

How to pause the boot screen? I need this because I see some error message every time on boot. it is quick so I can't take screenshots. I assume it is hw related. maybe HDD or SSD. I need to ensure that before data loss. I can't remember fully but it is like {DRW} and some number.



What is this means ?

Your question is an example of the X - Y problem. It is not that you want to know how to pause the boot screen - it is that you want access to the error messages.

You can access the Boot Logs (and errors) with

journalctl -b

The boot screen cannot be paused because it is a running INIT process.
There is no "pause" ability anymore than you can pause the travel of electron energy through a wire...

From your screenshot - we can see that you have some Bad Sectors on the drive that question its health and integrity. I would suggest being diligent with back ups and planning ahead for a replacement drive.

1 Like

which one I have two HDD and SSD. how to check this error in the terminal so that I can be sure? is there any way to repair it?

/dev/sda shows the error.

You can use

lsblk

in terminal to ID drives and partitions.

Bad Sectors can only be set to ignore. They are often due to small physical damage to the disk itself in an HDD or due to degraded components in an SSD. They cannot be repaired - only have the data moved to a good sector and that data repaired if corrupted.

However, while a drive can last a while with bad sectors - they often can be an indicator of future troubles.
It cannot be said: It may last for years - or days.
Your best bet is to play it safe. Make back ups - as often as needed and plan ahead.

i have restored Windows/Zorin/linux many times using rescuezilla, is this the cause?
here is the test result
hasibul@hasibul-S551LN:~$ sudo smartctl -a /dev/sda
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.15.0-73-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: WD Blue and Green SSDs
Device Model: WDC WDS120G2G0A-00JH30
Serial Number: 2050A7803668
Firmware Version: UF450000
User Capacity: 120,034,123,776 bytes [120 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Mon Jun 5 13:10:36 2023 +06
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: (0x02) Offline data collection activity
was completed without error.
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: (0x11) 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.
No Selective Self-test supported.
SMART capabilities: (0x0002) Does not save 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: ( 10) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x0032 100 100 050 Old_age Always - 0
5 Reallocated_Sector_Ct 0x0032 100 100 050 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 050 Old_age Always - 10557
12 Power_Cycle_Count 0x0032 100 100 050 Old_age Always - 1265
160 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 0
161 Unknown_Attribute 0x0033 100 100 050 Pre-fail Always - 100
163 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 39
164 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 262579
165 Block_Erase_Count 0x0032 100 100 050 Old_age Always - 1887
166 Minimum_PE_Cycles_TLC 0x0032 100 100 050 Old_age Always - 316
167 Max_Bad_Blocks_per_Die 0x0032 100 100 050 Old_age Always - 441
168 Maximum_PE_Cycles_TLC 0x0032 100 100 050 Old_age Always - 5050
169 Total_Bad_Blocks 0x0032 100 100 050 Old_age Always - 92
175 Program_Fail_Count_Chip 0x0032 100 100 050 Old_age Always - 0
176 Erase_Fail_Count_Chip 0x0032 100 100 050 Old_age Always - 0
177 Wear_Leveling_Count 0x0032 100 100 050 Old_age Always - 0
178 Used_Rsvd_Blk_Cnt_Chip 0x0032 100 100 050 Old_age Always - 0
181 Program_Fail_Cnt_Total 0x0032 100 100 050 Old_age Always - 0
182 Erase_Fail_Count_Total 0x0032 100 100 050 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 050 Old_age Always - 329
194 Temperature_Celsius 0x0022 100 100 050 Old_age Always - 40
195 Hardware_ECC_Recovered 0x0032 100 100 050 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 100 100 050 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 050 Old_age Always - 0
198 Offline_Uncorrectable 0x0032 100 100 050 Old_age Always - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always - 830
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always - 100
241 Host_Writes_GiB 0x0030 100 100 050 Old_age Offline - 362550
242 Host_Reads_GiB 0x0030 100 100 050 Old_age Offline - 470731
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 385034

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 4

ATA Error Count: 0
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 0 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH


04 51 00 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name


e5 00 00 00 00 00 00 08 00:00:00.000 CHECK POWER MODE
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d5 01 06 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG

Error -1 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH


04 51 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name


b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG

Error -2 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH


04 51 00 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name


e5 00 00 00 00 00 00 08 00:00:00.000 CHECK POWER MODE
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d5 01 06 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG

Error -3 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH


04 51 00 00 00 00 00

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name


e5 00 00 00 00 00 00 08 00:00:00.000 CHECK POWER MODE
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d5 01 06 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG

Error -4 occurred at disk power-on lifetime: 0 hours (0 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 SC SN CL CH DH


04 51 00 00 00 00 00 Error: ABRT

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name


b0 d0 01 00 4f c2 00 08 00:00:00.000 SMART READ DATA
b0 d1 01 01 4f c2 00 08 00:00:00.000 SMART READ ATTRIBUTE THRESHOLDS [OBS-4]
b0 da 00 00 4f c2 00 08 00:00:00.000 SMART RETURN STATUS
b0 d5 01 00 4f c2 00 08 00:00:00.000 SMART READ LOG
b0 d5 01 01 4f c2 00 08 00:00:00.000 SMART READ LOG

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Short offline Completed without error 00% 10557 -

2 Short offline Completed without error 00% 10259 -

3 Short offline Completed without error 00% 8928 -

4 Short offline Completed without error 00% 6206 -

5 Short offline Completed without error 00% 6136 -

Selective Self-tests/Logging not supported

There are many things that can wear out an HHD or SSD. A great many things. We must always remember to consider them as a Consumable With Limited Lifespans.

i cant understand the report. is there any errors? as a general user i am so sorry to asking this like of question. thanks in advanced for your response.

You have a lot of Bad Blocks... and there is plenty in there to cause concern:

Total_Bad_Blocks 0x0032 100 100 050 Old_age Always - 92
Temperature_Celsius 0x0022 100 100 050 Old_age Always - 40
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always - 830
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always - 100
241 Host_Writes_GiB 0x0030 100 100 050 Old_age Offline - 362550
242 Host_Reads_GiB 0x0030 100 100 050 Old_age Offline - 470731
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 385034

1 Like

I have some questions but I'll start my own thread and not hijack this one .... :laughing:

1 Like

You have a lot of Bad Blocks... and there is plenty in there to cause concern:

Total_Bad_Blocks 0x0032 100 100 050 Old_age Always - 92
Temperature_Celsius 0x0022 100 100 050 Old_age Always - 40
199 UDMA_CRC_Error_Count 0x0032 100 100 050 Old_age Always - 830
232 Available_Reservd_Space 0x0032 100 100 050 Old_age Always - 100
241 Host_Writes_GiB 0x0030 100 100 050 Old_age Offline - 362550
242 Host_Reads_GiB 0x0030 100 100 050 Old_age Offline - 470731
245 Unknown_Attribute 0x0032 100 100 050 Old_age Always - 385034

would you please tell me which one? SSD (first)/HDD (second)?

I have checked for bad sectors and errors in Windows but nothing was found and everything is normal. I have used chkdsk command and diskgenius software to test bad sectors. I have reinstalled zorin but show this error. I have ssd(1st) and hdd(2nd). Zorin in ssd(1st) and HDD has no windows and it is NTFS format one partition only. need to know which HDD is problematic? Please see the video

is there any way to repair it?
Thanks.

I presume that the error you are referring to in the video is when it displays error: failure writing sector... to hd0

Again, this most often is referencing a bad sector.

One thing you could try is checking (since you are dual boot) if you are booting One OS in LEgacy (MBR) and one in EFI. They both should boot the same way.

1 Like

How can I do that? I think i found the problem.


is there any tools to repair it? like fsck?

I have reseated ssd and hdd physically and cleaned them. now this message.
Please see the updated video

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.