Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  (solved) mdadm errors after last D-U  (Read 3735 times)

Offline dion

  • User
  • Posts: 38
(solved) mdadm errors after last D-U
« on: 2017/10/27, 17:12:06 »
Hi all,


After the last D-U, about a week ago, I get a long list of the same message during boot:


"mdadm: no arrays found in config or automatically"


then one message: error opening /dev/md?* ... plus something (disappeared too fast to write it down)


This delays the boot process quite a bit. Is there a solution?
I remember the D-U installing a new version of grub in the MBR. Maybe this has something to do with it?


Thanks!
« Last Edit: 2017/12/26, 11:50:28 by piper »

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: mdadm errors after last D-U
« Reply #1 on: 2017/10/27, 17:38:03 »
If you don't use it (mdadm)

apt purge mdadm
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #2 on: 2017/10/27, 21:28:09 »
@piper: I purged mdadm. Now during the boot process, I see a blinking cursor in the top left corner of the screen but the boot process pauses just as long as before. So even though I have a SSD, siduction boot takes over 30 seconds. This was not the case before.

Offline piper

  • User
  • Posts: 1.785
  • we are the priests ... of the temples of syrinx
Re: mdadm errors after last D-U
« Reply #3 on: 2017/10/27, 22:06:44 »
You have to find out what " error opening /dev/md?*" is, logs would be helpful, I am probably the only one without a SSD so I can't help with that
Free speech isn't just fucking saying what you want to say, it's also hearing what you don't want to fucking hear

I either give too many fucks or no fucks at all, it's like I cannot find a middle ground for a moderate fuck distribution, it's like what the fuck

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #4 on: 2017/10/27, 22:16:23 »
Which log would you need? @piper

Offline OppaErich

  • OLE
  • User
  • Posts: 381
Re: mdadm errors after last D-U
« Reply #5 on: 2017/10/28, 13:23:24 »
SSD ? I thought is is something for RAID stuff, 'Multiple Devices ADMin' or so. Something seems to pull this in. I've purged this twice and it's there again.

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.838
Re: mdadm errors after last D-U
« Reply #6 on: 2017/10/28, 15:02:49 »
Let's  get the confusion out of this. It does not matter if SSD or HDD. Something is prolonging boot. Checking the journal for the delay might help.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.345
    • Land of the Buckeye
Re: mdadm errors after last D-U
« Reply #7 on: 2017/10/28, 15:43:23 »

Code: [Select]
don@Hibiscus:~$ systemd-analyze blame > boot.txt

On my KDE desktop system, it begins like this:


Code: [Select]
10.372s networking.service
          2.852s cron-daily.service
          1.234s mnt-DATA.mount
          1.112s dnsmasq.service
          1.096s dev-sdb1.device
           987ms keyboard-setup.service
           830ms systemd-journal-flush.service
           483ms systemd-hwdb-update.service
           372ms systemd-udevd.service
           330ms ModemManager.service
           309ms libvirtd.service
           278ms systemd-modules-load.service
           276ms lvm2-monitor.service
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #8 on: 2017/10/28, 21:46:20 »
boot.txt here reads like this:


Code: [Select]
         2.984s NetworkManager-wait-online.service
           802ms nfs-server.service
           516ms udisks2.service
           447ms apt-daily.service
           317ms apt-daily-upgrade.service
           262ms lvm2-monitor.service
           259ms dev-sda5.device
           250ms systemd-journal-flush.service
           172ms systemd-fsck@dev-disk-by\x2duuid-8d413a0a\x2d61a5\x2d4b97\x2d9e8c\x2d4480c2a6f43d.service
           151ms systemd-fsck@dev-disk-by\x2duuid-26dd6ee1\x2d46db\x2d4884\x2d8237\x2d9c41412c8d89.service
           117ms systemd-fsck@dev-disk-by\x2duuid-68cac8fc\x2d922a\x2d4a52\x2d86c9\x2d78d6154e03aa.service
           112ms ModemManager.service
           108ms systemd-modules-load.service
            94ms accounts-daemon.service


So I don't see any long delay times at all here. The blinking cursor appears for at least 30 seconds.
« Last Edit: 2017/10/29, 11:20:18 by dion »

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.345
    • Land of the Buckeye
Re: mdadm errors after last D-U
« Reply #9 on: 2017/10/28, 23:56:15 »
OK if it's not the base OS, then the issue is related to your DE and/or graphics driver and hardware, or some user-level service or autostart script.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #10 on: 2017/10/29, 10:55:24 »
I edited the grub replacing 'quiet' with 'text' so that I can see what's happening.


I found two time-consuming processes:


Code: [Select]
Begin: Running /scripts/local-block/ .... done

and then a bit later:


Code: [Select]
[drm] RC6 on progress on 1 disk

Output of dmesg:


Code: [Select]
...

[    2.575722] usb 1-9: New USB device found, idVendor=0bda, idProduct=0165
[    2.576280] usb 1-9: New USB device strings: Mfr=1, Product=6, SerialNumber=3
[    2.576838] usb 1-9: Product: Smart Card Reader Interface
[    2.577387] usb 1-9: Manufacturer: Generic
[    2.577931] usb 1-9: SerialNumber: 20070818000000000
[    2.736093] usb 1-10: new high-speed USB device number 5 using xhci_hcd
[    2.907330] usb 1-10: New USB device found, idVendor=058f, idProduct=6377
[    2.907893] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.908450] usb 1-10: Product: Mass Storage Device
[    2.908997] usb 1-10: Manufacturer: Generic
[    2.909543] usb 1-10: SerialNumber: 920321111113
[    2.910582] usb-storage 1-10:1.0: USB Mass Storage device detected
[    2.911360] scsi host7: usb-storage 1-10:1.0
[    3.935849] scsi 7:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
[    3.936928] scsi 7:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
[    3.937970] scsi 7:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
[    3.939031] scsi 7:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
[    3.941651] sd 7:0:0:0: [sde] Attached SCSI removable disk
[    3.955337] sd 7:0:0:3: [sdh] Attached SCSI removable disk
[    3.955713] sd 7:0:0:1: [sdf] Attached SCSI removable disk
[    3.956483] sd 7:0:0:2: [sdg] Attached SCSI removable disk
[   33.626231] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   33.699689] NET: Registered protocol family 10
[   33.703626] Segment Routing with IPv6
[   33.705987] ip_tables: (C) 2000-2006 Netfilter Core Team
[   33.710738] systemd[1]: systemd 235 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid)
[   33.711423] systemd[1]: Detected architecture x86-64.
[   33.713596] systemd[1]: Set hostname to <siductionbox>.
[   33.760092] systemd[1]: getty.target: Wants dependency dropin /etc/systemd/system/getty.target.wants/getty@tty1.service target /lib/systemd/system/autovt@.service has different name
[   33.773050] systemd[1]: Created slice System Slice.
[   33.773980] systemd[1]: Mounting RPC Pipe File System...
[   33.774704] systemd[1]: Listening on LVM2 metadata daemon socket.
[   33.775467] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[   33.777102] systemd[1]: Listening on Process Core Dump Socket.
[   33.777929] systemd[1]: Created slice system-getty.slice.
[   33.782304] RPC: Registered named UNIX socket transport module.
[   33.782304] RPC: Registered udp transport module.
[   33.782305] RPC: Registered tcp transport module.
[   33.782305] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   33.788166] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   33.805286] EXT4-fs (sda5): re-mounted. Opts: (null)
[   33.806011] lp: driver loaded but no devices found
[   33.808005] ppdev: user-space parallel port driver
[   33.809583] parport_pc 00:01: reported by Plug and Play ACPI
[   33.809649] parport0: PC-style at 0x378, irq 5 [PCSPP]
[   33.824627] systemd-journald[530]: Received request to flush runtime journal from PID 1
[   33.899045] lp0: using parport0 (interrupt-driven).
[   33.899045] lp0: console ready
[   33.901927] loop: module loaded
[   33.923129] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input5
[   33.923686] ACPI: Sleep Button [SLPB]
[   33.924865] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input6
[   33.925809] ACPI: Power Button [PWRB]
[   33.926386] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input7
[   33.927447] ACPI: Power Button [PWRF]
[   33.943007] Bluetooth: Core ver 2.22
[   33.943631] NET: Registered protocol family 31
[   33.944163] Bluetooth: HCI device and connection manager initialized
[   33.944697] Bluetooth: HCI socket layer initialized
[   33.945267] Bluetooth: L2CAP socket layer initialized
[   33.945828] Bluetooth: SCO socket layer initialized
[   33.954522] Bluetooth: HCI UART driver ver 2.3
[   33.955040] Bluetooth: HCI UART protocol H4 registered
[   33.955560] Bluetooth: HCI UART protocol BCSP registered
[   33.956065] Bluetooth: HCI UART protocol LL registered
[   33.956548] Bluetooth: HCI UART protocol ATH3K registered
[   33.957034] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   33.957541] Bluetooth: HCI UART protocol Intel registered
[   33.958020] Bluetooth: HCI UART protocol Broadcom registered
[   33.958479] Bluetooth: HCI UART protocol QCA registered
[   33.958938] Bluetooth: HCI UART protocol AG6XX registered
[   33.959416] Bluetooth: HCI UART protocol Marvell registered
[   33.960212] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   33.963521] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   33.964433] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   33.965004] sr 4:0:0:0: Attached scsi generic sg2 type 5
[   33.965516] sd 5:0:0:0: Attached scsi generic sg3 type 0
[   33.966455] sd 6:0:0:0: Attached scsi generic sg4 type 0
[   33.966899] sd 7:0:0:0: Attached scsi generic sg5 type 0
[   33.967574] sd 7:0:0:1: Attached scsi generic sg6 type 0
[   33.968087] sd 7:0:0:2: Attached scsi generic sg7 type 0
[   33.968695] sd 7:0:0:3: Attached scsi generic sg8 type 0
[   33.971705] iTCO_vendor_support: vendor-support=0
[   33.976055] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   33.976595] iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
[   33.978322] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   33.986204] input: PC Speaker as /devices/platform/pcspkr/input/input8
[   33.990522] media: Linux media interface: v0.10
[   33.994707] Linux video capture interface: v2.00
[   34.004275] pwc: Logitech QuickCam 4000 Pro USB webcam detected.
[   34.005158] [drm] Memory usable by graphics device = 4096M
[   34.005579] checking generic (c0000000 500000) vs hw (c0000000 10000000)
[   34.005579] fb: switching to inteldrmfb from simple
[   34.006081] Console: switching to colour dummy device 80x25
[   34.006167] [drm] Replacing VGA console driver
[   34.012097] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   34.012100] [drm] Driver supports precise vblank timestamp query.
[   34.020244] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   34.022541] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_01.bin
[   34.022854] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)
[   34.023381] [drm] Initialized i915 1.6.0 20170619 for 0000:00:02.0 on minor 0
[   34.024651] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   34.025131] acpi device:0f: registered as cooling_device9
[   34.025187] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9
[   34.029395] intel_rapl: Found RAPL domain package
[   34.029398] intel_rapl: Found RAPL domain core
[   34.029399] intel_rapl: Found RAPL domain uncore
[   34.029417] intel_rapl: Found RAPL domain dram
[   34.059770] ath: EEPROM regdomain: 0x809c
[   34.059771] ath: EEPROM indicates we should expect a country code
[   34.059772] ath: doing EEPROM country->regdmn map search
[   34.059772] ath: country maps to regdmn code: 0x52
[   34.059773] ath: Country alpha2 being used: CN
[   34.059773] ath: Regpair used: 0x52
[   34.066247] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   34.066434] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90002660000, irq=16
[   34.074993] Adding 95392k swap on /dev/sda6.  Priority:-1 extents:1 across:95392k SSFS
[   34.081758] ath9k 0000:01:00.0 wlp1s0: renamed from wlan0
[   34.194500] pwc: Registered as video0.
[   34.194522] input: PWC snapshot button as /devices/pci0000:00/0000:00:14.0/usb1/1-8/input/input10
[   34.194563] usbcore: registered new interface driver Philips webcam
[   34.226725] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
[   34.230006] usbcore: registered new interface driver snd-usb-audio
[   34.241533] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[   34.241629] fbcon: inteldrmfb (fb0) is primary device
[   34.262161] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[   34.262161] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   34.262162] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[   34.262163] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[   34.262163] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[   34.262164] snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x19
[   34.262164] snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
[   34.262165] snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
[   34.277291] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
[   34.277315] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
[   34.277336] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
[   34.277354] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
[   34.277372] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
[   34.277391] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[   34.277409] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[   34.277427] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[   34.277446] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[   34.277463] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
[   34.292712] Console: switching to colour frame buffer device 240x67
[   34.312033] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[   34.555142] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null)
[   35.743444] [drm] RC6 on
[   82.401103] EXT4-fs (sdc4): mounted filesystem with ordered data mode. Opts: (null)
[   82.655348] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   82.656231] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw
[   82.668837] r8169 0000:02:00.0 enp2s0: link down
[   82.669369] r8169 0000:02:00.0 enp2s0: link down
[   82.670014] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   82.672533] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[   82.687638] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[   82.708568] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[   82.728727] NET: Registered protocol family 17
[   82.748021] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[   83.414022] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[   83.415800] NFSD: starting 90-second grace period (net ffffffff81cba5c0)
[   85.523384] r8169 0000:02:00.0 enp2s0: link up
[   85.523425] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[   93.559360] fuse init (API version 7.26)
[   93.893881] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   93.893883] Bluetooth: BNEP filters: protocol multicast
[   93.893885] Bluetooth: BNEP socket layer initialized
[   96.627252] rfkill: input handler disabled
[  425.027501] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[  740.034023] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 1055.045429] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready

Code: [Select]
dion@siductionbox:~$ blkid
/dev/sdb2: LABEL="Windata" UUID="DC14118014115F38" TYPE="ntfs" PARTLABEL="Windows data" PARTUUID="fa6802f1-9a4c-4b1e-9372-713c4e0661b6"
/dev/sdb3: LABEL="home" UUID="68cac8fc-922a-4a52-86c9-78d6154e03aa" TYPE="ext4" PARTLABEL="Linux data" PARTUUID="3c66ec4f-e980-48a3-b4bf-155e764821e8"
/dev/sda1: LABEL="Herstel" UUID="F49E68F59E68B1B2" TYPE="ntfs" PARTLABEL="Basi" PARTUUID="cd7531f6-2bcc-48d9-9b13-1b49a2f06907"
/dev/sda2: UUID="2068-DCA4" TYPE="vfat" PARTLABEL="EFI" PARTUUID="73443833-8b3f-4b1d-bc8b-fe2d2034fb5c"
/dev/sda4: LABEL="windows" UUID="B8706A357069FA90" TYPE="ntfs" PARTUUID="0df2e960-bf5f-46b3-a04e-f5a1a0c48dcf"
/dev/sda5: UUID="01ce6ad0-d23b-433a-9f8e-c7260b1955ee" TYPE="ext4" PARTUUID="a16ee7f6-08b3-43fc-8f32-25e628401a1d"
/dev/sda6: UUID="2605ebab-d33a-4408-b51e-bfcd421b8887" TYPE="swap" PARTUUID="d46ddd69-288e-4c67-b3c5-46d782e8a77d"
/dev/sdc1: LABEL="oldroot" UUID="666e42a0-0b61-43ec-b3e8-0af894888e4d" TYPE="ext4" PARTUUID="7a89d7e3-01"
/dev/sdc4: LABEL="HD1TB" UUID="26dd6ee1-46db-4884-8237-9c41412c8d89" TYPE="ext4" PARTUUID="7a89d7e3-04"
/dev/sdd1: LABEL="backup" UUID="8d413a0a-61a5-4b97-9e8c-4480c2a6f43d" TYPE="ext4"


Code: [Select]
dion@siductionbox:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>                           <mount point>  <type>  <options>  <dump>  <pass>
UUID=01ce6ad0-d23b-433a-9f8e-c7260b1955ee /              ext4    defaults,noatime 0       1
UUID=2605ebab-d33a-4408-b51e-bfcd421b8887 swap           swap    defaults,noatime 0       0
UUID=68cac8fc-922a-4a52-86c9-78d6154e03aa /home ext4 defaults,noatime 0 2
UUID=8d413a0a-61a5-4b97-9e8c-4480c2a6f43d /media/dion/backup ext4 defaults,noatime 0 2
UUID=26dd6ee1-46db-4884-8237-9c41412c8d89 /media/dion/HD1TB ext4 defaults,noatime 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0       0
Does this help?
« Last Edit: 2017/10/29, 11:16:18 by dion »

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #11 on: 2017/10/29, 16:47:55 »
Update: isolated the cause of the [drm] RC6 in progress on 1 disk:


Appartently a script starting up memopal (cloud backup service):


/etc/rc6.d/memopal


I disabled memopal and the second pause does not occur again.


I got messages:


Code: [Select]
root@siductionbox:/home/dion# systemctl disable memopal.service
memopal.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable memopal
insserv: warning: current start runlevel(s) (empty) of script `memopal' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `memopal' overrides LSB defaults (0 1 6).


Can these messages explain the delay?


Still the other delay persists. So any help finding the problem there is still appreciated.


Thanks!
Dion

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #12 on: 2017/12/25, 20:28:12 »
I think this problem:


http://forums.debian.net/viewtopic.php?f=5&t=133578


can be related to my first problem stated in the above.


After reinstalling siduction on my current PC, I had two swap-partitions. One on my old HDD (which I kept in my new PC) and one one the HDD of the new PC. I deleted one of the two, but maybe some process in the boot process is still looking for it?


Any clues where to look?


Thanks!
Dion

Offline dion

  • User
  • Posts: 38
Re: mdadm errors after last D-U
« Reply #13 on: 2017/12/25, 20:47:10 »
I found the problem after all. My grub contained an invalid RESUME partition. It referred to a non-existing swap partition. So I edited grub to reflect the right RESUME partition and now the system boots as fast as it should. Also the other problem with memopal is no longer happening.


So this can be marked as SOLVED.