RAIDiator-x86 4.2.28 | VirtualBox image #notsupported

I have this image -- and the 6.0.6 image (which I then upgraded to 6.1.6) running in VMWare Workstation. This image was easy to fix for VMWare, the 6.0.6 was more challenging. Now that they are in Workstation - they should easily migrate over to ESXi. I can post instructions if anyone is interested.

lancerus wrote:
I have this image -- and the 6.0.6 image (which I then upgraded to 6.1.6) running in VMWare Workstation. This image was easy to fix for VMWare, the 6.0.6 was more challenging. Now that they are in Workstation - they should easily migrate over to ESXi. I can post instructions if anyone is interested.

I'd be very interested in the procedure you used to get ReadyNAS OS6 going in VMware :)

Please feel free to PM me the info, or post it here for others too.

Thanks muchly :)

lancerus wrote:
I have this image -- and the 6.0.6 image (which I then upgraded to 6.1.6) running in VMWare Workstation. This image was easy to fix for VMWare, the 6.0.6 was more challenging. Now that they are in Workstation - they should easily migrate over to ESXi. I can post instructions if anyone is interested.

me, too!

I'm just trying to convert OS6.0.6 VirtualBox image to vmware's with VMware workstation 10.
I attached converted disks to SATA controller, but failed to boot.
serial output message says 'ERROR: Could not mount root RAID device' like below.

SYSLINUX 3.31 Debian-2007-03-09  Copyright (C) 1994-2005 H. Peter Anvin
boot: 
Loading kernel.......................................................................
Loading initrd.gz.............................................Ready.
Starting the boot process...
Detected system type: UNKNOWN
Loading kernel modules...done
Bringing up network...eth0.done
Bringing up RAID arrays...done
ERROR: Could not mount root RAID device
/bin/sh: can't access tty; job control turned off
/ # 

How do you resolve the issue ?
I suspect it comes from different SATA emulated device on the hypervisors.
Is it required to install another driver ?
I'll make Debian VM with SATA configuration and try to check device emulation and drivers being used.

Could you share your procedure ? :)

p.s.
Any way, we should move thread below or create new one. It seems off topic, isn't it ? :wink:

NETGEAR ReadyNAS • View topic - ReadyNAS OS 6.0.6 | VirtualBox Image #notsupported
http://www.readynas.com/forum/viewtopic.php?f=35&t=70699

You need a newer version of ReadyNAS OS. Update the firmware in the VM to e.g. 6.1.7 RC5: http://www.readynas.com/forum/viewtopic.php?f=154&t=72282

Then try converting it.

Oh, it just depends OS version.
I never imagine that.

On VirtualBox,
1. Update ReadyNAS VM to latest via WebUI.
2. Export VM with OVF1.0

On VMware workstation 10,
3. Open OVF with VMware WS10 & Import.
4. Remove all virtual harddrives (it's connected as IDE drives)
5. Add SATA drives and choose those existing vmdk.

That's all.
so easy ! Thanks. :D

Clearly they must have added support for virtualising it with VMWare in a more recent firmware than 6.0.6.

Workstation has always worked I believe, since it has virtual SATA disks. The issue is with VMware ESX, as it only presents SCSI disks.

Hi

I have got this image up and running locally and it seems to work well, so thanks for that. However I do have a problem that I could do with some help with. I am trying to use the image to test out hosting a Z-Wave controller. In order to do that I need to get USB support for the controller hardware and part of that process involves grabbing the Raidator GPL sources and unzipping it so that I can build the missing kernel modules. Doing that in the VB image is proving to be difficult because whilst there is enough disk space (I think) there are not enough inodes. I thought that I could just add some more disks and expand the volume on which I am trying to unzip the sources but I don't seem to be able to get Raidiator to recognize the new devices in a way that it will allow me to either expand or create a new volume on them.

Does anyone have any tips?

Thanks

James.

Make sure you extract all the files to /c, not to / (different limited partition which easily runs out of inodes).

Unfortunately I was trying to unzip to /c and still there is nowhere near enough inodes :-(