Jtdcftul

I've got a fresh install of Ubuntu 18.04.2 server that takes over an hour to boot. I've looked into a few possible causes but haven't found anything definitive yet.

I'm using the new ubiquity installer with guided-lvm over the entire disk. I manually created a swap partition and activated it after the install finished. I tried the same setup on a VM with no issues, so I don't think it's the problem described in these links:

• https://www.hiroom2.com/2018/05/01/ubuntu-1804-lvm-swap-wait-for-root-en/


• https://tinycp.com/community/show/solved-print-req-error-i-o-error-dev-fd0-sector-0,43.html


• https://ubuntuforums.org/showthread.php?t=2390618&page=2

systemd-analyze blame shows:

     18.661s apt-daily.service

     10.376s systemd-udev-settle.service

     10.260s dev-mapper-ubuntux2dx2dvgx2dsystemx2dx2dlv.device

      9.639s cloud-init-local.service

      9.214s snapd.service

      7.875s lxd-containers.service

systemd-analyze shows:

Startup finished in 1h 2min 5.017s (kernel) + 1min 7.007s (userspace) = 1h 3min 12.024s

After POST, the normal messages fly by and then every 23 seconds I get this message:

Mar  7 15:02:19 server kernel: [   81.401001] floppy: error 10 while reading block 0

Mar  7 15:02:19 server kernel: [  104.223783] print_req_error: I/O error, dev fd0, sector 0

Mar  7 15:02:19 server kernel: [  104.224975] floppy: error 10 while reading block 0

Mar  7 15:02:19 server kernel: [  127.323255] print_req_error: I/O error, dev fd0, sector 0

until 3725 seconds, when the system finally mounts the filesystem:

Mar  7 15:02:19 server kernel: [ 3723.824233] print_req_error: I/O error, dev fd0, sector 0

Mar  7 15:02:19 server kernel: [ 3723.825351] floppy: error 10 while reading block 0

Mar  7 15:02:19 server kernel: [ 3724.161930] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)

Mar  7 15:02:19 server kernel: [ 3725.524789] ip_tables: (C) 2000-2006 Netfilter Core Team

The machine is and AMD FX-4100 on an AM3+ GA-78LMT-S2, if that helps. I didn't see any option to disable a floppy controller as I skimmed through the BIOS options.

Why haven't I blacklisted the floppy driver? Well, I'm a bit reluctant to try it since the end-to-end time to run a test is obviously 1 hour. I thought I'd ask here and see if I can pin down the root cause before trying the "blacklist everything" approach.