Ice_Black Posted March 14, 2013 Share Posted March 14, 2013 Managed to get Unraid to boot up via Plop. I have added a few virtual Hard Disk's from VM setting on Esxi (Not using RDM and no pass thru SATA controller). Here what I did from VM setting: 1. Click on Add 2. Click on Hard Disk on the list and click Next 3. Select "Create a virtual disk" and click on Next 4. Choose a disk size and select a datastore where should the virtual disk should be created in. 5. Click on Next and Finish Screenshot: On Unraid page it show all "unassigned" disks and when I select any disk from the dropdown then it goes back to 'unassigned' I have notice on the syslog it show: Mar 12 17:14:02 Tower emhttp: shcmd (100): rmmod md-mod |& logger Mar 12 17:14:02 Tower emhttp: shcmd (101): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Mar 12 17:14:02 Tower kernel: md: unRAID driver removed Mar 12 17:14:02 Tower kernel: md: unRAID driver 2.1.5 installed Mar 12 17:14:02 Tower kernel: read_file: error 2 opening /boot/config/super.dat Mar 12 17:14:02 Tower kernel: md: could not read superblock from /boot/config/super.dat Mar 12 17:14:02 Tower kernel: md: initializing superblock Mar 12 17:14:02 Tower emhttp: shcmd (102): udevadm settle Mar 12 17:14:03 Tower emhttp: Device inventory: Mar 12 17:14:03 Tower emhttp: (sda) 8388608 Mar 12 17:14:03 Tower emhttp: (sdb) 1073741823 Mar 12 17:14:03 Tower emhttp: (sdc) 1073741823 Mar 12 17:14:03 Tower emhttp: (sdd) 1932735283 Mar 12 17:14:03 Tower kernel: mdcmd (1): import 0 0,0 Mar 12 17:14:03 Tower kernel: mdcmd (2): import 1 0,0 Mar 12 17:14:03 Tower kernel: mdcmd (3): import 2 0,0 Mar 12 17:14:03 Tower kernel: mdcmd (4): import 3 0,0 Mar 12 17:14:03 Tower kernel: mdcmd (5): import 4 0,0 Mar 12 17:14:03 Tower kernel: mdcmd (6): import 5 0,0 Mar 12 17:14:03 Tower emhttp: shcmd (103): /usr/local/sbin/emhttp_event driver_loaded Mar 12 17:14:03 Tower emhttp_event: driver_loaded What could be wrong? I have tried reformat the Flash USB and no luck! Syslog attached.. syslog.txt Quote Link to comment
AndroidCat Posted March 14, 2013 Share Posted March 14, 2013 From my experience you can only use IDE virtual drives. Quote Link to comment
BetaQuasi Posted March 14, 2013 Share Posted March 14, 2013 As per the other thread where I answered this - they need to be IDE virtual drives.. but if you do this, your performance will be quite ordinary. You need to either RDM your drives or pass through a controller. If you are using on board SATA, then you are best to RDM. Quote Link to comment
Ice_Black Posted March 14, 2013 Author Share Posted March 14, 2013 As per the other thread where I answered this - they need to be IDE virtual drives.. but if you do this, your performance will be quite ordinary. You need to either RDM your drives or pass through a controller. If you are using on board SATA, then you are best to RDM. Ohh you are correct, - I just changed to IDE virtual drives and it work! Yes I will do RDM but at the moment I am experimenting Which has better performance RDM or pass through a controller? Quote Link to comment
BetaQuasi Posted March 14, 2013 Share Posted March 14, 2013 There is no difference between the two - however replacing a failed drive that has been RDM'ed is far more complex and potentially dangerous than a passed through controller. Quote Link to comment
cj0r Posted March 14, 2013 Share Posted March 14, 2013 I remember I chose Pass-Through because I believed that RDM did not allow spin down, is that still true? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.