On Sun, Jan 29, 2012 at 12:05 AM, Gabriel <[email protected]> wrote: > > >> parted >> >> Acum arata cam asa: >> Number Start End Size File system Name >> Flags >> 1 20.5kB 537MB 537MB fat16 EFI System boot >> 2 537MB 9127MB 8590MB linux-swap(v1) Linux swap >> 3 9127MB 30,6GB 26.8GB ext3 Linux filesystem >> >> Am ajuns la stadiul in care pleaca grub-ul in mod EFI, dar imi da dupa aceea >> Loading Linux 2.6.32-5.amd64 >> Loading initial ramdisk >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown >> block(0,0) >> >> Optiunile de boot din grub sunt: >> insmod part_gpt >> insmod ext2 >> set root='(hd0,gpt3)' >> search --no-floppy --fs-uuid --set >> aea1cdf9-e444-43d8-9435-554b6df7779c <-----asta partitia 3 >> echo 'Loading Linux 2.6.32-5-amd64 ...' >> linux /boot/vmlinuz-2.6.32-5-amd64 >> root=UUID=aea1cdf9-e444-43d8-9435-554b6df7779c ro quiet >> echo 'Loading initial ramdisk ...' >> initrd /boot/initrd.img-2.6.32-5-amd64 >> >> Din cate imi dau seama, sunt corecte. Nu inteleg de ce nu vede fs-ul. >> Block device-ul este 8,0, iar la ls in grub imi arata (hd0) (hd0,gpt3) >> (hd0,gpt2) (hd0,gpt1) (cd0). > > La linia cu search banuiesc ca e root=aea1cdf9-e444-43d8-9435-554b6df7779c, > nu doar --set aea1cdf9-e444-43d8-9435-554b6df7779c.
Nu e cu root=aea... Am incercat sa modific in --set root=aea... , rezultatul este No such device root=aea... _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
