Table of Contents
If you notice that vfs cannot open root device or unknown-block2 0, this article will help you.
Quick and Easy PC Repair
I am working on an i.MX6DL sabreSD card. I am trying to get rootfs using NFS.
When I boot the kernel and try to mount the rootfs from the server, I get this error message.
VFS: Unable to open root cause of device “nfs” or unknown block (2.0): error -6
[463.891422] Add correct parameter “root =”; Here is a list of the running shoes for sale:
[463.899879] 0100 65536 ram0 463 (driver?)
[.904617] 0101 65536 ram1 463 (driver?)
[.909279] 0102 ram2 65536 (driver?) ))
[463.913976] 0103 Ram3 65536 (driver?)
[463.918633] 65536 0104 ram4 (driver?)
[463.923288] 65536 0105 ram5 (driver?)
[463.928207] 0106 65536 ( Driver?)
[463.923288] 65536 0105 ram5 (driver?)
[463.928207] 0106 65536 (driver?)?)
[ram6 463.933121] 65536 0107 ram7 (driver?)
[463.0108 937780 ] 65536 ram8 (driver?)
[463.942414] 0109 65536 ram9 (driver?)
[463.947094] 010a 65536 (driver?)
[ram10 463.951816] 010b 65536 (driver?)
[ram11 463.956554] 010c 65536 ram12 (driver?)
[463.961275] 010d 65536 ram13 463 (driver?)
[. 966011] 010e 65536 ram14 (driver?)
[463.970733] 010f 65536 (driver?)
[ram15 463.0800 975476] 8192 sda driver: sd
[463.980112] 7761920 b300 mmcblk2 driver: mmcblk
[463.985455] 15288320 driver b308 mmcblk3: mmcblk
[463.990784] b309 12288 f737a026-01
[mmcblk3p1 463.996126] b30a 152 71936 mmcblk3p2 f737a026-02cb [b3037p1 mmcbl7-02] mmcblk3p2 f737a026-0257 (b320r?)
[464.006773] b318 4096 (driver?)
[mmcblk3boot1 464.012103] b310 4096 (driver?)
[mmcblk3boot1 464.012103] b310 4096 (driver?)
[mmcbl0] 464.02] 464.017449] 464.017449] Kernel not synchronized: VFS: mounting root filesystem on unknown block (2.0) impossible
[464.025723] CPU1: Stop
[464.028441] CPU: 1 PID: 0 Comm: swapper / 1 not only painted 4.1.15-1.2 … 0 + gbecce8c # 107
[464.035837] Hardware name: Freescale i.MX6 Quad / DualLite (device tree)
[464.042395] [<800168c4>] (unwind_backtrace) [<80012728>] from (show_stack + 0x10 / 0x14)
[464.050150] [<80012728>] (show_stack) with [<8089c32c>] (dump_stack + 0x84 / 0xc4)
[464. [<8089c32c>] 057381] (dump_stack) versus [<800157cc>] (handle_IPI + 0x178 / 0x18c)
[464.064784] [<800157cc>] (handle_IPI) from [<80009480>] 464 (gic_handle_irq + 0x58 / 0x5 )
[.072361] [<80009480>] (gic_handle_irq) due to [<80013200>] 464 (__irq_svc + 0x40 / 0x74)
[.079845] exception stack (0xa8093f50 0xa8093f98)
[to 464.084902] 3f40: a8093f98 ff98.64ffff7 00000 06c
09.09] 3904.093083] 00000000 08aaa263 09dbca2e 0000006c 00000006c 0000001 00000000
[464.101264] 3f80: 00000017 a6asca] [8011630119159110000] [80059_15119159110000] ] [cpuidle_enter_4] [] received from [<80065104>] (cpu_startup_entry + 0x1fc / 0x320)
[4 64. [<1247065103]> (cpuidle_start) 1000952c>] (0x1000952c)
[464.131672] — [End kernel panic – no sync: VFS: Root file server for unknown block (2, 0) could not be mounted
Run I.MX6q SABER on TFTP network using NFS
PossiblyI tried Ubuntu rootfs and QT rootfs getting the same result.
Of course, below I usually add to / etc / exports on the server side.
| 08/01/2014, PM | A# 1 |
|
LQ 04:16 newbie Registered: February 2010 Posts: 10 Representative: |
Unable to extend root device “nfs” or unknown block (2.0): error -6 I cannot mount the root filesystem on NFS. keeps getting -6 errors, I’m not even sure what this error system means.
here is the dump: IP-Config: Complete Complete: device = eth4, hwaddr = 00: 22: bd: fe: 71: b0, ipaddr = 192.168.0.20, mask = 255.255.255.0, gw = 192.168.0.2 host = eth4, domain =, nis -domain = (none) bootserver = 192.168.0.2, rootserver = 192.168.0.2, rootpath = VFS: root cannot be mounted via fs NFS, this floppy. VFS: Cannot open root device ‘nfs’ or possibly unknown block (2.0): Error -6 Please add the boot parameter “root =” to the right; here are my available partitions: Kernel Panic – and without synchronization: vfs is impossible: mount Reason for fs on unavailableknown block (2,0) Pid: 1, Go: swapper / 0 Not corrupted 3.8.3+ # 56 when I formulate a kernel with an embedded rootfs that I can mount on this nfs server .. Quick and Easy PC RepairIs your computer running a little slower than it used to? Maybe you've been getting more and more pop-ups, or your Internet connection seems a bit spotty. Don't worry, there's a solution! ASR Pro is the revolutionary new software that helps you fix all of those pesky Windows problems with just the click of a button. With ASR Pro, your computer will be running like new in no time!  SELinux is disabled on the client. I also included in the corresponding client kernel config file: MLM Support-> Network Settings-> IP: Kernel-Smooth-Autoconfiguration-> Enable All In This Option Then File System-> Network System-> File Plan Root on NFS. I also disabled CONFIG_BLK_DEV_INITRD (tried it incredibly well, but it didn’t really matter). NFS server side tcpdump suggests queries, but I don’t know how to interpret those packages. 11: 17: 25.626806 IP router09.me.com.1011 normz.me.com.mountd: UDP, length 40 |
| A |
I can’t get root fs on itNFS. Keep asking about error -6, I don’t know what this error code means.
IP-Config: Complete: device = eth4, hwaddr = 00: 22: bd: fe: 71: b0, ipaddr = 192.168.0.20, mask = 255.255.255.0, gw = 192.168.0.2 host = eth4, domain =, nis- domain = (no) boot server = 192.168.0.2, root server = 192.168.0.2, root path =
Please add the correct boot option “root =”; on the right – available partitions: Severe fear of the kernel – no synchronization: VFS: The root filesystem ultimately cannot be mounted on an unknown block (2.0)
If I build a kernel with built-in rootfs, I can now mount it to help you with the nfs server ..
In the client kernel configuration history, I actually activated: Network Support-> Network Settings-> IP Core: Auto Config Level-> Enable All With One Option Then File System-> Initiate Network System-> Root Filesystem with NFS Enabled. I grew up with CONFIG_BLK_DEV_INITRD too (tried it too but found no difference.)
tcpdump on the server wall displays nfs requests, but you should never interpret those packages.
11: 17: 25.626806 IP router09.me.com.1011 normz.me.com.mountd: UDP, length 40
11: 17: 25.626875 IP normz.me.com.mountd router09.me.com.1011: UDP, length 24
11: 17: 25.627057 IP router09.me.com.1011 normz.me.com.mountd: UDP, length 88
11: 17: 25.627596 IP normz.me.com.mountd router09.me.com.1011: UDP, length 60
11: 17: 25.628054 IP router09.me.com.59949 normz.me.com.sunrpc: UDP, length 80
11: 17: 25.628946 IP normz.me.com.sunrpc router09.me.com.59949: UDP, length 28
11: 17: 25.629304 IP router09.me.com.298303220 normz.com.nfs: 40 null
11: 17: 25.629346 IP normz.me.com.nfs Router09.298303220: reply ok 32 n
* / Thank yourself in advance.
Enjoy a faster
Vfs Non Puo Aprire Il Dispositivo Root O Unknown Block2 0
Vfs Ne Peut Pas Ouvrir Le Peripherique Racine Ou Unknown Block2 0
Vfs Ne Mozhet Otkryt Kornevoe Ustrojstvo Ili Unknown Block2 0
Vfs는 루트 장치 또는 Unknown Block2 0을 열 수 없습니다
Vfs Nao Pode Abrir O Dispositivo Root Ou Unknown Block2 0
Vfs Kan Root Apparaat Of Unknown Block2 Niet Openen 0
Vfs Nie Moze Otworzyc Urzadzenia Root Lub Nieznanego Bloku2 0
Vfs Kann Root Gerat Oder Unknown Block2 Nicht Offnen 0
Vfs Kan Inte Oppna Rotenhet Eller Unknown Block2 0
Vfs No Puede Abrir El Dispositivo Raiz O Unknown Block2 0
