LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 07-15-2017, 11:59 PM   #1
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,098

Rep: Reputation: 100Reputation: 100
Cannot boot if USB drive connected.


I am running Slackware64 14.2, kernel 4.4.75. I have a relatively new ASRock 970M Pro3 motherboard (bought 6 months ago, but not used until now).

If I have a USB drive connected, I cannot boot. I get the error
Code:
error: no such device: 83880a6f-3e10-4c41-b4a1-1e5fd5ef026a
Entering rescue mode...
grub rescue >
If I remove the USB drive and reset or CTL-ALT-DEL it boots fine. btw I don't find the UUID listed in the error message on any drive, including the USB drive.

In examining the Bios, I don't even see USB as a possible boot option (image). The BIOS shows boot option 1 as the DVD, option 2 as the Samsung hard drive and option 3 disabled.

This LQ thread mentioned there might be issues with ASROK http://www.linuxquestions.org/questi...3/#post5639598

Does anyone have any ideas on fixing this? This seems like incredibly stupid behavior for a motherboard as people leave USB drives connected for all kinds of reasons -- in my case, for backups.
 
Old 07-16-2017, 12:03 AM   #2
Laserbeak
Member
 
Registered: Jan 2017
Location: Manhattan, NYC NY
Distribution: Mac OS X, iOS, Solaris
Posts: 508

Rep: Reputation: 142Reputation: 142
Sorry, no help... but that is bizarre!

edit:

OK, I'll throw something out there: do you have anything in your firmware preferences (BIOS or UEFI) that says to boot from USB first?

Last edited by Laserbeak; 07-16-2017 at 12:07 AM.
 
Old 07-16-2017, 12:28 AM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 15,936

Rep: Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209Reputation: 2209
If you think you are having support issues for new chips, get onto a kernel that is somewhere near current. I've been on 4.12 rc kernels for awhile for example.
I see marvel mentioned in that other thread (I only skimmed over it) - years ago they caused me grief for weeks, and I was recompiling every time Linus tree got updated. Eventually support moves into mainline.
 
Old 07-16-2017, 07:43 PM   #4
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,098

Original Poster
Rep: Reputation: 100Reputation: 100
Quote:
Originally Posted by Laserbeak View Post
OK, I'll throw something out there: do you have anything in your firmware preferences (BIOS or UEFI) that says to boot from USB first?
No, nothing the firmware (BIOS) that I can find. The boot order menu doesn't even list USB.

Quote:
Originally Posted by syg00 View Post
If you think you are having support issues for new chips, get onto a kernel that is somewhere near current. I've been on 4.12 rc kernels for awhile for example.
I see marvel mentioned in that other thread (I only skimmed over it) - years ago they caused me grief for weeks, and I was recompiling every time Linus tree got updated. Eventually support moves into mainline.
This isn't a kernel issue. I can't boot to any OS if the USB drive is plugged in.

I may have to get a different MB! Too bad because I've just now started to use it and it's been too long to return it to the store.

Any other ideas? Surely LQ users have run into this before with ASROCK MBs.
 
Old 07-17-2017, 12:46 AM   #5
TheEzekielProject
Member
 
Registered: Dec 2016
Distribution: Devuan, Slackware
Posts: 455

Rep: Reputation: 108Reputation: 108
The fact that you can't boot to any OS suggests an issue with the BIOS/UEFI. I would suggest checking for a firmware update for the motherboard if you haven't already done so
 
Old 07-17-2017, 05:18 AM   #6
aragorn2101
Member
 
Registered: Dec 2012
Location: Mauritius
Distribution: Slackware
Posts: 509

Rep: Reputation: 241Reputation: 241Reputation: 241
Does it do this for any USB drive plugged in? Did you do a fresh install of Slackware? Did you just swap motherboards on a working system?
 
Old 07-17-2017, 06:13 AM   #7
Teufel
Member
 
Registered: Apr 2012
Distribution: Gentoo
Posts: 575

Rep: Reputation: 134Reputation: 134
Seems USB drive messes a drives/partitions order.
If it's absolutely necessary to boot with USB drive attached, I'd boot into system with detached drive, then attached it and run grub-mkconfig. May be this case grub will take into account USB drive on next boot.
 
Old 07-17-2017, 05:03 PM   #8
jefro
Moderator
 
Registered: Mar 2008
Posts: 17,099

Rep: Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551Reputation: 2551
Look in bios under hard drives when you have usb installed.
Grub using hdx ??

Other info here. https://superuser.com/questions/3594...h-device-error

Last edited by jefro; 07-17-2017 at 05:06 PM.
 
Old 07-17-2017, 05:41 PM   #9
Mike_Walsh
Member
 
Registered: Jul 2017
Location: King's Lynn, UK
Distribution: Puppy Linux, AntiX
Posts: 108

Rep: Reputation: 72
Perhaps something to do with the fact that some BIOSes don't recognise USB drives as USB drives at all? They see them, instead, as HDD's; e.g. 'HDD-01', or 'HDD-02', etc.

The Phoenix BIOS, for example, is well-known for this.


Mike.
 
Old 07-17-2017, 07:51 PM   #10
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,098

Original Poster
Rep: Reputation: 100Reputation: 100
Quote:
Originally Posted by TheEzekielProject View Post
The fact that you can't boot to any OS suggests an issue with the BIOS/UEFI. I would suggest checking for a firmware update for the motherboard if you haven't already done so
I have the latest firmware update.
Quote:
Originally Posted by aragorn2101 View Post
Does it do this for any USB drive plugged in? Did you do a fresh install of Slackware? Did you just swap motherboards on a working system?
Actually, no! I tested with another USB drive and it booted fine (more below). It is not related to Slackware as I've tried booting from DVD with other OSes and same problem.
Quote:
Originally Posted by Teufel View Post
Seems USB drive messes a drives/partitions order.
If it's absolutely necessary to boot with USB drive attached, I'd boot into system with detached drive, then attached it and run grub-mkconfig. May be this case grub will take into account USB drive on next boot.
Not sure where the grub message is coming from. My Slackware installation uses lilo not grub. I suspect the grub message is coming from the USB drive itself.
Quote:
Originally Posted by Mike_Walsh View Post
Perhaps something to do with the fact that some BIOSes don't recognise USB drives as USB drives at all? They see them, instead, as HDD's; e.g. 'HDD-01', or 'HDD-02', etc.

The Phoenix BIOS, for example, is well-known for this.
Yes, I think this is the heart of the matter. There is no BIOS selection for USB in the boot order at all, and I've heard that some motherboards assume USB drives as boot priority 1, regardless. I think this is what the ASROCK MB does.

I fixed the problem: The USB drive giving me the problems is a WD Elements. As I mentioned, I was able to boot normally with a different USB drive connected. That got me to thinking. So, I saved off all the files from the WD Elements USB and zeroed the boot sector `dd if=/dev/zero of=/dev/hdb bs=512 count=1`. I then re-formatted the drive to NTFS with Windows. I then plugged the drive back into the Linux box and rebooted. Behold! It booted successfully, no "grub" message. I then copied all the files back to the drive and tried the reboot again. It still booted OK.

So, there must be something on out-of-the-box WD Elements USB drives that appears boot-like. And perhaps, if this ASROCK MB is one of those that automatically attempts to boot from connected USB drives, then the MB could have very well thought this was a bootable USB and "automatically" booted from it. Perhaps the "grub" message was from something on the WD Elements.

If so, this is a VERY BAD IDEA. I can think of no good reason to automatically put USBs as first boot priority (you should always be able to manually set that if so desired in the BIOS), and I can think of lots of excellent reason to NEVER do such a thing, including this several-day waste of time, not to mention that just because one has an "apparently" bootable USB attached does not mean ipso facto that user must certainly want to boot from it.

I will avoid ASROCK motherboards in the future; and per Mike_Walsh, Phoenix BIOSes as well. I think I'll also avoid WD USB drives. I already avoid Seagate USB drives because of auto-spindown http://www.nslu2-linux.org/wiki/pmwi...agateFreeAgent.

Last edited by mfoley; 07-17-2017 at 07:55 PM.
 
Old 07-18-2017, 04:44 AM   #11
Teufel
Member
 
Registered: Apr 2012
Distribution: Gentoo
Posts: 575

Rep: Reputation: 134Reputation: 134
Quote:
Originally Posted by mfoley View Post
Actually, no! I tested with another USB drive and it booted fine (more below). It is not related to Slackware as I've tried booting from DVD with other OSes and same problem.

Not sure where the grub message is coming from. My Slackware installation uses lilo not grub. I suspect the grub message is coming from the USB drive itself.
LOL, your USB drive has a bootloader (grub) installed at boot sector. And this bootloader tries to boot, but root partition (with uuid 83880a6f-3e10-4c41-b4a1-1e5fd5ef026a) is missing, so you getting a message

Code:
no such device: 83880a6f-3e10-4c41-b4a1-1e5fd5ef026a
You have to erase the grub boot code at the boot sector of your USB drive.
 
Old 07-18-2017, 05:01 AM   #12
Teufel
Member
 
Registered: Apr 2012
Distribution: Gentoo
Posts: 575

Rep: Reputation: 134Reputation: 134
To erase boot sector from USB drive save your data from USB drive (if there is something important) and run
Code:
# dd if=/dev/zero of=/dev/sdX bs=446 count=1
where sdX stands for your USB drive. It may be sdb or sdc (or something other, you can read it from "fdisk -l" command output).
 
Old 07-18-2017, 04:44 PM   #13
Mike_Walsh
Member
 
Registered: Jul 2017
Location: King's Lynn, UK
Distribution: Puppy Linux, AntiX
Posts: 108

Rep: Reputation: 72
Quote:
Originally Posted by mfoley View Post
I will avoid ASROCK motherboards in the future; and per Mike_Walsh, Phoenix BIOSes as well. I think I'll also avoid WD USB drives. I already avoid Seagate USB drives because of auto-spindown http://www.nslu2-linux.org/wiki/pmwi...agateFreeAgent.
Sounds like a plan. This 'Puppy' box of mine started life as a Compaq Presario business-class PC (from just before the HP 'takeover' of 2004, thus of far superior build quality to the subsequent crap that HP churned out under the name.) It originally had a single-core Athlon64, with a 'built-under-contract' MSI motherboard.....and a bog-standard HP BIOS, which had a one-time boot menu, and would boot from a FAT-32 formatted USB drive, if necessary.

Where the fun began was when I uprated the CPU to an X2 dual-core Athlon64 (which fitted the same socket). The BIOS needed upgrading to support the dual-core CPU. HP didn't have one for it, so, along with an acquaintance from the Murga-Linux 'Puppy' forums, we tracked down a suitable BIOS from MSI themselves. They wouldn't even admit to having produced the MS-7184; as far as they were concerned, it was HP's 'problem', and they'd washed their hands of them the instant they went out the door. MSI did, however, produce an almost identical board (the MS-7093); same chipsets and everything.....just with the addition of two extra SATA ports.

The BIOS upgrade went very smoothly; we tracked down the 'flashROM' utility through the Arch Linux wiki, and the whole thing only took a couple of hours , back & forth through the forum. I'd never done one of these before, so my friend basically 'held my hand' through the procedure, since I was scared shi***ss of 'bricking it'. (He'd spent a few years as a repair technician in his home town of Des Moines, Illinois, and had done hundreds of BIOS upgrades.....so he did at least have some idea of what he was doing!)

The upshot of all this? The old girl now thinks she has an MS-7093 motherboard, instead of the MS-7184 (due to the BIOS upgrade).....and the Phoenix BIOS has introduced a few gremlins of its own. No one-time boot menu; USB drives are recognised as hard drives.....and it won't boot from a FAT 32 partition any more. Which annoyed the hell out of me; I've got a Kolibri USB drive that I used to spend quite a bit of time messing around with, which is now gathering dust in the back of a desk drawer.

KolibriOS will not run from anything other than a FAT32 partition.....

Go figure.


Mike.
 
Old 08-22-2017, 09:51 AM   #14
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,098

Original Poster
Rep: Reputation: 100Reputation: 100
Followup note: Out of necessity, I installed 3 Seagate ST5000LM000 5GB external USB drives on different computers. They appear to be working just fine. Apparently Seagate 'fixed' the auto-spindown "feature".
 
Old 08-22-2017, 10:35 AM   #15
Shadow_7
Senior Member
 
Registered: Feb 2003
Distribution: debian
Posts: 3,299
Blog Entries: 1

Rep: Reputation: 685Reputation: 685Reputation: 685Reputation: 685Reputation: 685Reputation: 685
I have a system that only boots external USB "IF" it's plugged into a usb hub plugged into a usb port. Or "IF" the bootable usb drive is plugged into the FRONT usb port. There's a lot of quirky systems out there. I still have a 300GB seagate PATA drive that came in an enclosure that STILL clunks after relatively short use and needs a power cycle to work again. They've never fixed that smart chip issue. My $300 300GB brick that leaves me buying seagate as only a last resort.
 
  


Reply

Tags
asrock, boot failure, grub rescue, usb


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Detect if USB drive is connected Fixit7 Puppy 13 05-30-2015 08:17 PM
No boot with SATA drive connected WeeFreeMan Linux - Hardware 11 08-13-2008 12:33 AM
How to detect wheather usb drive is connected thru script linux1 Linux - Newbie 2 06-05-2008 10:34 AM
Boot with second drive connected lenlutz Red Hat 1 07-18-2005 10:59 AM
How to open external hard drive when connected to USB??? kingslax Linux - Hardware 1 09-22-2004 07:07 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 08:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration