Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Is my file system corrupting or physical fault in my HDD?

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
ekeimaja
Posts: 3
Joined: 2017-04-14 10:40

Is my file system corrupting or physical fault in my HDD?

#1 Post by ekeimaja »

I am running Debian 8 on my laptop. On saturday evening when I started my laptop, in HDD boot screen it runned the "The start job for dev-mapper" / "The start job for udev". It takes very long, and then it either boots normally or requires running systemctl default as root. If I can login normally, everything works, but I cannot download anything on Chromium (I have not other browsers installed). And if I reboot, then it prints about task job of chromium download and stops, which I bypass using Crtl+Alt+Del, and then it starts prtinting BIOS messages about clock and so on. On saturday it worked normally after I rebooted.

After Saturday, it also booted everytime without problem, but now when I started it, it started making this on every boot (x3). The laptop has been in very shaky environment inside car, so I assume it is physical failure.

User avatar
Hallvor
Global Moderator
Global Moderator
Posts: 2042
Joined: 2009-04-16 18:35
Location: Kristiansand, Norway
Has thanked: 149 times
Been thanked: 212 times

Re: Is my file system corrupting or physical fault in my HDD

#2 Post by Hallvor »

You may want to check the logs.
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD

ekeimaja
Posts: 3
Joined: 2017-04-14 10:40

Re: Is my file system corrupting or physical fault in my HDD

#3 Post by ekeimaja »

Now it keeps booting normally again, so I need to wait if it fails again. I will report then to this topic again :)

Post Reply