been using it fine till this morning.
Failed to start File system check on dev/disk/by-uuid/3ef36a22-e5d4-43db-94bf-89203f2f755a.
With the recent version of endeavour os, do I approach this any differently from what is done in 2023 below?
Failed to start file system check - General system / Newbie - EndeavourOS
It sounds like I should make an attempt to backup files before I do anything.
You might try booting with the EndeavourOS Live ISO, then running this and sharing the output:
lsblk -f
What we’re looking for, is the UUID for the drive you’re having issues with. It may or may not match. If it doesn’t match, that’s the culprit.
The other thing to check would be your physical connectivity, but as you say this happened after a software update, I’m less inclined to suspect that, but keep it in mind all the same.
What sort of drive is it? SATA or M.2?
The original installation software is not the current version of endeavour os, but has gone through many updates since initial install.
Is there a way to check for the output on the computer?
If so, I should try recovery first?
Sorry @Peas_n_Carrots, I’m not sure I follow what you’re saying here.
Are you suggesting that you can’t boot using the Live ISO?
I’m saying the iso would be old…
but updates would have potentially patched that on the computer itself?
At the moment, my suggested use of the Live ISO has so far been purely investigative, so an old ISO is likely going to be fine.
If it comes to re-installing, then sure, I would suggest updating it.
The UUID there, 3ef36a22-e5d4-43db-94bf-89203f2f755a, looks to match, so no issue there.
Can you run this and share the link it generates please:
sudo smartctl --all /dev/sda | eos-sendlogon the iso again?
If I understand your situation correctly, your system is failing to boot?
If so, yes, all actions are on the live ISO.
failed
You’re going to need to express yourself more clearly than that, if we’re going to be able to help you @Peas_n_Carrots.
What “failed”?
smartctl?eos-sendlog?What errors did it fail with?
actually, i think i see a dpaste link now.
187 Reported_Uncorrect 0x0032 087 087 000 Old_age Always - 15
Your drive is reporting 15 critical, uncorrectable failures.
SMART 187: Reported_Uncorrect
Number 187 reports the number of reads that could not be corrected using hardware ECC. Drives with zero uncorrectable errors hardly ever fail. This is one of the SMART stats we use to determine hard drive failure; once SMART 187 goes above zero, we schedule the drive for replacement.
Based on that, I’d recommend backing up all data important to you, currently on that drive, and retiring the drive.
Edit: After performing a backup, you can perform more in-depth tests using:
smartctl -t long /dev/sda
Performing any tests before a backup could be dangerous. Until the backup is taken, all access to the drive should be avoided.
oh my, I’ll start backup right away.
thank you
Hopefully everything is ok. After the backup, let us know how that long test goes (expect it to take a while).
will do…
weirdly enough it just let me in, though any other time i turned it on, it would not start the main os.
def starting backup though.
I’d recommend performing the backup from the Live ISO environment. This will reduce load on the drive, and ensure you’re in an environment that doesn’t have any potential corruption.