«Gave up waiting for root device.», (initramfs)

"Gave up waiting for root device.", (initramfs) Техника

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

"Gave up waiting for root device.", (initramfs)

February 22nd, 2011

"Gave up waiting for root device.", (initramfs)

Тема: Gave up waiting for root device ….. (initramfs)  (Прочитано 1755 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
wtor

Всем привет.
Я стараюсь спрашивать на форуме, всегда в крайнем случае, сначала облажу весь гугл, испытаю все методы решения проблемы на себе, и только потом, когда уже ничего не выходит, пишу на форум. Вот он этот случай.
Расскажу немного предысторию, может поможет в решении.
Дело было так. Установил я Ubuntu, настроил под себя(мое почти первое знакомство с системой), и решил залезть в раздел Software & Updates, во вкладку Additional Drivers. Там поменял драйвер для Broadcom-а, с того что у меня стоял(не помню какой), на этот(нашел похожий скрин в гугле)
"Gave up waiting for root device.", (initramfs)
"Gave up waiting for root device.", (initramfs)
Опять выключил машину кнопкой. После второй загрузки, вижу только стандартный фиолетовый цвет экрана, и никаких изменений.(позже понял что за этим экраном все таки что-то есть, потому что могу написать reboot в слепую и машина выполнит команду)
Решил запуститься в рекавери моде, и уже какую-то обратную связь получил.
"Gave up waiting for root device.", (initramfs)
Естественно полез в гугл. Чего я только не пробовал. Прописывал в параметрах запуска груба путь к разделу на котором у меня система. Пробовал проверять разделы через лайв сд(gparted => Check). Ни на англоязычных, ни на русских форумах, ничего толкового не нашел.
Уже опустил руки, думаю переустанавливать систему, но больно жалко настройки, которые я под себя ставил пол дня.  :'(
Может кто-то поможет.
Заранее спасибо всем добрым людям за ответы.

« Последнее редактирование: 05 Марта 2017, 20:38:05 от wtor »


Оффлайн
Azure

больно жалко настройки, которые я под себя ставил пол дня.

home

загрузившись с LiveCD, а с ним и сохранятся Ваши настройки. После переустановки верните его назад также загрузившись с LiveCD

В Линукс можно сделать ВСЁ что угодно, достаточно знать КАК !


Оффлайн
wtor

Сохраните home загрузившись с LiveCD, а с ним и сохранятся Ваши настройки. После переустановки верните его назад также загрузившись с LiveCD

Вы имеете ввиду не форматировать раздел home при переустановке? Если нет, то можно подробнее о этом способе, если не тяжело. Я просто новичок.


Оффлайн
archuser

wtor, на последнем скрине вроде же ясно написано: UUID корня не существует. Загружайтесь с LiveCD, монтируйте корень проблемной системы, правьте файл /mounted_root/etc/fstab и выполните update-grub. Как-то так. Удачи.


Оффлайн
wtor

wtor, на последнем скрине вроде же ясно написано: UUID корня не существует. Загружайтесь с LiveCD, монтируйте корень проблемной системы, правьте файл /mounted_root/etc/fstab и выполните update-grub. Как-то так. Удачи.

Я пробовал это.
В итоге после

tune2fs -U uuid /dev/sda1
получил

the uuid may only be changed when the filesystem is unmounted


Оффлайн
archuser

Ну так опять же написано, чтобы сменить UUID раздела, его (раздел диска) сначала нужно размонтировать.


Оффлайн
wtor


Оффлайн
Heider

Я просто новичок.

Загрузитесь с LiveUSB, выберите пункт «Попробовать без установки», вызовите терминал и выполните в нем:

lsblk -fнайдите раздел с корнем своей системы, срисуйте его UUID
смонтируйте этот раздел куда-нибудь, например в /mnt
откройте файл

sudo nano /mnt/etc/fstab, найдите строчку с корнем и поправьте там UUID.


Оффлайн
wtor

Я просто новичок.

Загрузитесь с LiveUSB, выберите пункт «Попробовать без установки», вызовите терминал и выполните в нем:
lsblk -fнайдите раздел с корнем своей системы, срисуйте его UUID
смонтируйте этот раздел куда-нибудь, например в /mnt
откройте файл sudo nano /mnt/etc/fstab, найдите строчку с корнем и поправьте там UUID.

В файле и в выводе совпадают UUID


Оффлайн
symon.2014

Покажите что там в fstab


Оффлайн
wtor

Покажите что там в fstab
cat /etc/fstab

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda7 during installation
UUID=145bd829-80ca-4bf4-a168-10d58efaa30b /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=E686-02C4  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda9 during installation
UUID=2cff000b-b6a2-44e6-97d6-b9e831a48589 /home           ext4    defaults        0       2
# /windows1 was on /dev/sda4 during installation
UUID=9C54B4ED54B4CAF2 /windows1       ntfs    defaults,umask=007,gid=46 0       0
# /windows2 was on /dev/sda5 during installation
UUID=0EDCDFE1DCDFC0DF /windows2       ntfs    defaults,umask=007,gid=46 0       0
# /windows3 was on /dev/sda6 during installation
UUID=90623D34623D2080 /windows3       ntfs    defaults,umask=007,gid=46 0       0
# swap was on /dev/sda8 during installation
UUID=1674e267-e04e-45b7-bd7e-68f7e44702a8 none            swap    sw              0       0


Пользователь добавил сообщение 05 Марта 2017, 20:23:01:


Пробовал обновлять initramfs.

/usr/sbin/update-initramfs -u -k all Безуспешно.

« Последнее редактирование: 05 Марта 2017, 20:23:01 от wtor »


Оффлайн
archuser

wtor, вы выполняли команду update-grub? 


Оффлайн
wtor

wtor, вы выполняли команду update-grub?

Нет не выполнял. Просто выполнить эту команду? Или предварительно что-то сделать?


Оффлайн
archuser

sudo update-grub --output=/mnt/boot/grub/grub.cfgгде mnt — каталог с примонтированным корнем.


Оффлайн
wtor

sudo update-grub --output=/mnt/boot/grub/grub.cfgгде mnt — каталог с примонтированным корнем.

В chroot окружении:

sudo update-grub --output=/mnt/boot/grub/grub.cfg
sudo: unable to resolve host ubuntu: Connection refused
/usr/sbin/grub-mkconfig: 250: /usr/sbin/grub-mkconfig: cannot create /mnt/boot/grub/grub.cfg.new: Directory nonexistent
В LiveCD:

sudo update-grub --output=/mnt/boot/grub/grub.cfg
/usr/sbin/grub-probe: error: failed to get canonical path of `aufs'.


Как правильно задавать вопросы

Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. указывать 2, 3 и 4 того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот

Аватара пользователя

demonlibra

Сообщения: 835
Зарегистрирован: 12 авг 2017, 09:09
Решено: 13
Откуда: Ростов-на-Дону
Благодарил (а): 29 раз
Поблагодарили: 198 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 12:37

Решение нашёл здесь:

Загрузиться до initramfs

cryptsetup luksOpen /dev/sda3 sda3_crypt
lvm vgchange -a y
exit

Система должна загрузиться
Проверить crypttab и fstab

sudo nano /etc/crypttab
sudo nano /etc/fstab

update-initramfs -k all -c
Не должно быть ошибок

sudo -i
cryptsetup luksOpen /dev/sda5 sda5_crypt

# (do any lvm management you need here, I didn’t need any.)

mkdir /mnt/system
mount /dev/mapper/ubuntu—vg-root /mnt/system
mount /dev/sda2 /mnt/system/boot
mount /dev/sda1 /mnt/system/boot/efi (May or may not be needed.)

for i in /dev/pts /dev /proc /sys; do mount -B $i /mnt/system$i; done

chroot /mnt/system
update-initramfs -k all -c
exit

for i in /dev/pts /dev /proc /sys; do umount /mnt/system$i; done
umount /mnt/system/boot/efi # (If you have UEFI.)
umount /mnt/system/boot
umount /mnt/system

Reboot and hope it works.


Аватара пользователя

symon2014

Сообщения: 5432
Зарегистрирован: 16 дек 2017, 21:59
Решено: 31
Откуда: Феодосия
Благодарил (а): 32 раза
Поблагодарили: 666 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 12:42

Вариант три. Не устраивать паранойю с шифрованием.


Аватара пользователя

demonlibra

Сообщения: 835
Зарегистрирован: 12 авг 2017, 09:09
Решено: 13
Откуда: Ростов-на-Дону
Благодарил (а): 29 раз
Поблагодарили: 198 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 15:49

Шифрование актуально на ноутбуке, которому в любой момент могут приделать ноги.


Аватара пользователя

symon2014

Сообщения: 5432
Зарегистрирован: 16 дек 2017, 21:59
Решено: 31
Откуда: Феодосия
Благодарил (а): 32 раза
Поблагодарили: 666 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 15:54

demonlibra писал(а):

30 мар 2023, 15:49

Шифрование актуально

Позволь не поверить. Навернётся диск , это будет хуже приделанных ног. И не хранишь же ты наличные в ноуте. Всё относительно.


Аватара пользователя

slant

Сообщения: 4242
Зарегистрирован: 21 июн 2017, 18:09
Решено: 82
Благодарил (а): 51 раз
Поблагодарили: 1829 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 16:10

symon2014 писал(а):

30 мар 2023, 15:54

Навернётся диск , это будет хуже приделанных ног.

Ты ему через плечо ассистировал, или хрустальный шар прикупил, чтобы такое утверждать? :)
Как раз на рабочих ноутах бывает, что потеря данных/диска — мелочи по сравнению с их попаданием не в те руки. Особенно когда на ноуте — это рабочая, а не единственная копия (т.е. настроен нормальный бекап/синхронизация).


Аватара пользователя

symon2014

Сообщения: 5432
Зарегистрирован: 16 дек 2017, 21:59
Решено: 31
Откуда: Феодосия
Благодарил (а): 32 раза
Поблагодарили: 666 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 16:17

, У меня вагон хрустальных шаров)) Я просто уверен , что тот кому есть что прятать от чужих глаз , рук и ног , умеет это делать. И к тому же вряд ли он будеть создавать тему на подобном форуме об исправлении каких то там ошибок. Он их просто не допустит. Примерно где то так.
Так же меня умиляют темы о Кали линукс , типа всю жизнь мечтал проверить свою безопасность ))


Аватара пользователя

slant

Сообщения: 4242
Зарегистрирован: 21 июн 2017, 18:09
Решено: 82
Благодарил (а): 51 раз
Поблагодарили: 1829 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 16:53

symon2014 писал(а):

30 мар 2023, 16:17

умеет это делать

Прямо вот так и родился со знаниями. Или по воздуху получил?

symon2014 писал(а):

30 мар 2023, 16:17

И к тому же вряд ли он будеть создавать тему на подобном форуме об исправлении каких то там ошибок.

Я тут неоднократно писал по разные вещи — как решал возникшую проблему. Почему другим так нельзя?

Форум создан для обмена опытом. И темы где человек пишет, как он свои проблемы решал — на вес золота, т.к. человек не только сам думал, но и с другими своим опытом поделился.
И твое отношение — крайне неуместно.

symon2014 писал(а):

30 мар 2023, 16:17

Так же меня умиляют темы о Кали линукс , типа всю жизнь мечтал проверить свою безопасность ))

Каким боком ЭТО здесь. Мне кажется, ты просто опять начинаешь брюзжать без разбора на всех, как уже раз было. Не надо так, ладно?


Аватара пользователя

symon2014

Сообщения: 5432
Зарегистрирован: 16 дек 2017, 21:59
Решено: 31
Откуда: Феодосия
Благодарил (а): 32 раза
Поблагодарили: 666 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 17:05

slant писал(а):

30 мар 2023, 16:53

Каким боком ЭТО здесь. Мне кажется,

Вообще то я предложил третий вариант решения проблемы. Что бы героически не преодолевать глюки с шифрованием, лучше не шифровать. Я практически уверен , что не было в этом супер острой и жизненно необходимой потребности.
А упоминание о Кали , просто посторонний пример , как использовать для отмазки притянутые оправдания.


Аватара пользователя

demonlibra

Сообщения: 835
Зарегистрирован: 12 авг 2017, 09:09
Решено: 13
Откуда: Ростов-на-Дону
Благодарил (а): 29 раз
Поблагодарили: 198 раз
Контактная информация:

Gave up waiting for root file system device

30 мар 2023, 18:33

symon2014 писал(а):

30 мар 2023, 15:54

Навернётся диск , это будет хуже приделанных ног

symon2014 писал(а):

30 мар 2023, 16:17

И к тому же вряд ли он будеть создавать тему на подобном форуме об исправлении каких то там ошибок.

Есть такой грешок. Периодически использую форум, как записную книжку.


michaelzap

Level 3
Level 3
Posts: 166
Joined: Sat Sep 11, 2010 9:32 pm

«Gave up waiting for root device» on boot

Having some trouble installing the latest LMDE 64-bit on my Lenovo Y530 laptop. This is (potentially) a triple boot system with Windows 7 and LM Julia 64-bit. The Windows partition is encrypted with Truecrypt and uses the TC boot loader. On that boot loader’s prompt I press Esc and get Grub on the LM Julia partition. I ran update-grub after installing LMDE on the third partition (without Grub), and it found LMDE and added a Grub menu entry as expected. However, when I choose that entry the LMDE system says that’s it’s loading but then times out with the message «Gave up waiting for root device» and drops down to a busybox shell.

I’ve tried reinstalling (and formatting the partition to ext3 rather than ext4), but that doesn’t help.

Anyone know why this may be happening or how I can resolve it?

To clarify, I have four partitions total on my laptop:
/dev/sda1 — Windows 7 — encrypted by TrueCrypt and with the TC boot loader in the MBR
/dev/sda4 — LM Julia 64-bit (with Grub installed here)
/dev/sda2 — the non-functional LMDE 64-bit that I just installed
/dev/sda3 — swap

Code: Select all

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Linux Mint 10 64-bit, 2.6.35-22-generic (/dev/sda4)' --class linuxmint --class gnu-linux --class gnu --class os {	recordfail	insmod part_msdos	insmod ext2	set root='(hd0,msdos4)'	search --no-floppy --fs-uuid --set 1e25a31e-e6b0-4879-b32f-3619554f6e42	linux	/boot/vmlinuz-2.6.35-22-generic root=UUID=1e25a31e-e6b0-4879-b32f-3619554f6e42 ro quiet splash	initrd	/boot/initrd.img-2.6.35-22-generic
}
menuentry 'Linux Mint 10 64-bit, 2.6.35-22-generic (/dev/sda4) -- recovery mode' --class linuxmint --class gnu-linux --class gnu --class os {	recordfail	insmod part_msdos	insmod ext2	set root='(hd0,msdos4)'	search --no-floppy --fs-uuid --set 1e25a31e-e6b0-4879-b32f-3619554f6e42	echo	'Loading Linux 2.6.35-22-generic ...'	linux	/boot/vmlinuz-2.6.35-22-generic root=UUID=1e25a31e-e6b0-4879-b32f-3619554f6e42 ro single	echo	'Loading initial ramdisk ...'	initrd	/boot/initrd.img-2.6.35-22-generic
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {	insmod part_msdos	insmod ext2	set root='(hd0,msdos4)'	search --no-floppy --fs-uuid --set 1e25a31e-e6b0-4879-b32f-3619554f6e42	linux16	/boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {	insmod part_msdos	insmod ext2	set root='(hd0,msdos4)'	search --no-floppy --fs-uuid --set 1e25a31e-e6b0-4879-b32f-3619554f6e42	linux16	/boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-amd64 (on /dev/sda2)" {	insmod part_msdos	insmod ext2	set root='(hd0,msdos2)'	search --no-floppy --fs-uuid --set ef555c74-bd68-45a0-a686-0334c67adb5c	linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=1f084bbd-a556-4e8b-9ab4-c9049cfda7e3 ro quiet	initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode) (on /dev/sda2)" {	insmod part_msdos	insmod ext2	set root='(hd0,msdos2)'	search --no-floppy --fs-uuid --set ef555c74-bd68-45a0-a686-0334c67adb5c	linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=1f084bbd-a556-4e8b-9ab4-c9049cfda7e3 ro single	initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/30_os-prober ###

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Re: «Gave up waiting for root device» on boot


by » Sat Dec 25, 2010 6:30 am

Hi!
I don’t know if I can help, because your situation is complex and I never heard of TC boot loader.
First we should find out where Grub is installed:
Please run as root:

Code: Select all

fdisk -l 2>/dev/null | egrep "Disk /|/dev/" | sed "s#^/dev/#Part /dev/#" | awk '{print $2}' | sed 's/://' | xargs -n1 -IX sudo sh -c "hexdump -v -s 0x80 -n 2 -e '2/1 \"%x\" \"\\n\"' X | xargs -n1 -IY sh -c \"case \"Y\" in '48b4') echo X: GRUB 2 v1.96 ;; 'aa75' | '5272') echo X: GRUB Legacy ;; '7c3c') echo X: GRUB 2 v1.97 or higher ;; *) echo X: No GRUB Y ;; esac\""

Re: «Gave up waiting for root device» on boot


by » Sat Dec 25, 2010 6:45 pm

I thought I could help, because I had the same problem (LMDE-64bit boot drops down to shell, with similar messaging), but on my Toshiba the problem solved itself on the third try.

(I have a dual boot with Mint Julia 64-bit, so I doubt it’s a triple boot problem.)

It seems like the UUID listed in Grub didn’t match the actual UUID, but I can’t be certain, as I was expecting to reproduce the problem to see what UUID the message gave and check that against the actual UUID (given by blkid in a terminal). But since it booted correctly, so there’s no way to check. My only guess is that I installed LMDE twice, the second time choosing to place the LMDE Grub on the device with the LMDE /root (rather than not at all, which is what I did the first time). Perhaps when I ran update-grub in Julia it picked up the right UUID?

Hope this helps.

Re: «Gave up waiting for root device» on boot


by » Sun Dec 26, 2010 6:29 am

Hi!
A «normal» /etc/default/grub:

Code: Select all

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
...
GRUB_GFXMODE=800x600

and part of a /boot/grub/grub.cfg :

Code: Select all

...
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Home Edition (on /dev/sda1)" {	insmod part_msdos	insmod ntfs	set root='(hd0,msdos1)'	search --no-floppy --fs-uuid --set b6c411c6c4118a2f	drivemap -s (hd0) ${root}	chainloader +1
}
menuentry "Linux Mint 9, 2.6.32-22-generic (/dev/sda6) (on /dev/sda6)" {	insmod part_msdos	insmod ext2	set root='(hd0,msdos6)'	search --no-floppy --fs-uuid --set f2c6fecb-3195-481b-9b6f-21677dff3e2e	linux /boot/vmlinuz-2.6.32-22-generic root=UUID=f2c6fecb-3195-481b-9b6f-21677dff3e2e ro quiet splash	initrd /boot/initrd.img-2.6.32-22-generic
}
...

michaelzap

Level 3
Level 3
Posts: 166
Joined: Sat Sep 11, 2010 9:32 pm

Re: «Gave up waiting for root device» on boot


by michaelzap » Tue Dec 28, 2010 4:25 pm

Thanks for your replies. Between Xmas and the forums being down I didn’t have a chance to report back until now. It turns out that the automatically-discovered UUID for the LMDE partition was wrong. Dunno why that would be, but it’s a general Grub problem, I guess, and not specifically a LMDE problem (it was actually Grub on my regular LM Julia installation that got the UUID wrong on update). All I did was to look up the correct UUID (I used gparted to do this, since I’m not ashamed to admit that I use GUI apps whenever I can) and edit the rub config file and it booted as expected. As this is a testing installation anyway, I’m not going to investigate it further. If it happens to me again on a real installation I’ll start looking through bug reports.

Re: «Gave up waiting for root device» on boot


by » Wed Dec 29, 2010 3:48 pm

Another one here with the same problem!
I am using original LMDE as my main system and i have installed, in a second partition, LMDE 64. I did not install grub, so, reboot to my primary LMDE, update-grub, reboot to LMDE -64 >game over :?
I got the same message, ending in a console. The final words were ALERT and then the explanation that the UUID that it tries does not exist. So, i manually changed the UUID in grub.cfg and my problem solved.

Re: «Gave up waiting for root device» on boot


by » Thu Jan 13, 2011 3:13 pm

find: WARNING: Hard link count is wrong for .: this may be a bug in your filesystem driver. Automatically turning on find’s -noleaf option.

Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ============================== => Grub 0.97 is installed in the MBR of /dev/hdc and looks on boot drive #3 in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst. => No known boot loader is installed in the MBR of /dev/hdd => Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.
hdc1: _________________________________________________________________________ File system: ntfs Boot sector type: Windows XP Boot sector info: No errors found in the Boot Parameter Block. Operating System: Windows XP Boot files/dirs: /boot.ini /BOOT.INI /ntldr /NTLDR /NTDETECT.COM /ntdetect.com
hdd1: _________________________________________________________________________ File system: Extended Partition Boot sector type: Unknown Boot sector info:
hdd5: _________________________________________________________________________ File system: ntfs Boot sector type: Windows XP Boot sector info: According to the info in the boot sector, hdd5 starts at sector 63. Operating System: Boot files/dirs:
sda1: _________________________________________________________________________ File system: ext3 Boot sector type: - Boot sector info: Operating System: Ubuntu 10.04.1 LTS Boot files/dirs: /boot/grub/menu.lst /etc/fstab
sda2: _________________________________________________________________________ File system: Extended Partition Boot sector type: - Boot sector info:
sda5: _________________________________________________________________________ File system: swap Boot sector type: - Boot sector info:
hda: _________________________________________________________________________ File system: iso9660 Boot sector type: - Boot sector info: Operating System: Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: hdc ___________________ _____________________________________________________
Disk /dev/hdc: 41.1 GB, 41110142976 bytes
255 heads, 63 sectors/track, 4998 cylinders, total 80293248 sectors
Units = sectors of 1 * 512 = 512 bytes
Partition Boot Start End Size Id System
/dev/hdc1 * 63 80,276,804 80,276,742 7 HPFS/NTFS
Drive: hdd ___________________ _____________________________________________________
Disk /dev/hdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Partition Boot Start End Size Id System
/dev/hdd1 16,065 976,768,064 976,752,000 f W95 Ext d (LBA)
/dev/hdd5 16,128 976,768,064 976,751,937 7 HPFS/NTFS
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 * 63 961,570,574 961,570,512 83 Linux
/dev/sda2 961,570,575 976,768,064 15,197,490 5 Extended
/dev/sda5 961,570,638 976,768,064 15,197,427 82 Linux swap / Solaris
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/evms/hdc1 ntfs
/dev/evms/hdd5 ntfs
/dev/evms/sda1 667da5eb-f73d-4df0-8818-890edab5c8b7 ext3
/dev/evms/sda5 a453daf0-813e-4833-bda8-e23297071343 swap
/dev/hda iso9660
/dev/hdc1 ntfs
/dev/hdd5 ntfs
/dev/sda1 667da5eb-f73d-4df0-8818-890edab5c8b7 ext3
/dev/sda5 a453daf0-813e-4833-bda8-e23297071343 swap
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
unionfs / unionfs (rw)
/dev/sda1 /mnt ext3 (rw)
================================ hdc1/boot.ini: ================================
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Media Center Edition" /noexecute=optin /fastdetect 11111
================================ hdc1/BOOT.INI: ================================
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Media Center Edition" /noexecute=optin /fastdetect 11111
=========================== sda1/boot/grub/menu.lst: ===========================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default	4
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout	10
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title	Windows 95/98/NT/2000
# root	(hd0,0)
# makeactive
# chainloader	+1
#
# title	Linux
# root	(hd0,1)
# kernel	/vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd2,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## specify if running in Xen domU or have grub detect automatically
## update-grub will ignore non-xen kernels when running in domU and vice versa
## e.g. indomU=detect
## indomU=true
## indomU=false
# indomU=detect
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title	Ubuntu 8.04.2, kernel 2.6.24-24-386
root	(hd2,0)
kernel	/boot/vmlinuz-2.6.24-24-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro quiet splash
initrd	/boot/initrd.img-2.6.24-24-386
title	Ubuntu 8.04.2, kernel 2.6.24-24-386 (recovery mode)
root	(hd2,0)
kernel	/boot/vmlinuz-2.6.24-24-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro single
initrd	/boot/initrd.img-2.6.24-24-386
# title	Ubuntu 8.04.2, kernel 2.6.24-23-386
# root	(hd2,0)
# kernel	/boot/vmlinuz-2.6.24-23-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro quiet splash
# initrd	/boot/initrd.img-2.6.24-23-386
# title	Ubuntu 8.04.2, kernel 2.6.24-23-386 (recovery mode)
# root	(hd2,0)
# kernel	/boot/vmlinuz-2.6.24-23-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro single
# initrd	/boot/initrd.img-2.6.24-23-386
# title	Ubuntu 8.04.2, kernel 2.6.24-22-386
# root	(hd2,0)
# kernel	/boot/vmlinuz-2.6.24-22-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro quiet splash
# initrd	/boot/initrd.img-2.6.24-22-386
# title	Ubuntu 8.04.2, kernel 2.6.24-22-386 (recovery mode)
# root	(hd2,0)
# kernel	/boot/vmlinuz-2.6.24-22-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro single
# initrd	/boot/initrd.img-2.6.24-22-386
#title	Ubuntu 8.04.2, kernel 2.6.24-21-386
#root	(hd2,0)
#kernel	/boot/vmlinuz-2.6.24-21-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro quiet splash
#initrd	/boot/initrd.img-2.6.24-21-386
#title	Ubuntu 8.04.2, kernel 2.6.24-21-386 (recovery mode)
#root	(hd2,0)
#kernel	/boot/vmlinuz-2.6.24-21-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro single
#initrd	/boot/initrd.img-2.6.24-21-386
#title	Ubuntu 8.04.2, kernel 2.6.24-19-386
#root	(hd2,0)
#kernel	/boot/vmlinuz-2.6.24-19-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro quiet splash
#initrd	/boot/initrd.img-2.6.24-19-386
#title	Ubuntu 8.04.2, kernel 2.6.24-19-386 (recovery mode)
#root	(hd2,0)
#kernel	/boot/vmlinuz-2.6.24-19-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro single
#initrd	/boot/initrd.img-2.6.24-19-386
#title	Ubuntu 8.04.2, kernel 2.6.15-52-386
#root	(hd2,0)
#kernel	/boot/vmlinuz-2.6.15-52-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro quiet splash
#initrd	/boot/initrd.img-2.6.15-52-386
#title	Ubuntu 8.04.2, kernel 2.6.15-52-386 (recovery mode)
#root	(hd2,0)
#kernel	/boot/vmlinuz-2.6.15-52-386 root=UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 ro single
#initrd	/boot/initrd.img-2.6.15-52-386
title	Ubuntu 8.04.2, memtest86+
root	(hd2,0)
kernel	/boot/memtest86+.bin
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title	Other operating systems:
root
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title	Windows XP Media Center Edition
root	(hd0,0)
savedefault
makeactive
chainloader	+1
=============================== sda1/etc/fstab: ===============================
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 -- converted during upgrade to edgy
UUID=667da5eb-f73d-4df0-8818-890edab5c8b7 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5 -- converted during upgrade to edgy
UUID=a453daf0-813e-4833-bda8-e23297071343 none swap sw 0 0
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0
# /dev/hdb5 -- converted during upgrade to edgy
UUID=A8FCDB1BFCDAE29C /mnt/win ntfs-3g auto,gid=1001,umask=0,locale=ru_RU.utf8 0 0
=================== sda1: Location of files loaded by Grub: =================== 167.1GB: boot/grub/menu.lst 167.2GB: boot/grub/stage2 167.1GB: boot/initrd.img-2.6.15-52-386 167.3GB: boot/initrd.img-2.6.24-24-386 167.1GB: boot/initrd.img-2.6.24-24-386.bak 167.3GB: boot/initrd.img-2.6.32-25-386 167.3GB: boot/initrd.img-2.6.32-25-generic 167.1GB: boot/vmlinuz-2.6.15-52-386 167.2GB: boot/vmlinuz-2.6.24-24-386 167.2GB: boot/vmlinuz-2.6.32-25-386 167.2GB: boot/vmlinuz-2.6.32-25-generic 167.3GB: initrd.img 167.3GB: initrd.img.old 167.2GB: vmlinuz 167.2GB: vmlinuz.old
=========================== Unknown MBRs/Boot Sectors/etc =======================
Unknown MBR on /dev/hdd
00000000 33 ca 8e da bc 0a 7c fb 50 0f 50 1f fc be 1b 7e |3.....|.P.P....~|
00000010 bf 1b 06 5a 57 bb e5 0b f3 ae cb bf be 0f b1 0e |...ZW...........|
00000020 38 6e 00 7e 09 7f 13 8b c5 1a e2 fe cd 1a 8b ff |8n.~............|
00000030 83 ce 10 4b 74 1b 38 2e 74 fe a0 bf 07 be 07 8b |...Kt.8.t.......|
00000040 f0 ae 3c 0a 74 fe bb 0f 00 be 0e cf 10 eb f2 8a |..<.t...........|
00000050 4e 1a e8 4e 00 7b 2a fe 46 1a 80 7e 04 0b 74 0b |N..N.{*.F..~..t.|
00000060 80 7e 04 0e 74 0f a0 be 07 7f d2 8a 46 0a 06 8b |.~..t.......F...|
00000070 46 0a 06 8b 56 0a 00 ea 21 0a 73 0f a0 be 07 eb |F...V...!.s.....|
00000080 bc 8b 3e fe 7d 5f aa 7e 0b 8a 7e 1a 00 7e c8 aa |..>.}_.~..~..~..|
00000090 b7 0f eb ab 8b fe 1e 5f 8b ff cb bf 05 0a 8a 5e |......._.......^|
000000a0 00 be 08 cf 13 7a 23 8a c1 2e 3f 9a 8a de 8a fe |.....z#...?.....|
000000b0 43 ff e3 8b d1 8e d6 bb 06 da ee 4a f7 ea 39 5e |C..........J..9^|
000000c0 0a 7f 23 7a 05 3b 46 0a 73 1e b8 0b 02 bb 00 7e |..#z.;F.s......~|
000000d0 8b 4e 02 8b 56 0a cd 1b 73 5b 4f 7e 4e 3a e4 8a |.N..V...s[O~N:..|
000000e0 56 0a cd 1b eb ee 8a 5e 00 6a bb aa 55 be 41 cf |V......^.j..U.A.|
000000f0 13 7a 36 8b fb 5f aa 7f 30 fe c1 0b 74 2b 61 6a |.z6.._..0...t+aj|
00000100 6a 0a 6a 0a ff 7e 0a ff 76 0a 6a 0a 68 0a 7c 6a |j.j..~..v.j.h.|j|
00000110 01 6a 10 be 42 8b f4 cf 13 6b 61 7b 0e 4f 74 0b |.j..B....ka{.Ot.|
00000120 32 ee 8a 5e 00 cf 13 eb d6 6b f9 cb 49 6e 76 6b |2..^.....k..Invk|
00000130 6c 6b 64 2a 70 6b 72 7e 69 7e 69 6f 6e 2a 74 6b |lkd*pkr~i~ion*tk|
00000140 62 6e 65 0a 45 7a 72 6f 72 2a 6c 6f 61 6e 69 6e |bne.Ezror*loanin|
00000150 67 2a 6f 7a 65 7a 61 7e 69 6e 67 2a 73 7b 73 7e |g*ozeza~ing*s{s~|
00000160 65 6f 00 4f 69 7b 73 6b 6e 6f 20 6f 70 6f 72 6b |eo.Oi{skno opork|
00000170 74 6b 6e 6f 20 7b 79 7b 74 6f 6d 0a 00 0a 00 0a |tkno {y{tom.....|
00000180 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a |................|
00000190 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a |................|
000001a0 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a 00 0a |................|
000001b0 00 0a 00 0a 00 2e 44 6b c2 8e 60 ff 00 0a 00 00 |......Dk..`.....|
000001c0 01 01 0f fe ff ff c1 3e 00 00 80 0d 38 3a 00 00 |.......>....8:..|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
Unknown BootLoader on hdd1
00000000 10 80 10 80 10 80 10 80 10 80 10 80 10 80 10 80 |................|
*
000001b0 10 80 10 80 10 80 10 80 10 80 10 80 10 80 00 01 |................|
000001c0 01 01 07 fe ff ff 3f 00 00 00 41 0d 38 3a 00 00 |......?...A.8:..|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
=============================== StdErr Messages: =============================== No volume groups found
mdadm: No arrays found in config file

Gave up waiting for root device.

ubuntu@ubuntu:~$ cat /proc/cmdline
initrd=/ubninit file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash -- BOOT_IMAGE=/ubnkern
ubuntu@ubuntu:~$ sudo fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000 Device Boot Start End Blocks Id System
/dev/sda1 1 234441647 117220823+ ee GPT
/dev/sda2 * 0 0 0 0 Empty
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000 Device Boot Start End Blocks Id System
/dev/sdb1 * 2 3907029167 1953514583 af HFS / HFS+
Partition 1 does not start on physical sector boundary.
Disk /dev/sdc: 32.0 GB, 32008830976 bytes
255 heads, 63 sectors/track, 3891 cylinders, total 62517248 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18 Device Boot Start End Blocks Id System
/dev/sdc1 * 32 62517247 31258608 c W95 FAT32 (LBA)
Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000df45c Device Boot Start End Blocks Id System
/dev/sdd1 * 2 976773167 488386583 83 Linux
ubuntu@ubuntu:~$

Last edited by m�rg�s; March 1st, 2015 at .

Please post in CODE tags for terminal output

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

nano /etc/fstab (while chroot) :

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdd1 during installation
UUID=0f3554b3-3704-43fb-9358-9dbc69e8834d / ext4 errors=remount-ro 0 1
# swap was on /dev/sdd5 during installation
UUID=ac42196f-3674-4fb2-8652-cb44184af99f none swap sw 0 0

blkid (while chroot) :

/dev/sda1: LABEL="EFI" UUID="67E3-17ED" TYPE="vfat"
/dev/sda2: UUID="08440460-cf60-3686-af75-b65fa94eef8f" LABEL="HACKINTOSH" TYPE="hfsplus"
/dev/sda3: UUID="8309a303-f6a7-3ebe-b7b9-b1ecae7647ea" LABEL="Recovery HD" TYPE="hfsplus"
/dev/sdb1: UUID="60bbb74d-252a-343b-9ae1-55e0d1c73b49" LABEL="Minerva" TYPE="hfsplus"
/dev/loop0: TYPE="squashfs"
/dev/sdc1: LABEL="Lexar" UUID="93A0-E59E" TYPE="vfat"
/dev/sdd1: UUID="0f3554b3-3704-43fb-9358-9dbc69e8834d" TYPE="ext4"
/dev/sdd5: UUID="ac42196f-3674-4fb2-8652-cb44184af99f" TYPE="swap"

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

Hi everyone!

I haven’t been able to get rid of this boot issue and worked on it for days now. I have succesfully installed distros and ran them fine before, the disk works fine ’cause I’ve checkdisked the hell out of it.

Here is the message I have :

Gave up waiting on root device. Common problems:

Then my computer wether stops responding OR gets stuck in a loop where it tries to install whatever is connected to USB (MOUSE) in a loop and always fails and tries again.

Here are the things I have tried (googling the issue) :

2. Tried fsck

3. From live CD : sudo grub-install /dev/sdd1 : sudo update grub

4. From live CD install grub / update grub as CHROOT

5. I also tried many other things but since I am frustrated and have tried so many things, I don’t think I can recall exactly everything I did.

Here is my hardware specs if it can help :

Gigabyte Z68XP-UD4
Sandy Bridge — i7 2600K
HyperX 1600Mhz DDR (16Gb)
Main drive Samsung 120Gb SSD (OSX with Chimera bootloader (Unibeast / multibeast installation)
WD 500Gb (Linux install or at least, the drive that I’m trying to use.)
2Tb drive for data and backups, etc.
Airport extreme adapter ripped off an old imac, soldered to a PCI adapter
MSI Geforce GTX 760 twin frozr (2Gb) (2 screens connected / one via HDMI and the other via DVI)

Other stuff connected : Zoom R16 recording interface, HP Deskjet all in one printer/scanner

tgalati4's Avatar

March 1st, 2015

Gave up waiting for root device.

additionaly, I checked with parted :

ubuntu@ubuntu:~$ sudo parted -l
Model: ATA Corsair Force 3 (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags 1 20.5kB 210MB 210MB fat32 EFI System Partition boot 2 210MB 119GB 119GB hfs+ HACKINTOSH 3 119GB 120GB 650MB hfs+ Recovery HD
Model: ATA ST2000DM001-1CH1 (scsi)
Disk /dev/sdb: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Number Start End Size Type File system Flags 1 1024B 2000GB 2000GB primary hfs+ boot
Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdc: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags 1 16.4kB 32.0GB 32.0GB primary fat32 boot, lba
Model: ATA WDC WD5000AAKX-0 (scsi)
Disk /dev/sdd: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags 1 1024B 500GB 500GB primary ext4 boot

I found places where they suggest to add rootdelay=XXX to grub menu.lt, that file doesn’t seem to be where they suggest it should be.

But here’s my grub.cfg :

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env
fi
if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true
else set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id"
else menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true
fi
function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi
}
function recordfail { set recordfail=1 if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi
}
if [ x$feature_default_font_path = xy ] ; then font=unicode
else
insmod part_msdos
insmod ext2
set root='hd3,msdos1'
if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0
else search --no-floppy --fs-uuid --set=root c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0
fi font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=en_CA insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then set timeout=-1
else if [ x$feature_timeout_style = xy ] ; then set timeout_style=hidden set timeout=0 # Fallback hidden-timeout code in case the timeout_style feature is # unavailable. elif sleep --interruptible 0 ; then set timeout=0 fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 44,0,30,0; then clear
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode { set gfxpayload="${1}" if [ "${1}" = "keep" ]; then set vt_handoff=vt.handoff=7 else set vt_handoff= fi
}
if [ "${recordfail}" != 1 ]; then if [ -e ${prefix}/gfxblacklist.txt ]; then if hwmatch ${prefix}/gfxblacklist.txt 3; then if [ ${match} = 0 ]; then set linux_gfx_mode=keep else set linux_gfx_mode=text fi else set linux_gfx_mode=text fi else set linux_gfx_mode=keep fi
else set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0' { recordfail load_video gfxmode $linux_gfx_mode insmod gzio insmod part_msdos insmod ext2 set root='hd3,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 else search --no-floppy --fs-uuid --set=root c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 fi linux /boot/vmlinuz-3.16.0-30-generic root=UUID=c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 ro quiet splash $vt_handoff initrd /boot/initrd.img-3.16.0-30-generic
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0' { menuentry 'Ubuntu, with Linux 3.16.0-30-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-30-generic-advanced-c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0' { recordfail load_video gfxmode $linux_gfx_mode insmod gzio insmod part_msdos insmod ext2 set root='hd3,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 else search --no-floppy --fs-uuid --set=root c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 fi echo 'Loading Linux 3.16.0-30-generic ...' linux /boot/vmlinuz-3.16.0-30-generic root=UUID=c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 ro quiet splash $vt_handoff echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.16.0-30-generic } menuentry 'Ubuntu, with Linux 3.16.0-30-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-30-generic-recovery-c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0' { recordfail load_video insmod gzio insmod part_msdos insmod ext2 set root='hd3,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 else search --no-floppy --fs-uuid --set=root c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 fi echo 'Loading Linux 3.16.0-30-generic ...' linux /boot/vmlinuz-3.16.0-30-generic root=UUID=c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 ro recovery nomodeset echo 'Loading initial ramdisk ...' initrd /boot/initrd.img-3.16.0-30-generic }
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memory test (memtest86+)' { insmod part_msdos insmod ext2 set root='hd3,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 else search --no-floppy --fs-uuid --set=root c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 fi knetbsd /boot/memtest86+.elf
}
menuentry 'Memory test (memtest86+, serial console 115200)' { insmod part_msdos insmod ext2 set root='hd3,msdos1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 else search --no-floppy --fs-uuid --set=root c95d47fa-e0d3-4a54-b679-1c1d94cf6fa0 fi linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

I just had a flash, last week I ordered an Odroid C1 and created a microSD using Disk Destroyer (dd) and I might have made some mistakes cause I had to start over a few times.

Could Disk Destroyer cause something to the disk identification or something? Is there a way to fix it if it’s the case?

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

I’m confused. But I can explain everything there.

Disk /dev/sda
This is my SSD, it has OSX and it boots perfectly fine.

Disk /dev/sdb
This is my drive called «Minerva» and it’s 2Tb drive used to store my pictures / videos / music, etc.

Disk /dev/sdc
This is my LIVE USB UBUNTU 14.04 LTS

Disk /dev/sdd
This is where I’m trying to install UBUNTU as it always worked before,

Last edited by marc-andr2; March 1st, 2015 at .

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

I’m just so lost right now…

Booted once again with my USB LIVE (which works fine, I even rebuilt it and tested it)

Used the automatic installer using the whole disk, it told me it failed installing grub to /dev/sda, but that’s my OSX drive and it’s hfs+ so obviously linux can’t write there. Then I had the option to install bootloader elsewhere, so I picked /dev/sdd, which is my linux 500Gb drive.

— reboot gives me the exact same error message =

Gave up waiting on root device. Common problems:

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

I’m trying to install once again, this time I’m installing using : install ubuntu alongside… Just to see if the modification it’ll make to grub might get me through… and it popped up : Executing grub-install /dev/sda failed. I know linux can’t write to my HFS+ partition. Why would it try to do that tho? I asked the installer to install bootloader to sdd… I’m just about to throw my fist through my screens and throw that thing out the window…

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Gave up waiting for root device.

I just did dd if=/dev/zero of=/dev/sdd bs=100M

Gave up waiting for root device.

What is the output of:Perhaps you don’t have the boot flag set on the same partition that you have grub installed to. You can check with a LiveUSB session and use gparted to inspect and change it if necessary under «manage flags».

Also post the output of the disk partitions:

Pull out the 120 GB SSD. I’m sure that is tripping up the drive enumeration.

Last edited by tgalati4; March 1st, 2015 at .

————————————-
Oooh Shiny: PopularPages

Unumquodque potest reparantur. Patientia sit virtus.

"Gave up waiting for root device.", (initramfs)

March 1st, 2015

Boot problem — «Gave up waiting for root device. «, (initramfs)

I tried editing grub as suggested in post #2. No dice. I’ve been fighting with this problem for a couple weeks now! I’m relatively new to Linux, but do know to search for solutions. I’ve tried the Linux Mint forums (I’m using Mint 10, which is Ubuntu 10.10 based) and Linux Questions. Several «solutions», but none work.

Some solutions suggest booting from the Live CD (which boots and works fine!) and mounting the drive manually, but when I try that I get a «device doesn’t exist» error. The first time I got that I used gparted to look at the drive, and it finds it fine, just says there is no boot info on it.

I have an Athlon XP 2400+ processor, Radeon 8200 video card, 1 GB RAM, on an old FIC AZ31 motherboard (VIA KT133 chipset, VT 8363 North Bridge and 686A Super South), 120GB Maxtor 5400 rpm IDE hard drive. Mint 7 (Ubuntu 9.04) boots and installs flawlessly on this system. I’d really like a solution! This is my «shop» experimenting machine. If I can’t get Mint 10 (Ubuntu 10.10) to run on it I’m not about to attempt and upgrade on my main machine!

Here is the output from Bootinfo Script:

Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for (,msdos1)/boot/grub.
=> Windows is installed in the MBR of /dev/sdc
sda1: _________________________________________________________________________
File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed:
mount: unknown filesystem type ''
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: Unknown
Boot sector info:
sda5: _________________________________________________________________________
File system:
Boot sector type: Unknown
Boot sector info:
Mounting failed:
mount: unknown filesystem type ''
mount: unknown filesystem type ''
sdc1: _________________________________________________________________________
File system: vfat
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 122.9 GB, 122942324736 bytes
255 heads, 63 sectors/track, 14946 cylinders, total 240121728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 * 2,048 239,933,439 239,931,392 83 Linux
/dev/sda2 239,935,486 240,119,807 184,322 5 Extended
/dev/sda5 239,935,488 240,119,807 184,320 82 Linux swap / Solaris
Drive: sdc ___________________ _____________________________________________________
Disk /dev/sdc: 517 MB, 517521408 bytes
128 heads, 32 sectors/track, 246 cylinders, total 1010784 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sdc1 * 32 1,010,782 1,010,751 4 FAT16 <32M
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda: PTTYPE="dos"
/dev/sdc1 vfat LEXAR MEDIA
/dev/sdc: PTTYPE="dos"
error: /dev/sda1: No such file or directory
error: /dev/sda2: No such file or directory
error: /dev/sda5: No such file or directory
error: /dev/sdb: No medium found
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
aufs / aufs (rw)
/dev/sr1 /cdrom iso9660 (ro,noatime)
/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdc1 /media/LEXAR MEDIA vfat (rw,nosuid,nodev,uhelper=udisks,uid=999,gid=999,shortname=mixed,dmask=0077,utf8=1,showexec,flush)
=========================== Unknown MBRs/Boot Sectors/etc =======================
Unknown BootLoader on sda1
Unknown BootLoader on sda2
Unknown BootLoader on sda5
Unknown BootLoader on sdc1
00000000 eb 3c 90 4d 53 57 49 4e 34 2e 31 00 02 10 01 00 |.<.MSWIN4.1.....|
00000010 02 00 02 00 00 f8 f7 00 20 00 80 00 20 00 00 00 |........ ... ...|
00000020 3f 6c 0f 00 80 00 29 00 00 00 00 4e 4f 20 4e 41 |?l....)....NO NA|
00000030 4d 45 20 20 20 20 46 41 54 31 36 20 20 20 33 c9 |ME FAT16 3.|
00000040 8e d1 bc fc 7b 16 07 bd 78 00 c5 76 00 1e 56 16 |....{...x..v..V.|
00000050 55 bf 22 05 89 7e 00 89 4e 02 b1 0b fc f3 a4 06 |U."..~..N.......|
00000060 1f bd 00 7c c6 45 fe 0f 38 4e 24 7d 20 8b c1 99 |...|.E..8N$} ...|
00000070 e8 7e 01 83 eb 3a 66 a1 1c 7c 66 3b 07 8a 57 fc |.~...:f..|f;..W.|
00000080 75 06 80 ca 02 88 56 02 80 c3 10 73 ed 33 c9 fe |u.....V....s.3..|
00000090 06 d8 7d 8a 46 10 98 f7 66 16 03 46 1c 13 56 1e |..}.F...f..F..V.|
000000a0 03 46 0e 13 d1 8b 76 11 60 89 46 fc 89 56 fe b8 |.F....v.`.F..V..|
000000b0 20 00 f7 e6 8b 5e 0b 03 c3 48 f7 f3 01 46 fc 11 | ....^...H...F..|
000000c0 4e fe 61 bf 00 07 e8 28 01 72 3e 38 2d 74 17 60 |N.a....(.r>8-t.`|
000000d0 b1 0b be d8 7d f3 a6 61 74 3d 4e 74 09 83 c7 20 |....}..at=Nt... |
000000e0 3b fb 72 e7 eb dd fe 0e d8 7d 7b a7 be 7f 7d ac |;.r......}{...}.|
000000f0 98 03 f0 ac 98 40 74 0c 48 74 13 b4 0e bb 07 00 |.....@t.Ht......|
00000100 cd 10 eb ef be 82 7d eb e6 be 80 7d eb e1 cd 16 |......}....}....|
00000110 5e 1f 66 8f 04 cd 19 be 81 7d 8b 7d 1a 8d 45 fe |^.f......}.}..E.|
00000120 8a 4e 0d f7 e1 03 46 fc 13 56 fe b1 04 e8 c2 00 |.N....F..V......|
00000130 72 d7 ea 00 02 70 00 52 50 06 53 6a 01 6a 10 91 |r....p.RP.Sj.j..|
00000140 8b 46 18 a2 26 05 96 92 33 d2 f7 f6 91 f7 f6 42 |.F..&...3......B|
00000150 87 ca f7 76 1a 8a f2 8a e8 c0 cc 02 0a cc b8 01 |...v............|
00000160 02 80 7e 02 0e 75 04 b4 42 8b f4 8a 56 24 cd 13 |..~..u..B...V$..|
00000170 61 61 72 0a 40 75 01 42 03 5e 0b 49 75 77 c3 03 |aar.@u.B.^.Iuw..|
00000180 18 01 27 0d 0a 49 6e 76 61 6c 69 64 20 73 79 73 |..'..Invalid sys|
00000190 74 65 6d 20 64 69 73 6b ff 0d 0a 44 69 73 6b 20 |tem disk...Disk |
000001a0 49 2f 4f 20 65 72 72 6f 72 ff 0d 0a 52 65 70 6c |I/O error...Repl|
000001b0 61 63 65 20 74 68 65 20 64 69 73 6b 2c 20 61 6e |ace the disk, an|
000001c0 64 20 74 68 65 6e 20 70 72 65 73 73 20 61 6e 79 |d then press any|
000001d0 20 6b 65 79 0d 0a 00 00 49 4f 20 20 20 20 20 20 | key....IO |
000001e0 53 59 53 4d 53 44 4f 53 20 20 20 53 59 53 7f 01 |SYSMSDOS SYS..|
000001f0 00 41 bb 00 07 60 66 6a 00 e9 3b ff 00 00 55 aa |.A...`fj..;...U.|
00000200
=======Devices which don't seem to have a corresponding hard drive==============
sdb
=============================== StdErr Messages: ===============================
hexdump: /dev/sda1: No such file or directory
hexdump: /dev/sda1: No such file or directory
hexdump: /dev/sda2: No such file or directory
hexdump: /dev/sda2: No such file or directory
hexdump: /dev/sda5: No such file or directory
hexdump: /dev/sda5: No such file or directory

Last edited by drs305; February 22nd, 2011 at .

Added [code] [/code] tags. You can too, with the # icon in the menubar.

Дополнительно:  Пищит ноутбук. Что делать?
Оцените статью
Master Hi-technology