Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 9 Oct 2014 09:08:49 -0500
From:      "Jay West" <jwest@ezwind.net>
To:        <freebsd-xen@freebsd.org>
Subject:   disk loss
Message-ID:  <000001cfe3ca$8d242950$a76c7bf0$@ezwind.net>

Next in thread | Raw E-Mail | Index | Archive | Help
We're running lots of FreeBSD10 VM's  under Xenserver 6.2, and using FreeNas
9.X for iscsi storage. Note, none of the VM's see iSCSI - just the
hypervisors see it to create their storage repositories.

 

We've noticed an ongoing issue with recovery from crashes or issues with the
NAS. This doesn't happen often at all, but the nas will reboot about once a
year.

 

Windows VM's seem to recover fine. FreeBSD, not so much. The pattern seems
to be that if the NAS holding the SR's for the hypervisor reboots, when the
freebsd vm's come up that have just one virtual disk (boot), it complains
about unclean shutdown and fsck needs to be run. No problem, running fsck
fixes it. However, if the freebsd vm has two virtual disks (boot and data),
the first one (say, ada0) complains about unclean shutdown and fsck will fix
it. But the second disk (say, ada1) is not found. All we get is "can't stat
/dev/ada1p1" or somesuch, and /dev/ad1 is missing from /dev.

 

This seems to be a pretty consistent failure mode. We've tried to detach the
data disk and attach it to a different VM - but no joy.

 

1)      Anyone have any idea why FreeBSD seems so affected and Windows
doesn't?

2)      Any ideas as to how to (non-destructively) get /dev/ada1 back so we
can try to access the data?

 

Thanks in advance for any thoughts.

 

J




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000001cfe3ca$8d242950$a76c7bf0$>