Need a hint about system's verbage at bootup


I've got a dual boot W10/Ubuntu 14.04 laptop. I use GRUB2 as a boot loader. In the BIOS I chose "Legacy BIOS" option (the laptop was purchased with EUFI enabled system and W8 OEM). I don't know, maybe it's something wrong that I did during the installation or something else... Right now, I probably won't run and start changing or re-installing stuff, but at least I'd like to know what it's all about. What happens is that when I try to get into Ubuntu quite often I end up in BusyBox shell environment. Then I re-boot the machine and get to Ubuntu at last. What is even stranger to me is that it doesn't always happen. Sometimes everything is kosher and I get normally to the Ubuntu login screen (it's a desktop environment -- Unity). Now...I would present here the verbage I see on the screen while I try to get to Ubuntu, but end up in shell. sdb being the Ubuntu HDD (usually).

[      2.978708] usd 1-1.1: string descriptor 0 read error: -22
[      3.660632] sd 6:0:0:0: [sdb] No Caching mode page found
[      3.660665] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Gave up waiting for root device  Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-uuid/c6d0a763-50c0-4072-a72f-6286ec73709b does not exist.
Dropping to a shell!

BusyBox v1.21.1 (ubuntu...) built-in shell (ash)
(initramfs)_    (curson is blinking here)...
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Maidine FouadEngineerCommented:
i would try to use The Ubuntu Boot Repair Kit first

Then check the Logs ( you can try this scrip for example ) this will give you all the details , again you must run it from a live cd :

You can also link it here if you want

Ps: For fixing the Alert that showed up (ALERT!  /dev/disk/by-uuid/c6d0a763-50c0-4072-a72f-6286ec73709b) you can do the following , in a live cd of course:

replace the x in sdax with the corresponding number  you have ...
sudo mount /dev/sdax /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
update-initramfs -u

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David197705Author Commented:
Thanks a bunch!
I will definitely look into what you've proposed here!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.