arjans Posted March 9, 2015 Share #1 Posted March 9, 2015 Hi all, Using this link https://raymii.org/s/tutorials/FreeBSD_10.1-release_Openstack_Image.html I am atampting to run XPEnology in the cloud. Unfortunately the bootimage is not recognising the harddisk. After some research on both my VM on my laptop (on which XPEnology is running fine) and my NAS (Synology), could it be true that the the bootimage is only looking at devices at /dev/sd[a-z] and so does not recognise a device at /dev/vd[a-z]? (differece being physical and virtual devices). I can imagine the guest in virtualbox does not know it being virtualised and so attaches the disk to /dev/sda, while at my cloudprovider (cloudvps; from which I also received above url) probably attaches it to /dev/vda. Also note that in the url 'vdb' is mentioned, obviously i have tried many options including: /dev/vdb, /dev/vda, vdb, vda, /dev/sda and /dev/sdb. An email has been sent to support to get the probably unfortunate confirmation that drives will be attached to /dev/vd[a-z]. So in conclusion: is my assumption true? (only recognising devices at /dev/sd[a-z]) And if zo, could we (or could someone help me/point me in the right direction) fix this? Many thanks in advance, hope to hear something soon Arjan Link to comment Share on other sites More sharing options...
arjans Posted March 9, 2015 Author Share #2 Posted March 9, 2015 So I got an email back, indeed the disk will be attached to /dev/vd[a-z]. So somewhere in the kernel we need to enable to look for disk at /dev/vd[a-z]. Any ideas where this should be? Arjan Link to comment Share on other sites More sharing options...
Diverge Posted March 9, 2015 Share #3 Posted March 9, 2015 This may or not be helpful, but look into how people got Xenserver working; as I think I remember it having a an issue since it used /dev/xvda. Start here viewtopic.php?f=15&t=3001 from there are links to other posts/threads. Good luck! Link to comment Share on other sites More sharing options...
Recommended Posts