13

After I forcefully turned System off, and then Turned on tomorrow morning, I got :-

Failed to start default target: Transaction for graphical.target/start is destructive (emergency.target has 'start' job queued, but 'stop' is included in the transaction.

Ubuntu 20. There were no updates and i was running it fine since last 2 months. Ive tried using nomodeset but got same. In terminal, I dont see my user directory in home folder. I dont think it has something to do with UEFI as i was running it fine. Windows runs fine tho.

Can you help me understand the issue, it seems like a race condition to me.

System: Asus FX504GE , intel, Nvidia

Update: After investigating logs, I found that error occured in filesystem of home folder:-

[FAILED] Failed to start File System Check on /dev/disk/by-uuid/ <disk id>
[DEPEND] Dependency failed for /home
[DEPEND] Dependency failed for Local File Systems
Hacke
  • 428
  • 1
  • 4
  • 13

3 Answers3

15

So I finally found it. It was due to error in my file system after I saw logs. Simple solution was to run:

$ fsck /dev/diskname

In my case my home was on /dev/sda3.

But till I found solution, I had reinstalled ubuntu. I encountered same error while using the old home partition, so I issued above command. It worked!

Hacke
  • 428
  • 1
  • 4
  • 13
1

About start.default graphical failure with the "destructive" mesage etc...

I had the same problem running Kubuntu 22.04 after a power failure. I have a mixed installation with dual boot and use some ntfs3 volumes mounted at fstab. After checking all ext4 volumes with -f option from live cd, the problem continued. Finally the failure was on a ntfs3 volume. I chkdsk from Windows and Kubuntu started normally.

My deduction is that the ntfs3 volume didn't mount by not closing properly. I had some mounting problems in the past when a Windows volume stayed "unmounted" due to Windows quick start option enabled. I think this time the ntfs3 volume was wrong due to Kubuntu power off by main power failure while I was using the ntfs3 volume.

Checking all ntfs/ntfs3 volumes you mount from fstab can help discarding "start.default etc" problems. Either trying to mount them manually to check if they really can be mounted.

I hope this helps any of you.

user1876543
  • 11
  • 1
0

I launch ubuntu from an sd card. and I accidentally locked it. and it gave me this error. so I'm guessing Ubuntu does not have the info it needs to start.

but that was just me so. good luck.

August Young
  • 1