New IT forum
11 August 2022, 06:11:50 pm *
Welcome, %1$s. Please login or register.

: GertDuino now in stock.
 
Pages: [1]

Author Topic: Can't Boot: VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)  (Read 15517 times)

cam34

  • Newbie
  • *
  • Posts: 2

Hello,

When I try boot my Mirabox with the uBoot environments here: https://newit.co.uk/forum/index.php/topic,4037.0.html

It gets stuck on the (mirabox version) of Debian 6 and Debian 7 kernels with:

UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            6144 mtdblock0 (driver?)
1f01         1042432 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


 --SNIP--
 
 VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            6144 mtdblock0  (driver?)
1f01         1042432 mtdblock1  (driver?)

 --SNIP--

Can some print their working uBoot variables from 'printenv'
Logged

bigbear59

  • Full Member
  • ***
  • Posts: 118

From http://newit.co.uk/forum/index.php/topic,4048.msg10817.html#msg10817
Quote
Hi,

Here is the default configuration for bootcmd and bootargs :

bootcmd=nand read 0x6400000 0x400000 0x400000; bootm 0x6400000                                                                                           
bootargs=console=ttyS0,115200 $mtdparts ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs   

You have full printenv default value in this post : http://newit.co.uk/forum/index.php/topic,4037.msg10769.html#msg10769

Hopes it can help you
Logged
Cheers,
BigBear59

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663

Let me start by saying "I don't do Mirabox..."

There have been issues mounting UBIFS root file systems at boot which have become corrupted.
IF this is your issue, the way to handle it is to boot off some other device to carry out the repair to the file system.
Sometimes this can be as simple as mounting the file system at which point it will be repaired automatically.
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

cam34

  • Newbie
  • *
  • Posts: 2

Hello again.

After loading the U-boot environment variables again (from this post: https://newit.co.uk/forum/index.php/topic,4037.msg10769.html#msg10769)

and trying to re-install the stock image (from this post: https://newit.co.uk/forum/index.php?topic=3880.0#9308105502985519281)

Trying to boot after the re-install / re-image still results in:

UBIFS error (pid 1): ubifs_get_sb: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            6144 mtdblock0 (driver?)
1f01         1042432 mtdblock1 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)


Does any one have any other advice?

On the line:
setenv bootargs "console=ttyS0,115200 $mtdparts ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs"

I have tried setting ubi.mtd=2 to ubi.mtd=0 and ubi.mtd=1 but no difference....
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663

Are you sure you are booting the correct kernel (with UBI\UBIFS support built in) ?
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!
Pages: [1]
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!