-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 29 Dec 2012 14:20:29 -0600
Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> > Panic showed all my drives and partitions which means
> > they were detected correctly.
>
> Was it a panic, or was it simply a very verbose message which contained a backtrace?
>
> Can you please include what you actually saw in your logs?
Yes, it was a panic. Box did not boot (i would not bisect it otherwise).
I won't have access to real box thus I've reproduced it in minimal
UML:
Current usermode linux perfectly reproduces the problem as well:
$ cat ./run_ubda_fails
#!/bin/sh
./vmlinux \
ubd0=$(pwd)/1G.img \
root=/dev/ubda \
rw \
mem=256M \
umid=foo \
\
"$@"
reset
$ cat ./run_ubda
#!/bin/sh
./vmlinux \
ubd0=$(pwd)/1G.img \
root=/dev/ubda \
rw rootfstype=btrfs \
mem=256M \
umid=foo \
\
"$@"
reset
Note the rootfstype in the workign case. I've included only EXT4=y XFS=y and BTRFS=y
as supported FSen. The UML OOps:
[ 0.170000] VFS: Cannot open root device "ubda" or unknown-block(98,0): error -117
[ 0.170000] Please append a correct "root=" boot option; here are the available partitions:
[ 0.170000] 6200 1048576 ubda driver: uml-blkdev
[ 0.170000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98,0)
[ 0.170000] Call Trace:
[ 0.170000] 7003fd68: [<6037c4d8>] panic+0x164/0x2c6
[ 0.170000] 7003fda0: [<6037c374>] panic+0x0/0x2c6
[ 0.170000] 7003fdd8: [<60385a20>] _raw_spin_lock+0x0/0x20
[ 0.170000] 7003fe48: [<6037c63a>] printk+0x0/0xa0
[ 0.170000] 7003fe60: [<600d9780>] sys_mount+0x0/0x120
[ 0.170000] 7003fe78: [<60001fa5>] mount_block_root+0x33a/0x359
[ 0.170000] 7003fee8: [<602afdd0>] strcpy+0x0/0x30
[ 0.170000] 7003ff08: [<60002045>] mount_root+0x81/0x85
[ 0.170000] 7003ff18: [<602b0040>] strncmp+0x0/0x60
[ 0.170000] 7003ff28: [<6000222c>] prepare_namespace+0x1e3/0x22b
[ 0.170000] 7003ff38: [<600d5350>] sys_dup+0x0/0x80
[ 0.170000] 7003ff48: [<602afdd0>] strcpy+0x0/0x30
[ 0.170000] 7003ff58: [<6037b0f5>] kernel_init+0x205/0x3d0
[ 0.170000] 7003ff60: [<600011ae>] repair_env_string+0x0/0xbd
[ 0.170000] 7003ffd8: [<6001cc91>] new_thread_handler+0x81/0xb0
'Cannot open root device' is completely bogus. It can be opened if I set proper
FS type.
Thanks!
- --
Sergei
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlDfc+AACgkQcaHudmEf86qt9QCfWpWvLvgdyIP6IwvWTK+Mk74/
JToAni+pSTKgd7SPFGdYBfzPYa26HnY7
=hLVB
-----END PGP SIGNATURE-----
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
