F5F Stay Refreshed Software Operating Systems This message appears when Ubuntu Linux boots and files are being cleaned. It’s a normal part of the startup process.

This message appears when Ubuntu Linux boots and files are being cleaned. It’s a normal part of the startup process.

This message appears when Ubuntu Linux boots and files are being cleaned. It’s a normal part of the startup process.

Pages (2): 1 2 Next
A
AlexOMontoya
Member
65
02-03-2025, 12:10 PM
#1
Yesterday after rebooting my PC, I received this message and even after more than 12 hours it didn<|pad|> to not boot. I searched for solutions but nothing worked. How can I fix this? I’m new to Linux and don’t have a graphics card installed. Before this issue, Linux worked fine and showed an update error. I don’t remember exactly what it said.
A
AlexOMontoya
02-03-2025, 12:10 PM #1

Yesterday after rebooting my PC, I received this message and even after more than 12 hours it didn<|pad|> to not boot. I searched for solutions but nothing worked. How can I fix this? I’m new to Linux and don’t have a graphics card installed. Before this issue, Linux worked fine and showed an update error. I don’t remember exactly what it said.

P
ProfetaGames
Junior Member
16
02-07-2025, 08:42 PM
#2
You've run the standard initial check for /dev/sda5. What steps have you attempted thus far?
P
ProfetaGames
02-07-2025, 08:42 PM #2

You've run the standard initial check for /dev/sda5. What steps have you attempted thus far?

M
MrMatthewx
Member
64
02-11-2025, 08:05 AM
#3
Repeated restarts, setting up the GDM service (which initially didn’t start)
M
MrMatthewx
02-11-2025, 08:05 AM #3

Repeated restarts, setting up the GDM service (which initially didn’t start)

B
Bring_It
Senior Member
423
02-11-2025, 09:42 AM
#4
Updated the details for clarity.
Incorporated additional context to enhance understanding.
B
Bring_It
02-11-2025, 09:42 AM #4

Updated the details for clarity.
Incorporated additional context to enhance understanding.

M
Matke04
Posting Freak
825
02-24-2025, 07:06 PM
#5
You installed GDM without starting the system and accessed single-user mode. Once you reached a mountable location, you could view /etc/fstab to see your mounts. The final steps involved running fsck, which handled the actual mounting process.
M
Matke04
02-24-2025, 07:06 PM #5

You installed GDM without starting the system and accessed single-user mode. Once you reached a mountable location, you could view /etc/fstab to see your mounts. The final steps involved running fsck, which handled the actual mounting process.

I
ImiSiS
Member
75
02-24-2025, 08:27 PM
#6
It seems you might have pressed a specific key combination, possibly to open a feature or settings menu. That could potentially resolve the issue depending on what it does.
I
ImiSiS
02-24-2025, 08:27 PM #6

It seems you might have pressed a specific key combination, possibly to open a feature or settings menu. That could potentially resolve the issue depending on what it does.

_
_TrapBoy_
Member
224
02-26-2025, 02:16 AM
#7
Sure, you can modify the last character of /dev/sda5 to 0 to prevent it from attempting checks. It should finish quickly, though the setup might still take time based on your system. Once it boots fully, you can manually run fsck if needed. What type of storage device is this, and what’s the size of the partition?
_
_TrapBoy_
02-26-2025, 02:16 AM #7

Sure, you can modify the last character of /dev/sda5 to 0 to prevent it from attempting checks. It should finish quickly, though the setup might still take time based on your system. Once it boots fully, you can manually run fsck if needed. What type of storage device is this, and what’s the size of the partition?

T
52
03-14-2025, 05:17 PM
#8
Your observation indicates ext4 reindexing the journal while encountering a problem that leads to hanging. It may be due to file system degradation or disk issues. Disconnect the system and restart in a clean environment, then perform a diagnostic check on the disk.
T
thebigcheese22
03-14-2025, 05:17 PM #8

Your observation indicates ext4 reindexing the journal while encountering a problem that leads to hanging. It may be due to file system degradation or disk issues. Disconnect the system and restart in a clean environment, then perform a diagnostic check on the disk.

Z
z_x
Junior Member
3
03-16-2025, 06:46 PM
#9
You need to check the size of the partition manually. Use a disk management tool or command line to see the details. If unsure, consult your operating system's documentation for guidance.
Z
z_x
03-16-2025, 06:46 PM #9

You need to check the size of the partition manually. Use a disk management tool or command line to see the details. If unsure, consult your operating system's documentation for guidance.

_
_Rezward_
Member
56
03-16-2025, 07:14 PM
#10
From the disk application?
_
_Rezward_
03-16-2025, 07:14 PM #10

From the disk application?

Pages (2): 1 2 Next