Fix Linux Boot Error message : "a start job is running for dev-disk-by..."
 

Hire you can try, how to fix linux boot error message : "a start job is running for dev-disk-by..."

1. The first thing you need is GParted live cd, you may not use or follow the GParted partition report in your linux distro because it's some may be report wrong or deffrent partition data, so you need the live cd.

2. Boot in to GParted live cd

3. Open GParted, and see all partition


4. If you see there is partition with Boot flag, right click on it, select the "manage flags" and uncheck the "boot" flag.

5. Close the GParted and eject the live cd

5. Now your problem should be fixed, you may try to boot from your linux distro and see the error message is disappear.

This is also very usefull when we dual boot the linux distro with microsoft windows. The error message caused by the microsoft windows partition, because it was flagged "boot", just use GParted live cd and uncheck the boot flag on windows partition and the error will not be there any more.


Thankyou, Manuk_Londong na Toraya

Sorry to burst your bubble, but Linux totally ignores a partition's "boot" flag.

thankyou for the respone... i test this on my pc with multiple os ( kali linux, windows and android x86 ). i use this method to fix my kali linux error booting. Just uncheck the boot flag on linux partition and the error is gone :)

So, which is it?

Does the error return if you put the boot flag back on one of those partitions? I'd be very surprised it it did, since as far as I know there is nothing in Linux (other than the partitioning tools themselves, of course) that even looks at that boot flag.

Thankyou for the response.. Yes Sir,,, the error come when i put the boot flag on Kali Linux and Windows partitions (due to the diffrent file system type). You can put the boot flag on Android partition bacause as you can see it is support all file systems type.

I believe it incidentally worked in the OP's particular instance; how exactly I don't know. But I certainly wouldn't rank the solution among universal solutions, especially since the "message" being gotten rid of is not an error message!

Boot flag matters in Linux exactly the same as in Windows, if the MBR contains generic DOS/OS2/Windows code (including FOSS master-boot-code by whatever name from a Linux distro package) and primary boot control belongs to Windows or a Linux bootloader on a primary partition, as is the case on all my many multiboot machines.