Raspberry Pi 3 B fails to boot into Raspbian full

[AlekEagle]

I'm pretty sure I did something very wrong to my raspberry pi but now when ever I go to boot into Raspbian it will load everything normally until I hit "Starting Show Plymouth Boot Screen" then it lags very badly, though after a while of waiting for something to happen, it will eventually get to the "Welcome to the Raspberry Pi Desktop Powered by Raspbian", but it gets stuck there with the picture and in the corner a flashing cursor and it saying "systemd-hostnamed.service" At that point I get impatient and unplug the power. when p plug it back in I get met with it either doing the same thing, or it saying "You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to give root password for maintenance (or press Control-D to continue):" What have I done to cause this?
I'm using a Raspberry Pi 3 B with what I believe is the newest version of Raspbian.

[AlekEagle]

Ok this may just be me but I may have found the problem here is what I found in journalctl -xb

Code: Select all

-- The start-up result is done.
Mar 24 09:56:53 AlekEagleRPi kernel: random: crng init done
Mar 24 09:57:53 AlekEagleRPi systemd-udevd[158]: seq 842 '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0' is taking a long time
Mar 24 09:58:21 AlekEagleRPi systemd[1]: dev-mmcblk0p6.device: Job dev-mmcblk0p6.device/start timed out.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: Timed out waiting for device dev-mmcblk0p6.device.
-- Subject: Unit dev-mmcblk0p6.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dev-mmcblk0p6.device has failed.
-- 
-- The result is timeout.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: Dependency failed for /boot.
-- Subject: Unit boot.mount has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit boot.mount has failed.
-- 
-- The result is dependency.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit local-fs.target has failed.
-- 
-- The result is dependency.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: Dependency failed for File System Check on /dev/mmcblk0p6.
-- Subject: Unit systemd-fsck@dev-mmcblk0p6.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit systemd-fsck@dev-mmcblk0p6.service has failed.
-- 
-- The result is dependency.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: systemd-fsck@dev-mmcblk0p6.service: Job systemd-fsck@dev-mmcblk0p6.service/start failed with result 'dependency'.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: dev-mmcblk0p6.device: Job dev-mmcblk0p6.device/start failed with result 'timeout'.
Mar 24 09:58:21 AlekEagleRPi systemd-udevd[185]: Process '/bin/systemctl start bluealsa.service' failed with exit code 1.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: dev-serial1.device: Job dev-serial1.device/start timed out.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: Timed out waiting for device dev-serial1.device.
-- Subject: Unit dev-serial1.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dev-serial1.device has failed.
-- 
-- The result is timeout.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: dev-serial1.device: Job dev-serial1.device/start failed with result 'timeout'.
Mar 24 09:58:21 AlekEagleRPi systemd[1]: Starting Preprocess NFS configuration...
-- Subject: Unit nfs-config.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nfs-config.service has begun starting up.

Could it be my bluetooth adapter (the on-board bluetooth adapter stopped being detected when I reinstalled with NOOBS with my adapter plugged-in)
and shortly after the unit bluetooth.target finished starting up emergency.service came to life

[AlekEagle]

My Bluetooth adapter was the one causing all the trouble with booting, I don't quite know why though. I simply need to remove the adapter before I boot the system.

[dhruvvyas90]

I'm facing the same error messages. It seems that RPi gets stuck there but when I press enter, it just recovers from it and boots up. Has anyone found a solution to that error message ?

[DirkS]

I'm facing the same error messages. It seems that RPi gets stuck there but when I press enter, it just recovers from it and boots up. Has anyone found a solution to that error message ?

Yes, remove the BT dongle as the OP found out
If you don't have a BT dongle inserted you should start a new topic and describe your system OS, model Pi, exact error msgs, what you have tried already, etc