Forums

Resolved
0 votes
Hi Guys, I'm at the end of my wits trying to figure this one out. Any suggestions or directions would be helpful.

When I "plug in" a USB drive it causes a failure during the clearos startup process that causes clearos to go into startup recovery mode.

It does not matter if the drive is listed under fstab

Unplugging the USB drive results in a normal startup.

If the drive is plugged in after startup, I can mount and use the drive normally. It will even mount with fstab if it's plugged in right after the "bar turns white" in the startup procedure.

The drive is (obviously) recognized by the bios, and functioning properly.

I have previously installed a second internal drive, that went without a hitch.

At this point I'm not even sure what to check. Grateful for any suggestions.

The drive is a 4TB HDD, plugged into a USB3 port.
Friday, October 13 2017, 06:27 PM
Share this post:
Responses (4)
  • Accepted Answer

    Friday, October 13 2017, 11:04 PM - #Permalink
    Resolved
    0 votes
    Can you please list your /etc/fstab file (within code tags please) and also the command you use to mount the usb drive manually
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 14 2017, 02:49 AM - #Permalink
    Resolved
    0 votes
    /dev/mapper/clearos-root /                       xfs     defaults        0 0
    UUID=d1f2add6-5852-4e1f-bda8-4a2f8e2fd4a1 /boot xfs defaults 0 0
    /dev/mapper/clearos-swap swap swap defaults 0 0
    /dev/sdb1 /var/flexshare/shares/plexfiles ext4 defaults 0 0
    /dev/sdc1 /media/usb4t ext4 defaults 0 0


    The manual mount command is nothing special.
    mount /dev/sdc1 /media/usb4t


    Also, note that removing the last line in the fstab file does not affect this issue.
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, October 14 2017, 05:24 AM - #Permalink
    Resolved
    0 votes
    Did you have this problem with the USB drive before adding the extra disk for the plexfiles? (sdb1 in your fstab)?

    It is really not really the best practice to mount disks using using the dev/sdxy device name; /dev/sdb1 in your case. Disks can 'move'. Wonder whether the USB drive, when inserted before boot, is becoming /dev/sda1 or /dev/sdb1 and hence you are dropping into emergency mode as it cannot perform the mount as per your /etc/fstab as your 'plex' disk is no longer /dev/sdb1. It is much preferred to use the UUID. Your fstab is uisng UUID for the boot drive... If something like this is occurring - then the instructions below should help...

    If you run ' ls -l /dev/disk/by-uuid ' - you can see the UUID for your disk partitions...
    Check that you can see the one for your /boot partition to verify that you understand the output, matching it to your fstab ... suspect it is /dev/sda1
    Then find the UUID for /dev/sdb1 and amend your fstab - using the entry for /boot as a template for the format...

    Check first without the USB drive - then reboot with it inserted? Fixed? If so, is the USB drive still /dev/sdc1 when you boot with it inserted? If it moved then checking /var/log/messages is one of several ways to find its new device name...

    There are other causes for your problem - but this is the first solution that should be attempted...
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, October 15 2017, 11:16 PM - #Permalink
    Resolved
    0 votes
    That was it! It's all booting nicely now.

    Thanks for taking the time to help this noob out! I've still got a lot to learn when it comes to Linux CLI.
    The reply is currently minimized Show
Your Reply