精华内容
下载资源
问答
  • Kernel panic - not syncing VFS Unable to mount root fs on
                   

    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

    内核版本

     2.6.14

    处理器平台

     S3C2440

    问题

     Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

    解决方案

    下载和内核一样老的yaffs2源码包,可能是nand的OOB不同。

    下面是使用旧的(也就是和内核一样老yaffs2源码包的启动信息:

    Starting kernel ...

    Uncompressing Linux.............................................................................. done, booting the kernel.
    Linux version 2.6.14 (root@czu) (gcc version 3.4.1) #8 Sat Dec 22 13:23:39 CST 2012
    CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
    Machine: SMDK2440
    Memory policy: ECC disabled, Data cache writeback
    CPU S3C2440A (id 0x32440001)
    S3C2440: core 405.600 MHz, memory 101.400 MHz, peripheral 50.700 MHz
    S3C2410 Clocks, (c) 2004 Simtec Electronics
    CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
    CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
    Built 1 zonelists
    Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
    irq: clearing pending ext status 00000200
    irq: clearing subpending status 00000002
    PID hash table entries: 512 (order: 9, 8192 bytes)
    timer tcon=00500000, tcnt a509, tcfg 00000200,00000000, usec 00001e4c
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 64MB = 64MB total
    Memory: 62336KB available (1989K code, 439K data, 104K init)
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    softlockup thread 0 started up.
    NET: Registered protocol family 16
    S3C2410 Power Management, (c) 2004 Simtec Electronics
    S3C2440: Initialising architecture
    S3C2440: IRQ Support
    S3C2440: Clock Support, UPLL 48.000 MHz, DVS off
    S3C2410 DMA Driver, (c) 2003-2004 Simtec Electronics
    DMA channel 0 at c4800000, irq 33
    DMA channel 1 at c4800040, irq 34
    DMA channel 2 at c4800080, irq 35
    DMA channel 3 at c48000c0, irq 36
    NetWinder Floating Point Emulator V0.97 (double precision)
    devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
    devfs: devfs_debug: 0x0
    devfs: boot_options: 0x1
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    yaffs Dec 22 2012 13:19:49 Installing. 
    lp: driver loaded but no devices found
    S3C2410 RTC, (c) 2004 Simtec Electronics
    ppdev: user-space parallel port driver
    S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
    Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
    s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
    devfs_mk_dev: could not append to parent for tts/0
    s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
    devfs_mk_dev: could not append to parent for tts/1
    s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
    devfs_mk_dev: could not append to parent for tts/2
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
    loop: loaded (max 8 devices)
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
    BAST NOR-Flash Driver, (c) 2004 Simtec Electronics
    S3C24XX NAND Driver, (c) 2004 Simtec Electronics
    s3c2410-nand: mapped registers at c4a00000
    s3c2410-nand: timing: Tacls 20ns, Twrph0 60ns, Twrph1 20ns
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
    NAND_ECC_NONE selected by board driver. This is not recommended !!
    Scanning device for bad blocks
    Bad eraseblock 1945 at 0x0f320000
    Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit":
    0x00000000-0x00080000 : "Board_uboot"
    0x00240000-0x00440000 : "Board_kernel"
    0x00440000-0x0ff80000 : "Board_yaffs2"
    mice: PS/2 mouse device common for all mice
    s3c2440-i2c s3c2440-i2c: slave address 0x10
    s3c2440-i2c s3c2440-i2c: bus frequency set to 99 KHz
    s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    TCP reno registered
    TCP bic registered
    NET: Registered protocol family 1
    Reading data from NAND FLASH without ECC is not recommended
    yaffs: dev is 32505858 name is "mtdblock2"
    yaffs: passed flags ""
    yaffs: Attempting MTD mount on 31.2, "mtdblock2"
    yaffs: auto selecting yaffs2
    block 1912 is bad
    yaffs: dev is 32505858 name is "mtdblock2"
    yaffs: passed flags ""
    yaffs: Attempting MTD mount on 31.2, "mtdblock2"
    block 1912 is bad

    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)

    下面是使用旧的(也就是和内核一样老yaffs2源码包的启动信息:

    Starting kernel ...
    Uncompressing Linux............................................................................. done, booting the kernel.
    Linux version 2.6.14 (root@czu) (gcc version 3.4.1) #10 Sat Dec 22 15:33:15 CST 2012
    CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
    Machine: SMDK2440
    Memory policy: ECC disabled, Data cache writeback
    CPU S3C2440A (id 0x32440001)
    S3C2440: core 405.600 MHz, memory 101.400 MHz, peripheral 50.700 MHz
    S3C2410 Clocks, (c) 2004 Simtec Electronics
    CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
    CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
    Built 1 zonelists
    Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
    irq: clearing pending ext status 00000200
    irq: clearing subpending status 00000002
    PID hash table entries: 512 (order: 9, 8192 bytes)
    timer tcon=00500000, tcnt a509, tcfg 00000200,00000000, usec 00001e4c
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 64MB = 64MB total
    Memory: 62336KB available (1970K code, 443K data, 92K init)
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    softlockup thread 0 started up.
    NET: Registered protocol family 16
    S3C2410 Power Management, (c) 2004 Simtec Electronics
    S3C2440: Initialising architecture
    S3C2440: IRQ Support
    S3C2440: Clock Support, UPLL 48.000 MHz, DVS off
    S3C2410 DMA Driver, (c) 2003-2004 Simtec Electronics
    DMA channel 0 at c4800000, irq 33
    DMA channel 1 at c4800040, irq 34
    DMA channel 2 at c4800080, irq 35
    DMA channel 3 at c48000c0, irq 36
    NetWinder Floating Point Emulator V0.97 (double precision)
    devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
    devfs: devfs_debug: 0x0
    devfs: boot_options: 0x1
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    yaffs Dec 22 2012 15:29:35 Installing. 
    lp: driver loaded but no devices found
    S3C2410 RTC, (c) 2004 Simtec Electronics
    ppdev: user-space parallel port driver
    S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
    Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
    s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
    devfs_mk_dev: could not append to parent for tts/0
    s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
    devfs_mk_dev: could not append to parent for tts/1
    s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
    devfs_mk_dev: could not append to parent for tts/2
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered
    loop: loaded (max 8 devices)
    nbd: registered device at major 43
    Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
    ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
    BAST NOR-Flash Driver, (c) 2004 Simtec Electronics
    S3C24XX NAND Driver, (c) 2004 Simtec Electronics
    s3c2410-nand: mapped registers at c4a00000
    s3c2410-nand: timing: Tacls 20ns, Twrph0 60ns, Twrph1 20ns
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
    NAND_ECC_NONE selected by board driver. This is not recommended !!
    Scanning device for bad blocks
    Bad eraseblock 35 at 0x00460000
    Bad eraseblock 36 at 0x00480000
    Bad eraseblock 37 at 0x004a0000
    Bad eraseblock 38 at 0x004c0000
    Bad eraseblock 39 at 0x004e0000
    Bad eraseblock 40 at 0x00500000
    Bad eraseblock 41 at 0x00520000
    Bad eraseblock 42 at 0x00540000
    Bad eraseblock 43 at 0x00560000
    Bad eraseblock 44 at 0x00580000
    Bad eraseblock 45 at 0x005a0000
    Bad eraseblock 46 at 0x005c0000
    Bad eraseblock 47 at 0x005e0000
    Bad eraseblock 48 at 0x00600000
    Bad eraseblock 49 at 0x00620000
    Bad eraseblock 50 at 0x00640000
    Bad eraseblock 51 at 0x00660000
    Bad eraseblock 52 at 0x00680000
    Bad eraseblock 53 at 0x006a0000
    Bad eraseblock 54 at 0x006c0000
    Bad eraseblock 55 at 0x006e0000
    Bad eraseblock 56 at 0x00700000
    Bad eraseblock 57 at 0x00720000
    Bad eraseblock 58 at 0x00740000
    Bad eraseblock 59 at 0x00760000
    Bad eraseblock 60 at 0x00780000
    Bad eraseblock 61 at 0x007a0000
    Bad eraseblock 62 at 0x007c0000
    Bad eraseblock 63 at 0x007e0000
    Bad eraseblock 64 at 0x00800000
    Bad eraseblock 65 at 0x00820000
    Bad eraseblock 66 at 0x00840000
    Bad eraseblock 67 at 0x00860000
    Bad eraseblock 68 at 0x00880000
    Bad eraseblock 69 at 0x008a0000
    Bad eraseblock 70 at 0x008c0000
    Bad eraseblock 71 at 0x008e0000
    Bad eraseblock 72 at 0x00900000
    Bad eraseblock 73 at 0x00920000
    Bad eraseblock 74 at 0x00940000
    Bad eraseblock 75 at 0x00960000
    Bad eraseblock 76 at 0x00980000
    Bad eraseblock 77 at 0x009a0000
    Bad eraseblock 78 at 0x009c0000
    Bad eraseblock 79 at 0x009e0000
    Bad eraseblock 80 at 0x00a00000
    Bad eraseblock 81 at 0x00a20000
    Bad eraseblock 82 at 0x00a40000
    Bad eraseblock 83 at 0x00a60000
    Bad eraseblock 84 at 0x00a80000
    Bad eraseblock 85 at 0x00aa0000
    Bad eraseblock 86 at 0x00ac0000
    Bad eraseblock 87 at 0x00ae0000
    Bad eraseblock 88 at 0x00b00000
    Bad eraseblock 89 at 0x00b20000
    Bad eraseblock 90 at 0x00b40000
    Bad eraseblock 91 at 0x00b60000
    Bad eraseblock 92 at 0x00b80000
    Bad eraseblock 93 at 0x00ba0000
    Bad eraseblock 94 at 0x00bc0000
    Bad eraseblock 95 at 0x00be0000
    Bad eraseblock 96 at 0x00c00000
    Bad eraseblock 97 at 0x00c20000
    Bad eraseblock 98 at 0x00c40000
    Bad eraseblock 99 at 0x00c60000
    Bad eraseblock 100 at 0x00c80000
    Bad eraseblock 101 at 0x00ca0000
    Bad eraseblock 102 at 0x00cc0000
    Bad eraseblock 103 at 0x00ce0000
    Bad eraseblock 104 at 0x00d00000
    Bad eraseblock 105 at 0x00d20000
    Bad eraseblock 106 at 0x00d40000
    Bad eraseblock 107 at 0x00d60000
    Bad eraseblock 108 at 0x00d80000
    Bad eraseblock 109 at 0x00da0000
    Bad eraseblock 110 at 0x00dc0000
    Bad eraseblock 111 at 0x00de0000
    Bad eraseblock 112 at 0x00e00000
    Bad eraseblock 113 at 0x00e20000
    Bad eraseblock 114 at 0x00e40000
    Bad eraseblock 115 at 0x00e60000
    Bad eraseblock 116 at 0x00e80000
    Bad eraseblock 117 at 0x00ea0000
    Bad eraseblock 118 at 0x00ec0000
    Bad eraseblock 119 at 0x00ee0000
    Bad eraseblock 120 at 0x00f00000
    Bad eraseblock 1945 at 0x0f320000
    Creating 3 MTD partitions on "NAND 256MiB 3,3V 8-bit":
    0x00000000-0x00080000 : "Board_uboot"
    0x00240000-0x00440000 : "Board_kernel"
    0x00440000-0x0ff80000 : "Board_yaffs2"
    mice: PS/2 mouse device common for all mice
    s3c2440-i2c s3c2440-i2c: slave address 0x10
    s3c2440-i2c s3c2440-i2c: bus frequency set to 99 KHz
    s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    TCP reno registered
    TCP bic registered
    NET: Registered protocol family 1
    Reading data from NAND FLASH without ECC is not recommended
    yaffs: dev is 32505858 name is "mtdblock2"
    yaffs: Attempting MTD mount on 31.2, "mtdblock2"
    yaffs: MTD device does not support have the right page sizes
    yaffs: dev is 32505858 name is "mtdblock2"
    yaffs: Attempting MTD mount on 31.2, "mtdblock2"
    yaffs: yaffs_GutsInitialise()
    block 2 is bad
    block 3 is bad
    block 4 is bad
    block 5 is bad
    block 6 is bad
    block 7 is bad
    block 8 is bad
    block 9 is bad
    block 10 is bad
    block 11 is bad
    block 12 is bad
    block 13 is bad
    block 14 is bad
    block 15 is bad
    block 16 is bad
    block 17 is bad
    block 18 is bad
    block 19 is bad
    block 20 is bad
    block 21 is bad
    block 22 is bad
    block 23 is bad
    block 24 is bad
    block 25 is bad
    block 26 is bad
    block 27 is bad
    block 28 is bad
    block 29 is bad
    block 30 is bad
    block 31 is bad
    block 32 is bad
    block 33 is bad
    block 34 is bad
    block 35 is bad
    block 36 is bad
    block 37 is bad
    block 38 is bad
    block 39 is bad
    block 40 is bad
    block 41 is bad
    block 42 is bad
    block 43 is bad
    block 44 is bad
    block 45 is bad
    block 46 is bad
    block 47 is bad
    block 48 is bad
    block 49 is bad
    block 50 is bad
    block 51 is bad
    block 52 is bad
    block 53 is bad
    block 54 is bad
    block 55 is bad
    block 56 is bad
    block 57 is bad
    block 58 is bad
    block 59 is bad
    block 60 is bad
    block 61 is bad
    block 62 is bad
    block 63 is bad
    block 64 is bad
    block 65 is bad
    block 66 is bad
    block 67 is bad
    block 68 is bad
    block 69 is bad
    block 70 is bad
    block 71 is bad
    block 72 is bad
    block 73 is bad
    block 74 is bad
    block 75 is bad
    block 76 is bad
    block 77 is bad
    block 78 is bad
    block 79 is bad
    block 80 is bad
    block 81 is bad
    block 82 is bad
    block 83 is bad
    block 84 is bad
    block 85 is bad
    block 86 is bad
    block 87 is bad
    block 1912 is bad
    yaffs: yaffs_GutsInitialise() done.
    VFS: Mounted root (yaffs2 filesystem).
    mount_devfs_fs(): unable to mount devfs, err: -2
    Freeing init memory: 92K
    Warning: unable to open an initial console.
    Failed to execute /linuxrc.  Attempting defaults...
    Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

    继续加油!

               

    再分享一下我老师大神的人工智能教程吧。零基础!通俗易懂!风趣幽默!还带黄段子!希望你也加入到我们人工智能的队伍中来!https://blog.csdn.net/jiangjunshow

    展开全文
  • mount program didn't pass callback address [ 20.085962] NFS4: mount program didn't pass callback address <3>VFS: Unable to mount root fs via NFS, trying floppy. 注意,这里vers=4 不行,就改为2或者3试试...

    题目是一个非常常见的网络文件系统制作报错,下面列一下制作网络文件系统的一些关键环节。

    1. 配置环境
    1.1 软件环境
    主机:Linux redhat7 64位
    文件系统:busybox-1.31.1,使用动态编译制作完成,放在目录rootfs
    1.2 硬件环境
    任意arm开发板

    2. 主机软件
    2.1 portmap:Linux的RPC服务,它响应RPC服务的请求和与请求的RPC服务建立连接。(注意,在centos7以上或redhat7以上,portmap改名为rpcbind了)
        检查主机是否安装了rpcbind
        rpm -qa | grep rpcbind
        显示为:
        rpcbind-0.2.0-47.el7.x86_64
    2.2 nfs: 启动相应RPC服务进程来服务对于NFS文件系统的请求。
        检查主机是否安装了nfs
        rpm -qa | grep nfs-utils
        显示为:
        nfs-utils-1.3.0-0.61.el7.x86_64

    2.3 nfslock:一个可选的服务,用于启动相应的RPC进程,允许NFS客户端在服务器上对文件加锁。

    如果主机没有安装rpcbind和nfs程序,下载相应的版本安装,安装过程略。

    3. 启动rpcbind和nfs一般要注意顺序,应该是rpcbind先启动,nfs后启动
    3.1 启动服务:
        systemctl start rpcbind
        systemctl start nfs
    3.2 设置开机自动启动:
        systemctl enable rpcbind.service
        systemctl enable nfs.service
    3.3 查看版本,这是很多文件系统启动失败的原因之一
        查看版本:
        rpcinfo |grep portmap
        显示如下:
        100000    4    tcp6      ::.0.111               portmapper superuser
        100000    3    tcp6      ::.0.111               portmapper superuser
        100000    4    udp6      ::.0.111               portmapper superuser
        100000    3    udp6      ::.0.111               portmapper superuser
        100000    4    tcp       0.0.0.0.0.111          portmapper superuser
        100000    3    tcp       0.0.0.0.0.111          portmapper superuser
        100000    2    tcp       0.0.0.0.0.111          portmapper superuser
        100000    4    udp       0.0.0.0.0.111          portmapper superuser
        100000    3    udp       0.0.0.0.0.111          portmapper superuser
        100000    2    udp       0.0.0.0.0.111          portmapper superuser
        100000    4    local     /var/run/rpcbind.sock  portmapper superuser
        100000    3    local     /var/run/rpcbind.sock  portmapper superuser
        注意第2列显示版本号,也就是主机支持2,3,4版本,如果后面挂不上,排除了其
    它原因后,应该考虑这里的版本号对应。

    4. 配置共享文件夹
    vi /etc/exports
    输入以下内容:
    /home/software/rootfs 192.168.1.*(rw,sync)  *(rw,sync,no_root_squash)
    rootfs为我的根文件系统,已配置完善,192.168.1.*示允许192.168.1的任何机器访问。
    其它配置项很多地方介绍很详细,不再赘述。

    5. 配置防火墙
    如果开了防火墙,是挂不上的,将3.3节查看的111端口号加入防火墙,或者关掉防火墙
    systemctl stop firewalld
    在本机试挂一下:
    mount -t nfs 192.168.1.9:/home/software/rootfs  /mnt
    查看挂载情况:
    showmount -e localhost

    6. 编译内核时的配置
    6.1 如果配置了路由器的dhcp, 内核中设置为自动获取ip,这种方式是比较顺利的一种。
    Networking support  --->  
        Networking options  --->     
            TCP/IP networking 
                [*]     IP: DHCP support                                                                                                                 
                [*]     IP: BOOTP support                                                                                                                
                [*]     IP: RARP support 
        3项都选*
    6.2 网络文件选项
        File systems  ---> 
            [*] Network File Systems  ---> 
                <*>   NFS client support(如果编译内核文件大小没有超的话这下面的项都选上吧)
                [*]   Root file system on NFS 
                [*]   RPC: Enable dprintk debugging (这一项调试很重要呀,如果出错后面可以输出相关信息)

    6.3 启动参数配置
    root=/dev/nfs rw init=/linuxrc nfsroot=192.168.1.9:/home/software/rootfs,proto=tcp,vers=3 rootfstype=nfs console=ttySAC2,115200 init=/linuxrc ip=dhcp rootdelay=5 nfsrootdebug 
    ip=dhcp 表示让路由器分配ip地址
    192.168.1.9表示我的主机
    proto=tcp表示nfs使用tcp传输
    vers=3表示板子端的rpc客户端使用的是rpc版本3,如果排除了网卡驱动不正常,主机rpc不正常,防火墙问题之外,挂不上的问题一般出在这儿。
    rootdelay=5表示延时5秒,在有些情况下,不延时好像挂不上,至于延时几秒,可以修改试试。
    nfsrootdebug这项表示配合内核的rpc调试,如果挂不上可以看调试结果,开启此项后, 可以看到类似以下输出信息:
    [    8.088632] Waiting 5 sec before mounting root device...
    [   13.121983] Root-NFS: nfsroot=/home/software/rootfs,proto=tcp,vers=3
    [   13.128728] NFS:   parsing nfs mount option 'source'
    [   13.133775] NFS:   parsing nfs mount option 'vers'
    [   13.138163] NFS:   parsing nfs mount option 'tcp'
    [   13.143709] NFS:   parsing nfs mount option 'rsize'
    [   13.148149] NFS:   parsing nfs mount option 'wsize'
    [   13.153383] NFS:   parsing nfs mount option 'proto'
    [   13.157864] NFS:   parsing nfs mount option 'vers'
    [   13.162887] NFS:   parsing nfs mount option 'nolock'
    [   13.167547] NFS:   parsing nfs mount option 'addr'
    [   13.172490] NFS: MNTPATH: '/home/software/rootfs'
    [   13.178035] NFS: sending MNT request for 192.168.1.9:/home/software/rootfs
    [   13.266511] NFS: received 1 auth flavors
    [   13.268997] NFS:   auth flavor[0]: 1
    [   13.274015] NFS: MNT request succeeded
    [   13.276311] NFS: attempting to use auth flavor 1
    [   13.299952] VFS: Mounted root (nfs filesystem) on device 0:14.
    看到这样的信息,清清楚楚,心情自然畅。
    7. 启动可能出现的错误
    [    4.977061] Waiting 15sec before mounting root device...
    Root-NFS: nfsroot=/home/software/rootfs,tcp,vers=4
    [   19.986568] Root-NFS: nfsroot=/home/software/rootfs,tcp,vers=4
    NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,tcp,vers=4,nolock,addr=192.168.1.9'
    [   20.001732] NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,tcp,vers=4,nolock,addr=192.168.1.9'
    NFS:   parsing nfs mount option 'vers=2'
    [   20.014557] NFS:   parsing nfs mount option 'vers=2'
    NFS:   parsing nfs mount option 'udp'
    [   20.022876] NFS:   parsing nfs mount option 'udp'
    NFS:   parsing nfs mount option 'rsize=4096'
    [   20.031542] NFS:   parsing nfs mount option 'rsize=4096'
    NFS:   parsing nfs mount option 'wsize=4096'
    [   20.040814] NFS:   parsing nfs mount option 'wsize=4096'
    NFS:   parsing nfs mount option 'tcp'
    [   20.049480] NFS:   parsing nfs mount option 'tcp'
    NFS:   parsing nfs mount option 'vers=4'
    [   20.057799] NFS:   parsing nfs mount option 'vers=4'
    NFS:   parsing nfs mount option 'nolock'
    [   20.066378] NFS:   parsing nfs mount option 'nolock'
    NFS:   parsing nfs mount option 'addr=192.168.1.9'
    [   20.075823] NFS:   parsing nfs mount option 'addr=192.168.1.9'
    NFS4: mount program didn't pass callback address
    [   20.085962] NFS4: mount program didn't pass callback address
    <3>VFS: Unable to mount root fs via NFS, trying floppy.

    注意,这里vers=4 不行,就改为2或者3试试,板子上的系统不支持某一版本,修改几下试试。

       

    展开全文
  •  kernel panic VFS: Unable to mount root fs  参考链接:http://www.52os.net/articles/linux-from-scrath-7-7-part-four.html  发现,编译内核时,有些选项没有打开所致 编译内核: ...

    说明:

      使用Vm虚拟机构建自己的LFS系统时,系统引导不成功,提示

        kernel panic VFS: Unable to mount root fs 

      参考链接:http://www.52os.net/articles/linux-from-scrath-7-7-part-four.html 

      发现,编译内核时,有些选项没有打开所致

      

    编译内核:

      make mrproper

      make LANG=en_US.UTF-8 LC_ALL= menuconfig

    生成的.config文件中,确保以下内容是打开的: 

    CONFIG_FHANDLE=y
    
    CONFIG_CGROUPS=y
    
    CONFIG_SECCOMP=y
    
    CONFIG_IPV6=y
    
    CONFIG_DEVTMPFS=y
    
    CONFIG_DMIID=y
    
    ONFIG_INOTIFY_USER=y
    
    CONFIG_AUTOFS4_FS=y
    
    CONFIG_TMPFS_POSIX_ACL=y
    
    CONFIG_TMPFS_XATTR=y

     

     如果宿主机是vmware,还需要如下配置:

     

    CONFIG_FUSION=y
    
    CONFIG_FUSION_SPI=y
    
    CONFIG_FUSION_SAS=y
    
    CONFIG_FUSION_MAX_SGE=y
    
    CONFIG_FUSION_CTL=y
    
    CONFIG_FUSION_LOGGING=y
    
     
    
    CONFIG_VMWARE_BALLOON=y
    
    CONFIG_VMWARE_PVSCSI=y
    
     
    
    CONFIG_HYPERVISOR_GUEST=Y

     

    编译安装完成后,重新引导,OK

     

    转载于:https://www.cnblogs.com/zhangjy6/p/5584210.html

    展开全文
  • 解决 VFS:Unable to mount root fs on Unknown-block(0,0)1. 启动报错2. 引导修护3. 使用其他内核启动 1. 启动报错 出现原因是安装软件时断电造成内核升级失败 报错内容:VFS:Unable to mount root fs on Unknown...

    解决 VFS:Unable to mount root fs on Unknown-block(0,0)

    1. 启动报错

    • 出现原因是安装软件时断电造成内核升级失败
    • 报错内容:VFS:Unable to mount root fs on Unknown-block(0,0)

    2. 引导修护

    • 进入GNU GRUB 界面,选择默认启动版本的内核recovery mode(恢复模式)
    • 可以进入后可按照以下步骤处理,否则使用下一章节进行处理
      • 清理Ubuntu的引导分区
      • 当处于救援模式时,选择选项clean,然后是dpkg、grub和fsck。
      • 确保引导分区上的空间是空闲的,可以修复损坏的包,检查所有文件系统,确保它们是正确的,并更新grub引导加载程序。
      • 可使用命令行方式进行处理
        • 清理启动分区: $ sudo apt-get autoremove --purge
        • 更新GRUB内核列表: $ sudo update-grub
      • 使用df检查分区大小: $ df -h

    3. 使用其它内核启动

    • 当默认内核无法进入恢复模式时,可通过其它内核进行启动,启动后修护、删除或更新默认内核
    • 拆卸失败内核:
      • sudo apt-get remove linux-image- (tab可列出可以使用的内核版本)
      • 根据列表中的内核版本,选择需要拆卸的内核
    • 安装新内核:
      • sudo apt-get install linux-image-(tab可列出可以使用的内核版本)
      • 安装linux内核版本:
        sudo apt-get install linux-image-4.15.0-139-generic
        sudo apt-get install linux-image-extra-4.15.0-139-generic   
        sudo apt-get install linux-headers-4.15.0-139-generic    
        
    • 修改内核启动顺序:
      • 默认启动为最新内核,使用旧版本需修改启动顺序
        sudo chmod +w /etc/default/grub
        sudo gedit /etc/default/grub
        GRUB_DEFAULT=0 修改为所启动顺序
        GRUB_DEFAULT=0 ->设置默认启动项。比如要默认从第四个菜单项启动,数字改为3,若改为 saved,则默认为上次启动项。
        或使用固定版本:GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 4.15.0-129-generic"  
        sudo update-grub
        reboot
        
    展开全文
  • 之前用OK6410烧写cramfs文件系统的时候老是出现Unable to mount root fs on unknown-block(31,2)? 我也按照手册里面的一点一点的改了启动参数,还是出现Unable to mount root fs on unknown-block(31,2)?或者出现...
  • 升级了一下centos6.5 执行了 yum -y update reboot 出现了以下问题: Kernal Panic - Not syncing : VFS: unable to mount root fs on ...Kernal Panic - Not syncing : VFS: unable to mount root fs on unkn...
  • 在VM15中安装centos8出现Unable to Mount root fs on… 在VM15中安装centos8出现报错可能是因为版本不符合,可以重新下载其他镜像下面的版本或者是下载相同镜像下的低版本(centos7…)都可以解决,也可能是因为在...
  • CentOS启动报错:Centos kernel panic-not syncing:VFS:Unable to mount root fs on unknown block 原因:主要问题就是你更新了CentOS内核之后出现的问题。 故障原因: 打算安装GNOME Desktop,已经执行了yum ...
  • 在通过nfs启动文件系统过程中会遇到...[ 100.338146] VFS: Unable to mount root fs via NFS, trying floppy. [ 100.345728] VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6 [ 100.353202] Pl...
  • 昨天启动还好好的,然后安装了VM tools,因为内核头文件路径也没装成功,但是确给fedora 14执行  yum -y install kernel-devel ... unable to mount root fs on unknown-block 求解救,这边不能插入本地图片吗
  • 这个问题貌似很多人都遇到过,因为在网上搜了一下,结果还不少,由一个引用比较多的网页是:https://unix.stackexchange.com/questions/414655/not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block0-0 ...
  • mini2440 nfs 挂载文件系统 unable to mount root fs on unknown-block(2,0)
  • Guest fails to mount root FS

    2020-12-09 13:43:11
    [ 0.341045] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) </code></pre> <p>Using <code>--show-command</code> yields: <p><code>/usr/local/bin/qemu-system-x86_64 -fsdev...
  • 在此期间我尝试了很多种方法都没有得到解决,并且我在nfs服务器端查看Log发现有nfs mount迹象,这就很奇怪了,我通过抓包软件抓nfs的交互字段发现: Accept State: remote can't support version ...
  • 然后,从DELL的BIOS中,用UEFI从内存卡中启动,可以发现有几个选项,,try Ubuntu和install等,你随便进入一个,就会报unable to mount root fs on unknown-block(2,0)。这个时候应该不要按Enter键,按一下Esc键,...
  • 服务器dell sc440操作系统:redhat linux 5.2[@more@]运行的数据库停机,用fdisk查看:[root@tonykorn97 ~]# fdisk -lWarning: ignoring extra d...
  • <p>Apparently client is not able to read the root fs with this <code>cmdline.txt</code>: <pre><code>dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 rootfstype=nfs root=/...
  • Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0) 原因: 出现这种错误的原因多半是/boot盘空间不够,Ubuntu内核做了许多的更新,而默认情况下,Ubuntu将保留旧的内核并将它们...
  • CentOS开机提示 Centos kernel panic-not syncing:VFS:Unable to mount root fs on unknown-block 错误。 原因:主要问题就是你更新了CentOS内核之后出现的问题。 解决方案:开机启动时按Esc,然后选择下面的旧...
  • Centos kernel panic-not syncing:VFS:Unable to mount root fs on unknown block 原因:主要问题就是你更新了内核之后出现的问题。 解决方案:开机启动时按Esc,然后选择下面的旧版本的内核启动即可。(成功进入...
  • 树莓派启动报错:PANIC: VFS Unable to mount root fs on unknown-block(179,2) 解决方案:取出SD卡,在ubuntu linux系统(类似也可)打开: 执行: sudo fsck -f -v -r /dev/sdb2 (可能不是sdb2,需要查看你的sd...
  • 直接重启的时候导致系统配置文件丢失导致,没办法直接重启进入trobleshooting mode ,没想到troubleshooting mode 都不能正常启动,估计是废了,又重启选择debug mode,竟然起来了,最后使用root帐号执行以下命令: ...
  • https://thomasmodeneis.wordpress.com/2017/05/12/how-to-restore-ubuntu-16-04-kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block00/ How to restore Ubuntu 16.04 “Kernel panic – not ...
  • 我是因为配置完共享文件nfs后没有重启Ubuntu。
  • 内核找不到根文件系统,不是/etc/fstab配置的问题,根本原因在于你的内核配置参数的,问题,有些选项必须编译进内核... Make sure your kernel has a "root=" parameter passed to it in your bootloader and that the
  • 前两天ubuntu一直报boot卷满了,也没管他,然后忽然就进不去了,报错:kernel panic not syncing vfs unable to mount root fs on unknown-block 0 0 – error 去网上查了一下还真是boot卷饱满的问题,主要是因为boot卷太...
  • Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) 内核版本 2.6.14 处理器平台 S3C2440 问题 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 469
精华内容 187
关键字:

fsmountroottounable