just installed ubuntu 10.10 on my external usb hdd from my 8gb flash drive doing this on a laptop, my primary hdd (internal) is running windows (230gb of 250gb used) so i got an external hdd (2tb) and I decided to install ubuntu on it
[Code]....
When I boot off of Debian Kernel 2.6.26-2-686. This is what happens. It stops at attached scsi generic sg5 type 0 After 4 or 5 minutes it comes back and says.
Gave up waiting for root device. Common problems Boot args (cat /proc/cmdline) Check Root= (did the system wait for the right device) Missing modules (cat /proc/modules; ls /dev Alert /dev/sdd8 does not exist dropping to shell /bin /sh: can't access tty; job control turned off If I boot off Debian Kernel 2.6.26-2-686 (single user mode) Then use Control-D it boots fine.
I needed to use CIFS for accessing a NTFS network share. I decided to include CIFS in the kernel and tried compiling and installing it. Now when I (try to) boot in my new kernel with CIFS support, I get the message: gave up looking for root device.
View 5 Replies View RelatedI have been trying to update my server from 6.06 server to 10.04 server. My attempts have been complicated by versions later than 6.06 not being able to properly read my CD-ROM. I used the 'do-release-upgrade' mechanism to upgrade to from 6.06 to 8.04 and then to 10.04. 8.04 loaded OK, but 10.04 fails to boot with the surprisingly common "Gave up waiting for root device" error. It stops at the built-in shell prompt. If I exit from the shell, it seems to boot up normally.
I have verified that the boot partition is /dev/sda1 and the UUID for the partition is correct. My system is an older IBM eServer xSeries 350 with quad 700MHz XEON processors and a 36GB SCSI drive. This system properly installed from the 6.06 CD and boots under this version without problems. So I have some questions. Only the first one needs an answer.
1. What do I need to do to get my system to boot properly?
2. Why was this software released with this error?
3. Why wasn't the faulty loader pulled from the release until it was fixed?
4. Is it possible to revert to the 6.06 loader, which works fine?
5. Why doesn't the loader attempt to try something else that should work instead of just giving up?
ubuntu 9.10 is not booting shows Gave up waiting for root device.", (initramfs). how to boot normally from this problem. The problem is coming from installed system.
View 2 Replies View Relatedthis is my first setup of ubuntu. And I�m quite familar to Linux allthoug it�s been a while since my last setup. Anyway, my system is brand new and consist of the following parts:
AMD Athlon X2 240e on MSI 880GMA-E45 (SB850)
4GB RAM (DDR3)
All drives connected by SATA using onboard SB850 ordered by:
1 LG BluRay optical drive
2 WD Caviar Green WD10EARS 1TB
3 WD Caviar Green WD20EARS 2TB
4 WD Caviar Green WD20EARS 2TB
5 WD Caviar Green WD20EARS 2TB
6 WD Caviar Green WD15EARS 1,5TB
I set the SATA controller to AHCI because I want to set up a software raid (level 5) on the three 2TB-disks. The first disk (1TB) should be the ubuntu boot disk (no raid). The last one (1,5TB) is currently not connected - it will be added later. First I struggled booting the ubuntu server 10.10-CD (x64) from the bluray drive - after succesfull starting the setup procedure it told me that it cannot access the drive. It seems that drivers are missing. No problem - I connected an usb dvd drive to the system and gave it a try.
The boot order was set to usb-dvd, then bluray, then the first harddisk (1TB). Setup seems to run fine using the usb dvd drive. I�ve chosen the first disk (shown as /dev/sda) for the installation. It was automatically configured as one big root-partition and a small swap-partition. Grub was installed on the MBR of the first disk. But after restart GRUB tells me "Gave up waiting for root device" and "ALERT! /dev/disk/by-uuid/whatever does not exist. Dropping to a shell!". Obviously the boot loader cannot find (or access) the volume containing the kernel.
I made some research and found some other people complaining about some mixup of hdaX and sdaX devices on SATA devices - but these statements where from 2007. Another point is that the USB optical drive is my boot device while the installation runs, but not afterwards - does this matter? I also tried installing Ubuntu server 10.04, but is behaves the same. Please keep in mind that the goal is to have ubunto server 64bit running on this system - that�s it. No dual boot is needed. And there is no data on any disk that should be taken care. It�s a very new system. Where should I start to fix this issue? What�s wrong with the current linux boot loader using SATA disks connected to SB850 SATA controller?
I did an installation of Ubuntu 8.1 on my laptop. I ran the live CD first to check that everything was ok and got no problems. But when I try to boot I get this error:
Boot from (hd0,0) ext3 e194- long number
Gave up waiting for root device.
Alert /dev/disk/by-vvid/e194- long number
I tried a different hard drive with the same results. So I installed XP and everything worked fine. This makes me believe that all of the hardware is ok and I have some config screwy.
The system is an old AMD Duron 650MHz that was dug out of the garbage, trying to set it up as a light duty server. I installed ubuntu 10.04 with no errors or troubles during the install, however whenever the system is booted it sits at a cursor for about a minute then goes into busybox giving the error "Gave up waiting on root device." and says that the hard drive does not excist. If I sit at busybox for about another minute and type exit it then boots ubuntu 10.04 with no errors or issues.
View 7 Replies View RelatedI got the message "Gave up waiting for root device after I rebooted an Ubuntu 10.04 system I thought I restored by unpacking a tar.gz at the base of the directory tree I made for backup purposes.
View 1 Replies View RelatedAbout a week ago I changed the hard disk setup of my desktop PC. I installed a new SSD and changed the set-up of my old hard disks. Since I installed the SSD I have not been able to boot Ubuntu from it. When I reboot and chose Ubuntu at the grub menu then it ends with the following error: 'Gave up waiting for root device' and '/dev/disk/by-uuid/2bef4d2f-db0e-44b3-9e85-2065fad6f4a0 does not exist. Dropping to Shell!'
I have made a description of my current set-up and the changes made last week and I have copied the output from boot_info_script as well. Old setup:
Asus P5Q-Pro mainboard 3x Samsung Spinpoint F1 750GB with 2 drives in a (fake)raid 0 setup using Intel Matrix Raid Storage from the ICH10R chipset with 4 partitions: a system partition for Windows 7, a system partition for Ubuntu, a data storage partition for Windows and a linux swap partition 1 drive not in a raid array and split in 2 partitions: 1 ext4 partition used for my /home folder (since the Ubuntu system partition was not intented to be used to store documents) 1 ntfs partition used to backup documents, pictures/photo's and music from the Windows data partition on the raid array Since release 10.04 Ubuntu would install properly on the raid array. Before release 10 I had to use the alternate cd installation and install grub manually to avoid messing up the boot process.
[Code]....
I had to reinstall 10.04 because I got an error, waiting for root device. And I figured I knew why I got this error: I changed my xconf.cfg (or whatever the file is in /etc/x11/) -- So this time I downloaded the 64 bit, because I have a 64 bit computer, so though, might as well get it! I've narrowed the problem down to this:
After I install nvidia settings (the x server or whatever?) And change my view to TwinView (I have my laptop monitor and an external monitor), and save the config file, this happens. I will do some more testing, but here is the whole error message: Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system not 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/bcb49367-8554-4116-8e4d2b39d92415cf does not exist. Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu11) built-in shell (ash) Enter 'help' for a list of built-in commands.
I am running Ubuntu 10.10. After the most recent major upgrade I started getting the above message when booting with the default kernel, Linux 2.6.35.30 Generic. But if I drop back to Linux 2.6.35.28 Generic then everything works fine. I have plenty of free memory and none of the previous posts seem to apply to this problem. I downloaded and ran the boot info script and here are the results:
[Code]....
I'm trying my first install of Mythbuntu and I'm getting this same error. I am able to complete the install and even boot into the OS using a LIVE cd but after installation & reboot I get "gave up waiting for root device." I downloaded the info script and ran it - the results are attached but I haven't a clue what to make of it - other than my drive is sda and the OS is on sda1.
[Code]...
I know this has problem has been discussed several times but it always seems to be on an older ubuntu version which doesn't have the same solution as mine. I'm currently running Ubuntu Desktop 10.10 x64.When I'm trying to boot ubuntu I get this error message:
Code:
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
[code]...
I know this has problem has been discussed several times but it always seems to be on an older ubuntu version which doesn't have the same solution as mine. I'm currently running Ubuntu Desktop 10.10 x64. When I'm trying to boot ubuntu I get this error message:
Code: 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/{my hard drive's uuid} does not exist. Dropping to a shell!
[Code]....
recently attempted to upgrade to Lucid Lynx but it's not booting up. it just shows "Gave up waiting for root device" and drops to BusyBox. waiting doesn't do anything. i see the GRUB options but none of the 3 10.04 LTS's boot up. i've read a number of threads but i don't think my Ubuntu drive is being read. i say this 'cause cat/proc/partitions doesn't list my Ubuntu drive/partition. Also when booting up in the Live CD, GParted only lists the Windows partition. neither does sudo fdisk -l.
View 9 Replies View RelatedI just installed Ubuntu 10.04 and booted to the desktop 2 times. Both times the desktop was so big I could not see any of the icons. The third time and every time I tried to boot again I am getting the following Text Screen warning. "Gave up waiting for root device". I expect I have two different problems, but I can not work on the desktop being to big until I can get this system to boot again.
View 3 Replies View RelatedI've installed Ubuntu 9.10 server on old hardware. The boot seems to have a problem. See the screenshot attached. When I see that and type "exit" the normal login is displayed. There was nothing special about the install. Anyone has an idea how to fix it?
View 1 Replies View RelatedI had this problem after my mainboard crashed (my clumsiness) and I replaced my dual-core AMD with a Triple-core and a MSI mainboard deal from a dealer clearencing. Before my MBR was on my 80 gig IDE but I dropped it and put my SATA 320gig in its place and did a fresh install of Lucid. Preparing a machine for a friend that wanted Mepis on her computer with WindowsXP in VirtualBox I could not compile the vbox kernel and in the mepislovers forum I was instructed to run sudo m-a and to then compile the kernel. This worked perfectly.
This morning (01:57 Texas time) after trying a few solution suggestions from the forum here I said, what the snot and I typed sudo m-a in the terminal and was instructed to download the module-assistant with the useual 'apt-get install module-assistant. After the install I ran the sudo m-a and then with my arrow keys selected the second option and hit enter. As soon as it finished I used my down arrow and selected the third option and entered it. After that I selected exit and have been cold starting my machine without the aggravation.
since I did anything with Linux so I am understandably a bit rusty and alot has changed. That being said, I am trying to sideload (no separate partition) Ubuntu Netbook 10.10 on a HP Mini 311 1037NR so I can "get back in the game". This was supposed to be simple but now that I am seeing double and can't stop my eyes from watering from staring at these screens so long, time to ask for help. I used the wubi installer and the ubuntu i386 netbook iso, downloaded to a folder on Windows 7, then ran the installer, set it for Ubuntu Netbook, 20-25GB, then "install". Installation goes without a hitch apparently and after reboot, I get the Windows 7/Ubuntu boot prompt. Every time I select Unbootu, it get a flashing prompt for a few seconds then:
Code: "Gave up waiting for root device...blah blah blah... ALERT! /dev/sdb2 does not exist". Now I know this has to be something stupid like sdb2 being my RECOVERY D: drive or USB device, but for the life of me I cannot figure out how to confirm this, and then, I'm assuming, mount/chroot to the correct one. Output of "ls /dev" lists sda, sda1, sda2, sda3, disk, sdb, and sdb1...there is no sdb2 as the error states. I need to be able to correct this without having to boot to USB/CD. I have tried uninstalling/reinstalling and attempted to boot into ubuntu recovery, no dice.
When I was upgrading my system (ubuntu server edition) today from 8.10 to 10.04 (of course in small steps: upgrade version after version) everything seemed running smoothly. But when I restarted it, it gave an error message: Gave up waiting on root device. Screenshot of error and grub menu attached. I've read some information about it and applied the possible workaround given here: [URL]. My system is very old and so is the HDD: it uses an IDE connector. Typing 'exit' doesn't work either.
View 6 Replies View RelatedI have a Toshiba NB305 netbook running windows 7. I installed netbook ubuntu 10.04 from a USB drive this morning after playing with the live ISO off the USB. I chose to repartition and keep Windows 7. Upon boot, I get GRUB and when I choose either the Ubuntu or the Recovery I get a "gave up waiting for root device" page with a command prompt flashing at initiramfs.
The Alert reads, "/dev/disk/by-uuid/49024e15-119a-4339-ad23-f201ce4a6d1f does not exist. Dropping to Shell!
I'm still able to boot windows 7 as well as the live cd and see all the partitions and operating systems.
I've looked inside the Grub.cfg file and the commands aren't pointing to /dev/sda5/ but rather to the uuid? Is this normal? Does this need to be changed?
I will run this script and try and get some more info.
[url]
Recently setup Ubuntu Server 10.10 on an old Dell Poweredge 2650. It seemed to be working perfectly until I did my first reboot. I tried changing the 'root' reference on the linux line at the grub menu with no luck. I suspect the problem is something else but I have no clue.
So far the behavior seems completely consistent. If I physically power the machine down and start it back up everything works perfectly. However, if I do a sudo reboot now I'll end up at the initramfs prompt. I'm not comfortable setting up my dev environment on this box until I'm sure it will be stable. In case it matters the machine is running a single scsi drive and doesn't have a raid controller.
The case is that I've got 2 harddisks. On the one windows xp(slave) - and on the other one ubuntu (master). During the boot I get these errors...
"Gave up waiting for boot device"
"Boot args(cat /proc/cmdline)"
"Missing modules (cat /proc/modules; 1s , dev)"
"/dev/disk/by-uuid/f96603ce - does not exist"
These problems occured because of this:
After using ubuntu I tried to reset my bios, because else it couldn't have found the disk with xp. And I didn't disconnect the disk with xp while resetting the bios. And now the system can't find the disk with xp any more when booting. Is there a way to finding the disk..? And I'm in doubt about IF I've resetted the bios at all. I miss a manual for PCCHIPS M851. May be it can take 20 minutes for the bios to be resetted? The shop where I bought the motherboard doesn't exist any more... and don't know the manufacturer. Could I damage the motherboard if I tried rebooting lots of times to get it work?
I tried to install Lucid x64. I have a Dell Studio 1555 with a 250gb hard drive. I have it partitioned thusly: A 200GB NTFS partition that I keep all my music/videos/books on. When I have Linux installed, I mount this as /files. I never touch this partition during an OS install. A 100MB EXT4 partition that I created today during the install process. I mount this as /boot. A 4GB swap partition that I created today during the install process.
A 46GB(ish) EXT4 partition that I created today during the install process. I mount this as /. As far as I could tell, aside from being for some reason painstakingly slow, the install process went normally. At the end, I was prompted to remove the disc and press Enter to reboot. I did so. My computer didn't boot. Instead, after BIOS, I got a blinking text cursor for about ten seconds, and then the following message:
[Code]....
I've tried setting rootdelay=90, but that didn't work, and the majority of the failure output is greek to me. I've found reports of similar problems all over the forums, but nothing really useful or comprehensible.
I installed Ubuntu 10.10 inside Windows 7 today, Ubuntu 10.10 finished installing and all just fine
but when I try to boot into Ubuntu 10.10 from the boot menu I get this error
"gave up waiting for root device" while booting
and it mentions something about BusyBox
I am running 10.04 LTS on an old AMD Althon 64-bit MB. When I first installed Ubuntu, everything was working great. Then, a few weeks ago, I did a standard update and rebooted. At this point, I started getting "gave up waiting on root device" and related errors. After trying various fixes ranging from adding rootdelay=XX and root=/dev/sda1 and related, I have not been able to get my box to boot without having to sit and wait for a very long time.
Also, for whatever reason, Ubuntu now refuses to detect my DVD burner and 120GB HD. When I do ls /dev/sd*, I see sda (80GB HD below) and sdb (250GB HD below), but I do not see sdc and sdd. Here is the assignment of drives as reported by the BIOS. Primary IDE Master: WDC WD800JB-00ETA0 (80GB WD HD, set as boot drive and where ubuntu is installed to) Primary IDE Slave: WDC WD2500JB-00GVA0 (250GB WD HD) Secondary IDE Master: LITE-ON DVDRW SOHW-1683S (DVD-RW/dual layer/DVD-RAM burner) Secondary IDE Slave: WDC WD1200JB-00GVA0 (120GB WD HD, NTFS file system, uses ntfs-3g)
I noticed that if I go into the BIOS and sit for a while then exit the BIOS, Ubuntu loads just fine. I don't know how long I have to sit there before Ubuntu will fully load just fine, so this confuses me.
Here is the output from dmesg when I have trouble booting. The interesting section starts around index 0.839746 where it tries to find all the hardware.
[Code]...
I've installed squeeze and wheezy on an old Toshiba Satellite 210 CS laptop with 48MB RAM and a 20GB IDE harddrive.Grub2 won't boot at all and stops with a "error: cannot allocate real mode pages". The solution to that is to use the grub-legacy package.The boot then fails with "waiting for root device" and drops to an initramfs shell.
View 5 Replies View RelatedI updated yesterday and now when I start my laptop it goes in to grub rescue mode. I have booted from a 'live cd' and thought I could repair grub from there. In gparted however the partition with ubuntu (sda1) is seen as unknown file system, in terminal when I list the partition table it shows up as FAT16 type. When I try a grub-install it gives this error message:
[Code]....
i have a working Windows 7/xp dual boot prior and post to having installing ubuntu, after installation i removed the usb thumb drive then preformed a reboot. when i got to boot loader where i normally pick Win7/Xp/Linux and pick linux it then runs grub. I get the boot loader screen, select Ubuntu 10.10 "Gave up waiting for root device. Common problems:
- boot args (Cal /proc/cmdline)
- check rootdelay= ( Did the system wait long enough?)
From booting back of live usb
[Code]...
i tried hitting e and changing (there was more before this)linux /vmlinuz root=/dev/sdd1 ro quiet splash which kicked me back to same point saying it could not find it at sdd1
