Jump to content
funtoo forums
  • 0

kernel can't find / (root)


Hi guys,

(first of all, I'm sorry for my bad english)

I'm new here, and I have some problem right now. I have installed funtoo on (acer cloudbook11 intel celeron n3050, 2gb ram) 5hours and after that it dosn't start, because kernel don't find Root.

1) I want to know if I have to use uuid (and how I can find it while installing and if I need to generate another kernel or if the default debian is ready to read uuid and not /dev/sda option).

I have formatted and installed antergos to see fstab that the software has generated and while I was doing that trough the liveusb, just to be sure I have mounted the drive to see fstab on funtoo installation and it was  just like lsblk output that you see in the screeshot (but without uuid): you see that my notebook have one sd/mmc , so when I wrote the fstab it was like.

/dev/mmcblk0p1  vfat  /boot

/dev/mmcblk0p3  ext4 /

2) the other doubt is, maybe I dont need to use uuid but just to generate tone kernel that can read from sd/mmc

(because one thing that I have noticed and I dont know if is important is that when I tried gentoo hybrid live, the sistem don't even see my hdd so when I wrote lsblk on terminal the output was just /dev/sda (that was the usb drive))

I know that the debian kernel is a different one. but like I said, I don't know.

here my screenshot



and here the antergos fstab automatically generated 3) if I do not change partition table, but just use mkfs.vfat and mkfs.ext4 the uuid will be the same??



4) The last option that I have is that something go wrong during installation and grub was sure that there wans't one installation, because I also noticed that antergos don't ask me if I want to install the system alongside the other.

so I ask you this before to try another installation, cause of the long time my notebook need to compile, I want be sure to log in after reboot, so if tell me that kernel  can read some like /dev/mmcblk0p3

thank you guys.

Share this post

Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

kali ~ # lsblk -f
NAME   FSTYPE   LABEL    UUID                                 MOUNTPOINT
├─sda1 reiserfs          d86b9236-a944-4321-aa9b-2834ca71df0e /slack
├─sda2 reiserfs          e7bf1f48-bf96-4f86-a49e-e6cf6a1457e4 /
└─sda3 reiserfs          5d0a5b00-a46c-48bd-9cf6-53e97d8782ef /home
├─sdb1 reiserfs          dcafa159-b9aa-40cc-8d9e-40ebee6efe02 /data
└─sdb3 swap              4b919b0f-7d88-437f-b094-b1af759e9383 [SWAP]
sdc    iso9660  SlackDVD 2016-06-30-18-21-58-24               
└─sdc1 reiserfs          b89f0fda-5eea-4d01-9a3f-f0046fd93fb2 /data1
kali ~ #


don't need a  separate /boot


kali ~ # cat /etc/fstab

/dev/sdb3        swap             swap        defaults         0   0
/dev/sda1        /slack           reiserfs    defaults         1   2
/dev/sda3        /home            reiserfs    defaults         1   2
/dev/sdb1        /data            reiserfs    defaults         1   2
/dev/sdc1        /data1           reiserfs    defaults         1   2
/dev/sda2        /                reiserfs    defaults         1   1
kali ~ #



Share this post

Link to post
Share on other sites
  • 0

UUID should work with the default debian-sources (kernel), what you might need to add to your boot cmd is "rootwait". Sometimes it takes a while to initialize the USB ports or SD cards if /(root) is on those cards USB stick.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...