Can't Boot Anymore

I only have /home on XFS, in any case hot to unmount it and use xfs_repair on it please?
Thank you.

you can see what is mounted with


It probably is not mounted at the moment (because in emergency mode).

OK, what’s the target syntax to use with xfs_repair please?


From the screen shot you seem to have typed the password of the user “root” and logged in successfully.
[li]Type “umount /dev/sda4”.[/li][li]Check that, the unmount was successful with “lsblk --fs” and “findmnt”.[/li][li]Execute “xfs_repair /dev/sda4” – the default repair should be sufficient.[/li][LIST]
[li]If it isn’t, please check “man xfs_repair” and re-execute the XFS repair procedure with the appropriate additional option.[/li][/ul]

[li]If the repair was successful, “systemctl reboot” …[/li][/LIST]

Reading the man page, the simplest call is

xfs_repair /dev/sda4

I can now mount /home and boot normally, but I had to use xfs_repair -L.

  1. How do I check I haven’t wrecked anything or lost any files in my /home please?
  2. Also, it happened outta the blue, not even after an update, can I find the cause somehow?

Thank you.

I assume you can only check if you lost something by compaireing with your backup.

No idea why it happened. Sometimes a power outage on the wrong moment is the culprit. Of course also disk failure (maybe run smartctl).

If you haven’t been regularly backing up your user’s directories, no chance …

You haven’t mentioned anything about the affected system –

  • The age of the disk(s) …
  • Whether or not you’ve been taking care to occasionally inspect the S.M.A.R.T. data – the results of the checks that disk hardware performs to detect any end-of-life issues …
  • Whether or not the hardware has suffered any physical or electrical “events” – physical shock due to being dropped on a hard surface – electrical damage due to voltage spikes such as lightning strikes or power supply surges …
  • Creatures inside the hardware’s case – cockroaches are a frequent cause of trouble because, they’re moist and therefore cause short circuits as they move around on the hardware components …

Fairly old notebook (in my sig) updated last year with a brand new SSD, no hardware issues (SMART doesn’t report any and neither does the checkup in the BIOS), no power outages, just happened this morn at boot, worked up to yesterday night.

Documents all backed up, gonna overwrite them all now, but is there a way to check if anything else in /home has been lost, like configs or preferences maybe?

Is the systemd “fstrim.timer” service enabled?

  • Please note that, the “btrfs-trim.service” will only trim mount points which are Btrfs – to enable the TRIM capability of XFS, you have to use the more generic systemd service …

All files includes all configuraion files and that includes all preferences.

Bear with me please: how do I check which SSD trim service is actually running? Thanks.

I’ve written all documents, not all files, I’m not backing up the whole partition.

Well, rather obvious, files you did not backup, you can not restore.

 > systemctl list-unit-files | grep -i 'trim'
btrfs-trim.service                                                     static   
fstrim.service                                                         static   
btrfs-trim.timer                                                       masked   
fstrim.timer                                                           disabled 

The services are “static” – meaning they’ll be started when called …
You have to enable at least one of the “timer” items – in your case at least the “fstrim.timer” –

 # systemctl enable fstrim.timer

You can also start an fstrim service manually –

 # systemctl start fstrim.service

You can check the progress of the TRIM by checking the status of the service –

 # systemctl status fstrim.service

Checking the status of a timer will indicate when the next time when TRIM will be executed …

I have a Gigabyte GA-AB350 Gaming 3 mobo. Usually when i boot up, the Gigabyte logo appears and I’m able to press delete to get into the bios.
Now it boots straight into windows and I can’t access the BIOS. I did not enable fast boot or anything. It just stopped showing the logo randomly.

Thank you, appreciated.

Note that courrpted files may show up in Lost&found. They may or may not be recoverable but at least you may see the names

The file names in “lost+found” are just numbers (the “inode” number of the recovered file). So that’s not much help for seeing names. As far as I know, a “btrfs” file system does not have a “lost+found” directory. I don’t think “xfs” uses “lost+found” either.