Announcement

Collapse
No announcement yet.

Kubuntu 23.04, Original internal fail of separate Data drive fixed, after backing up the drive, now slow to boot

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kubuntu 23.04, Original internal fail of separate Data drive fixed, after backing up the drive, now slow to boot

    Hi,

    I have 2 drives one for Kubuntu and one for all my Data.
    This morning the Data drive was not there, opened the PC case unplugged drive and reconnected drive and now fully working.

    As a precaution I backed up all of that drive data onto a external USB drive. Which was successful.

    But now if that external drive is not plugged in PC is very slow to boot waiting at the Kubuntu pulsing icon or sometimes shows me terminal with emergency text. ( If i connect the usb drive and then it can boot correctly for these. )

    When I made the USB drive I did as I always do and mounted it as media/gb/usbdrive. But I think I did change owner from root to gb ( gb is me )

    I have tried mounting it to mnt/usbdrive but still the delay on boot is there.

    So somewhere it is waiting for that usb drive but i cannot find where.

    here is fstab ( as i look at this now I have posted it should /dev/sdc1 /media/gb/usbdrive ext4 defaults 0 0 not be in the fstab ? )
    Code:
    # <file system> <mount point> <type> <options> <dump> <pass>
    
    UUID=bfb60022-0d3e-42d0-87c6-9d349bbc9922 / ext4 errors=remount-ro 0 1
    #UUID=7AE8-3325 /boot/efi vfat umask=0077 0 1
    UUID=1ab7fee0-293a-4d25-bb8d-32bde9358b2d /home ext4 defaults 0 2
    UUID=7AE8-3325 /boot/efi vfat defaults 0 1
    /dev/sdc1 /media/gb/usbdrive ext4 defaults 0 0
    /dev/sdb1 /media/gb/EXT4 ext4 defaults 0 0
    ​[/CODE]​

    here is ls /dev/disk/by-uuid -lt
    Code:
    lrwxrwxrwx 1 root root 10 Nov  7 15:17 a3235df3-bfb5-42c3-93fe-f99b0d184d4a -> ../../sda6
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 3f36a7da-f5ad-458e-b3a4-b02eb4c8d04b -> ../../sdc1
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 1ab7fee0-293a-4d25-bb8d-32bde9358b2d -> ../../sda8
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 7AE8-3325 -> ../../sda2
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 23affd00-616e-4c62-ab3d-7c81f26d3be9 -> ../../sda5
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 7288E7AD88E76DD3 -> ../../sda1
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 680AEC9A0AEC6692 -> ../../sda4
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 bfb60022-0d3e-42d0-87c6-9d349bbc9922 -> ../../sda7
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 08A9E242794B8CA0 -> ../../sdb2
    lrwxrwxrwx 1 root root 10 Nov  7 15:15 d35a3853-ab3c-4e5c-b266-64d1769bf2d6 -> ../../sdb1
    ​

    ​​

    Here is lsblk
    Code:
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
    loop0 7:0 0 4K 1 loop /snap/bare/5
    loop1 7:1 0 73.9M 1 loop /snap/core22/1663
    loop2 7:2 0 74.2M 1 loop /snap/core22/1621
    loop3 7:3 0 273.6M 1 loop /snap/firefox/5187
    loop4 7:4 0 273.6M 1 loop /snap/firefox/5239
    loop5 7:5 0 505.1M 1 loop /snap/gnome-42-2204/176
    loop6 7:6 0 504.2M 1 loop /snap/gnome-42-2204/172
    loop7 7:7 0 38.9M 1 loop /snap/gutenprint-printer-app/738
    loop8 7:8 0 91.7M 1 loop /snap/gtk-common-themes/1535
    loop9 7:9 0 38.7M 1 loop /snap/snapd/21465
    loop10 7:10 0 39.4M 1 loop /snap/gutenprint-printer-app/765
    loop11 7:11 0 38.8M 1 loop /snap/snapd/21759
    sda 8:0 0 111.8G 0 disk
    ├─sda1 8:1 0 450M 0 part
    ├─sda2 8:2 0 99M 0 part /boot/efi
    ├─sda3 8:3 0 16M 0 part
    ├─sda4 8:4 0 34G 0 part
    ├─sda5 8:5 0 28.3G 0 part
    ├─sda6 8:6 0 10.3G 0 part /media/gb/Kubuntu 21 Home1
    ├─sda7 8:7 0 29.6G 0 part /var/snap/firefox/common/host-hunspell
    │ /
    └─sda8 8:8 0 9G 0 part /home
    sdb 8:16 0 931.5G 0 disk
    ├─sdb1 8:17 0 850G 0 part /media/gb/EXT4
    └─sdb2 8:18 0 81.5G 0 part
    sdc 8:32 0 447.1G 0 disk
    └─sdc1 8:33 0 447.1G 0 part /media/gb/usbdrive
    ​


    and this from journalctl -xb
    The unit systemd-fsckd.service has successfully entered the 'dead' state.
    Nov 07 14:33:19 Mini-ITX-PC systemd[1]: dev-sdc1.device: Job dev-sdc1.device/start timed out.
    Nov 07 14:33:19 Mini-ITX-PC systemd[1]: Timed out waiting for device dev-sdc1.device - /dev/sdc1.
    ░░ Subject: A start job for unit dev-sdc1.device has failed
    ░░ Defined-By: systemd
    ░░ Support: http://www.ubuntu.com/support
    ░░

    I have no idea how to fix this as I have very little knowledge of disks etc.

    Please help me, Thanks
    Last edited by Gazzer; Nov 07, 2024, 09:53 AM.

    #2
    I would not use the media folder for permanent mounts. That's not what that folder is for. The convention is to make directories under /mnt/ and mount fixed devices there.

    If the drive is an external or unplug-able device, it really shouldn't be in fstab at all. You would let the system mount it in /media/<username>/ by clicking on it the system tray or Dolphin. This will mount it user the file system Label or UUID under /media/<username>/.

    Finally, if it's an unplug-able device but you want to automount it at boot when it's attached, open System Settings > Connected Devices > Device Auto-Mount and check the boxes for "On Login" and "On Attach"

    Please Read Me

    Comment


      #3
      Thanks for your help
      Looks like i was correct and the fstab files was incorrect had to remove /dev/sdc1 /media/gb/usbdrive ext4 defaults 0 0 from the fstab file now all working

      Comment


        #4
        BTW, 23.04 is past end-of-life... posting in the 22.04 sub-forum, perhaps it's 22.04?
        Regards, John Little

        Comment

        Working...
        X