Re: [Xen-users] Re: booting FreeBSD DomU

[Luke Crawford <lsc@xxxxxxxxx>]

Okay, to fix that one you need to fix the fstab so the device names are 
correct.
Are you using Macy's root filesystem?  that is perhaps the easiest way to 
do it.  use his file for /, then use your new vbd as a second disk;  then 
you can login and verify that things like the fstab are correct before 
you boot directly into your vbd.
On Mon, 16 Oct 2006, Andrey Khavryuchenko wrote:
> "AVK" == Andrey Khavryuchenko wrote:
>
> AVK> I've tried several vfs.root.mountfrom specifications per googled advises,
> AVK> including /dev/md0, /dev/xbd0a and /dev/xb769a, but with no success.
>
> Sorry, found a typo in config file
>
> Now it boots and finds the root partition:
>
> [XEN]
> Trying to mount root from ufs:/dev/xbd769s1a
> Loading configuration files.
> Entropy harvesting: interrupts ethernet point_to_point kickstart.
> swapon: /dev/ad0s1b: No such file or directory
> Starting file system checks:
> /dev/xbd769s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS
> /dev/xbd769s1a: clean, 128085 free (1765 frags, 15790 blocks, 1.2% 
> fragmentation)
> Can't stat /dev/ad0s1e: No such file or directory
> Can't stat /dev/ad0s1f: No such file or directory
> Can't stat /dev/ad0s1d: No such file or directory
> Can't stat /dev/ad1s1c: No such file or directory
> Can't stat /dev/ad0s1e: No such file or directory
> Can't stat /dev/ad1s1c: No such file or directory
> Can't stat /dev/ad0s1e: No such file or directory
> /dev/ad0s1e: CAN'T CHECK FILE SYSTEM.
> /dev/ad0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> Can't stat /dev/ad1s1c: No such file or directory
> /dev/ad1s1c: CAN'T CHECK FILE SYSTEM.
> /dev/ad1s1c: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> Can't stat /dev/ad0s1f: No such file or directory
> Can't stat /dev/ad0s1f: No such file or directory
> /dev/ad0s1f: CAN'T CHECK FILE SYSTEM.
> /dev/ad0s1f: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> Can't stat /dev/ad0s1d: No such file or directory
> Can't stat /dev/ad0s1d: No such file or directory
> /dev/ad0s1d: CAN'T CHECK FILE SYSTEM.
> /dev/ad0s1d: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY:
>        ufs: /dev/ad0s1e (/tmp), ufs: /dev/ad1s1c (/mnt), ufs: /dev/ad0s1f 
> (/usr), ufs: /dev/ad0s1d (/var)
> Automatic file system check failed; help!
> Oct 13 09:57:53 init: /bin/sh on /etc/rc terminated abnormally, going to single 
> user mode
> Enter full pathname of shell or RETURN for /bin/sh:
>
> Failure to boot is natural, since I've used unmodified FreeBSD qemu image.
>
> Sorry for troubling.
>
> --
> Andrey V Khavryuchenko
> Software Development Company http://www.kds.com.ua/
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users