Slow startup on one of my Manjaro desktops.

On booting my Manjaro gets to the first appearance of the cursor then instead of the desktop appearing as usual it says.

A start job is running for /devdisk/by-uuid (xxs /1 min 30s)

The countdown takes 1 min 30s before the Desktop pops up screen.

Any one know how to switch this off?

I had added K3B and put XFburn on the desktop maybe that caused it. It has not happened on my other machine as I am running on three at a time.

Interesting I have found the terminal does not use apt or get but another to install software.

When I put "A start job is running for /devdisk/by-uuid" into a search engine, I get hundreds of results back with explanations and potential solutions.

It's a systemd issue. Is swap being mounted in /etc/fstab or have you changed UUIDs for drives recently? You can run to see the log entries to help troubleshoot.

Yes. I made a new drive yesterday SSD with great difficulty as Manjaro kept losing the grub even though it installed without errors.

I put Lite 4.8 as a first install shrank to leave space for 2 more equal partitions unallocated installed Manjaro then the grub did not work so I installed Fedora. So then I had three distros.

The Fedora grub had all three but Manjaro refused to boot. I deleted the Manjaro centre partition then reinstalled Manjaro. Then I had the Manjaro grub and all work OK except this delay start up for Manjaro.

I did as you suggested the Terminal says:

-- Logs begin at Fri 2020-01-24 09:40:18 GMT, end at Fri 2020-01-24 16:35:22 GM>
Jan 24 15:19:53 barry-pc kernel: Linux version 5.4.13-3-MANJARO (builduser@deve>
Jan 24 15:19:53 barry-pc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4-x86>
Jan 24 15:19:53 barry-pc kernel: KERNEL supported cpus:
Jan 24 15:19:53 barry-pc kernel: Intel GenuineIntel
Jan 24 15:19:53 barry-pc kernel: AMD AuthenticAMD
Jan 24 15:19:53 barry-pc kernel: Hygon HygonGenuine
Jan 24 15:19:53 barry-pc kernel: Centaur CentaurHauls
Jan 24 15:19:53 barry-pc kernel: zhaoxin Shanghai
Jan 24 15:19:53 barry-pc kernel: random: get_random_u32 called from bsp_init_am>
Jan 24 15:19:53 barry-pc kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 >
Jan 24 15:19:53 barry-pc kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE >
Jan 24 15:19:53 barry-pc kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX >
Jan 24 15:19:53 barry-pc kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[>
Jan 24 15:19:53 barry-pc kernel: x86/fpu: Enabled xstate features 0x7, context >
Jan 24 15:19:53 barry-pc kernel: BIOS-provided physical RAM map:
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000>
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000>
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x00000000000e0000-0x000000000>
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x0000000000100000-0x000000008>
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x000000008d029000-0x000000008>
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x000000008d059000-0x000000008>
Jan 24 15:19:53 barry-pc kernel: BIOS-e820: [mem 0x000000008d31c000-0x000000008>

Cannot see a clue here?