mossiemosforth

I love the flexibility of the system, meaning I can run everything I want to on 1 piece of hardware. What I would like to see is the ability to snapshot VMs brought into the GUI.

Evening all, I'm after advice/opinions for a replacement cache drive in my server. My current Server specs are in my signature, but it boils down to 3x 4tb array, SSHD cache drive and a 240GB SSD I have mounted with UD that my VMs and Docker run on. As My array is around 90% full I want to buy another 4TB drive, so I don't want to spend too much more on a cache. That and given the Proliant only has SATA II capability I don't get (nor am I bothered by) read write speeds. Currently I have a Seagate SSHD (Model ST1000DX001) that is dying a horrible death with over 51K 'reported uncorrects', so I do need to replace it. Now looking I can get another SSHD, either 500GB or 1TB for a reasonable price, but I wondered if these types of drives are really that suitable as a cache drive? I do however need the drive to have a decent size capacity, as I do host a fair amount of data permanently on it (such as my music share) so it's always readily available. Anyway, I've waffled on long enough. Any advice or opinion would be greatly appreciated. TIA

Evening all, I'm hoping someone here more knowledgeable than I with S.M.A.R.T. could have a look at a disk I'm experiencing issues with. I have a SanDisk 240GB SSD I mount with UD, on which I run my VMs and Docker config directories. When upgrading to 6.3.5 I rebooted my server and it didn't come back up. Checked the console and and the bios complained that my SSD has SMART issues. I continued to boot so I could pull off the data (which I have managed to btw) and unraid also complained it failed SMART check. So i checked the drives warranty, 3yrs and I've had it 18months. Easy I though, I'll raise an RMA. Did that and SanDisk asked me to install their tool and run an extended test, sending them a screenshot of the results. Did that on my windows box, and it passed!! I haven't sent this to SanDisk as yet, as I'm sure they'll just tell me to do one. So place it back in my server and now it states it passed SMART checking, but I'm still receiving lots of warnings regarding 'retired block count' and 'reported uncorrect' (screenshot attached). Even though it now 'passes', every time I try to interact with the drive it's either slow, or ends up unresponsive. I'm kind of hoping I can get another failed reading that I can send to SanDisk. I'm stuck, can anyone have a look at the attached SMART report, give me advice. Thanks in advance unraid-smart-20170530-2202.zip

+1 for XFS, mines been working flawlessly for about a year now, mounted with Unassigned Devices

I can't even see my signature block in this new forum format, completely forgot about it. Updated now I've been keeping up with the releases as and when they come, currently running v6.3.2 with no issues

I run my VMs on an SSD mounted with unassigned devices at /mnt/disks/SSD and have done since before v6.1, with no issues. I also run my docker config folders on the same drive, so a subfolder for each - /mnt/disks/SSD/vms and /mnt/disks/SSD/docker My default path for VMs is set to /mnt/disks/SSD/vms, not had any issues using this, just wanted to re-assure you

Sounds like you have done everything correctly. Only piping up as I too have my VMs disks sat on an SSD outside the array using the unassigned devices plugin with no issues. When you have modified the VMs xml it should look similar to this; <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/disks/SSD/VMs/Win10VM/vdisk1.qcow2'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> So the source file starts with /mnt/disks (this is the path that UA plugin uses, the bit in bold) Also ensure the boot order is 1, or if you still have an ISO attached then remove it. Lastly you could also try deleting the address type line (in italic above), this will be automatically re-entered the next time you start the VM as KVM allocates it. I only mention this as I've had occasions where I've edited properties of the VM and I've needed to refresh this, when realistically if you're not changing the VMs hardware details you shouldn't have to. Hope you get it running ok.

Is it only the ssd share that's asking for credentials? Have you set the SMB security settings for Unassigned devices itself? Go to; Settings Tab >> Unassigned Devices (under user utilities, at the bottom of the page) Set the SMB settings as per what you wish, it's the same manner as any other share in unraid I only know as I was in the same position as you a little while ago, performing everything on my UD ssd through putty. I believe this is a global security setting for all UD. I only have the 1 drive setup outside the array, so can't prove it

If you're running v6 you can create a vm, pass the printer through to it and share that way. I've done it with mine so anyone in the house can use it Sent from my Nexus 5 using Tapatalk

you sir, are a true gent. That previous version has worked a treat for me. Now the hideous task of migrating my VMs and Docker to the new drive

I've come looking as i am also having this very same issue. Installed an SSD to host my VMs and Docker, all seems to be good until i tried to mount the disk and the icon never goes green saying mounted. That being said it does actually mount the disk and shares it. Another weird one is for some reason the share name is in lowercase (ssd), whereas in all config files i have defined it in uppercase (SSD), anyone have any idea to fix that? Checked my logs and i also get the same php errors as you all (after reporting it is mounted correctly); Fri Jan 15 18:29:56 GMT 2016: Mounting '/dev/sdf1' Fri Jan 15 18:29:56 GMT 2016: Drive found with the following attributes: name='sdf1', device='/dev/sdf1', part='1', disk='/dev/sdf', label='SanDisk_SDSSDA240G_154608406660-part1', fstype='btrfs', mounted='', mountpoint='/mnt/dis$ Fri Jan 15 18:29:56 GMT 2016: Adding disk ... Fri Jan 15 18:29:56 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:29:56 GMT 2016: Mounting drive with command: mount -t btrfs -o auto,async,noatime,nodiratime '/dev/sdf1' '/mnt/disks/SSD' Fri Jan 15 18:29:56 GMT 2016: Successfully mounted '/dev/sdf1' on '/mnt/disks/SSD' Fri Jan 15 18:29:56 GMT 2016: Partition '/dev/sdf1' successfully mounted. Fri Jan 15 18:29:56 GMT 2016: Defining share 'SSD' on file '/SSD.conf'. Fri Jan 15 18:29:56 GMT 2016: Adding share 'SSD' to /boot/config/smb-extra.conf. Fri Jan 15 18:29:56 GMT 2016: Reloading Samba configuration. Fri Jan 15 18:29:56 GMT 2016: Directory '/mnt/disks/SSD' shared successfully. Fri Jan 15 18:29:56 GMT 2016: Command not available, skipping. Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:29:58 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:00 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:00 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:02 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:02 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:04 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:04 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:06 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:06 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:08 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:08 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:10 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:10 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Fri Jan 15 18:30:12 GMT 2016: PHP Warning: set_error_handler() expects the argument () to be a valid callback in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 428 Would moving back to SNAP be an option do you think?

Thanks for the reply Jon, sounds like promising news. Sadly the VM dropped out on me while watching a TV Show last night, kind of lost my faith in it a little. Where can I find the logs, as to better find out what is going on with it? I've had to plug my raspberry pi back in for now, for stability, so waiting out for a new release should be too bad. On that note do you have a time frame for release? or an idea when Openelec v6.0.0 willl be an available template?

I figured that was the case, as the old AMD 3450 i had ran like a charm and was able to be reset (if it was HDMI i'd keep it) I have both bios types with no avail, shame as the card itself seems to perform well for a low end card. As for trying another rom, i have followed the wiki, but I have no idea what rom 'could' even work with this card. Anything in the region of this model i have tried failed miserably. Seems like buying another card is my best solution, current one that's caught my eye is a Radeon HD5450, I can currently get one for circa £20, should be good enough to run kodi and a few emulators, anyone have have one/know if they work?

I've just re-read all this and though 'wow, i was waffling on'. So i've edited it to bold up my main question, for those like me who hate to read blocks of text. next time i'm not going to write a post so late after staring at a screen for hours.

I got the pulse-eight adaptor working by adding the address manually to the xml for the VM. <hostdev mode='subsystem' type='usb' managed='yes'> <source> <vendor id='0x2548'/> <product id='0x1002'/> <address bus='7' device='5'/> </source> <alias name='hostdev1'/> </hostdev> The above is the code specific to my installation but it might be of some use. Smashing Phil, thanks for the confirmation. Thanks for the code, did you have to manually add it? Just it seems to be the same entered when using the tick boxes on the 'edit VM' screen. Either way, useful non-the-less I think i'll get one ordered once I've solved my graphics card issue.