BobPhoenix

If you use the method suggested by Fireball3 you would edit the 5IT.bat files and add "-b MPTSAS2.ROM" to the sas2flsh.exe line it is the same for opentoe's method. Downloads zip file and instructions in this post for Fireball3's method: http://lime-technology.com/forum/index.php?topic=12767.msg259006#msg259006 opentoe's method is here: http://lime-technology.com/forum/index.php?topic=12767.msg409058#msg409058 So just add the -b MPTSAS2.ROM to the end of the sas2flsh line for both methods if you want to see the bios boot up - like I do. This is making the assumption that the bios rom image is MPTSAS2.ROM for the opentoe method like the Fireball3 method. I've never tried opentoe's method because I had all of mine already flashed before he responded but it looks to be a lot simpler.

I think with XFS you might have lost all your data in your scenario. The xfs_repair tool does not seem to have an option equivalent to reiserfsck --scan-whole-partition that looks for file fragments that can be recovered. I assume this is because there is less redundancy in the file system so that such fragments can be properly identified and used in recovery. It simply repairs starting from the superblock and fixing any 'bad' links by chopping off what they might have originally pointed to (thus leading to data loss). The only thing that I have found that it has that reiserfsck does not have is the ability to scan the disk looking for backup copies of the superblock if you happen to corrupt the one at the start. Definitely sounds like I will not be switching any time soon. I definitely want recovery over performance. So I think I have officially changed my opinion. Thanks.

I wondered about that. I had to recover ReiserFS and got back 90% of my files after putting a completely full cache drive in as parity in a parity sync for about 5-10 minutes before I caught it. So in other words the corruption I experienced would have been the same for either ReiserFS or XFS. That is bad news maybe I won't switch my drives now. Was hoping XFS recoveries would be better then ReiserFS not worse. What I expected to be worse was btrfs.

There was a ReiserFS problem with one of the V5 betas that was caused by a Kernel update that Limetech had to patch because ReiserFS isn't a main stream file system in Linux any more so doesn't get the testing it used to. I WILL be updating all of my arrays because of this reason at some point but I'm not in a big hurry. Each new kernel that Limetech uses to fix other bugs introduces the possibility of a bug in ReiserFS similar to the bug in the V5 betas. And since ReiserFS isn't supported in all of the linux distributions it gets less testing. XFS is a newer file system and is still used in more/all? of the Linux distributions (including unRAID) so it should be better tested. LimeTech is going to have to be very careful when testing if they want to keep supporting it and may have to create a patch for it like they did during the V5 betas. Hopefully any bugs would be caught before any future unRAID released versions but I would like to be on a newer better supported file system and not tempt fate too much.

I have one of two USB MB controllers (the other is for ESXi and unRAID flash drives) passed through with ESXi 5.0 on a Tyan S5512 MB and E3-1230 v1 CPU works great with my HVR-950Q USB tuners on my Windows 7 x64 VMs. Haven't tried it with unRAID native yet but I will likely be trying it this winter some time.

This is true of course ... but that effectively shuts down the array for the duration of your pre-clears => which, with modern drives (and 2-3 passes) could easily be several days. Not, in most cases, a very desirable way to go. One of the key benefits of pre-clearing is you don't have an unavailable array during a clear operation. I think he was implying you could setup a free version on another PC to preclear the drives then transfer them to the server - not doing the preclears on the server the drives will eventually be attached to.

Thank you. It is a must have if you want to use Dockers. Hope it becomes a built in plugin in a future version of unRAID.

One less thing to need unMenu for now. Thanks.

I installed from a TechNet ISO Win7x64 pro and it went fine. Boots up with no problems - at least for the next few days - until I have to activate it or reinstall again anyway. I used the AMD64 drivers for it and installed like the wiki said balloon, net, vioserial and finally viostor order. For my Windows7 32bit VMs I transferred from an ESXi box I used the 32 bit drivers. They are working fine as well on same 6.0.1 unRAID server actually. It is a SandyBridge CPU and Tyan S5512 MB with 16GB memory if that makes any difference.

I wonder if the Q08 screws are the same as those of the V354. The V354B screws are the same as the screws I use for my SSDs (in size at least maybe not the same treads) and were black. V354 screws are the same as the SuperMicro 3x5 drive trays are interchangeable as far as I can remember. I have retired my V354 case for R4. Edit fixed the case name %$#& it!

Someone else may have a better idea so wait for their response! Especially if you don't like what I'm going to suggest and there is an easier way. But as I see it there are two options. [*] Add a two port controller card to your box and pass through the controller to the VM then put your drive on it. [*]Add your drive to unRAID and us the UnassignedDevices plugin to mount the drive then create an image file on it that you add to your VM. But as I said there may be more options that I haven't a clue existed. If this was ESXi I would tell you to RDM the drive but I haven't see that as an option with unRAID or KVM for that matter.

Thought that is what you would say but had to suggest it.

How about a phone home every day that states "I'm using this docker and this docker, etc..." and then you base the star rating on the count. That would get you popularity based on use count anyway. Obviously you would want to provide an opt out or maybe make it a opt in so that it does just start sending data you have to allow it first.

Even if it is possible to convert to/run on 64 bit I wouldn't trust it enough to actually do it myself. I would stick with what has worked. That is why I boot from a DOS USB stick and flash from a computer with a compatible chipset. If it works don't fix it is what I live buy. Saves me time if nothing else.

Actually I think he meant PMR and he is hoping for ~1.75TB platters by November. Or increase the platter count past 5.

The method to flash a H310 was posted in this thread by Fireball3. And the commands to use are coded in the ".bat" files in the archive earlier in this thread. I've done 4 H310's so far myself it works great. I use Fireball3's method and flash from USB dos boot. Here is his post http://lime-technology.com/forum/index.php?topic=12767.msg259006#msg259006

No problems for me so far. I only have 3 6TB WD Reds in service so far but 1 more will be added in the next month and 1 as a spare. All went through 3 preclear cycles with flying colors so not expecting troubles. So knock on wood now that I have jinxed them.

Did you follow the directions exactly when you installed your Windows 7 from scratch? Here is what I did for my 2 32bit Windows 7 VMs: [*]Set the VM to Window 7 / 2008 [*]Put the Win7 32Bit OS ISO image in correct box. [*]Put the virtio driver ISO (virtio-win-0.1.96.iso) in correct box. [*]Setup memory to 3GB (the highest I've found to not cause Windows to use PAE mode) [*]Setup location and size of the boot hard drive and other parameters [*]Start up the VM. [*]When Windows 7 setup stops and give you the empty box where you would pick a drive to install to is where you install drivers. [*]Install the balloon driver (in my case I used Balloon\w7\x86 directory because I'm using 32 bit Win7 even though the instructions tell you to pick AMD64) Windows tells you no drives were found but it DID install the balloon driver. [*]Install the NetKVM driver (once again I used the NetKVM\w7\x86 directory because I'm on 32 bit Win7) Windows tells you no drives were found but it DID install them. [*]Install the vioserial driver (once again I used the vioserial\w7\x86 directory because I'm on 32 bit Win7) Windows tells you no drives were found but it DID install them. [*]Install the viostor driver (once again I used the viostor\w7\x86 directory because I'm on 32 bit Win7) Windows displays the boot drive now to install your OS to. [*]Complete the install of windows. I just setup a 64 bit Win7 and followed the method above except I used Balloon\w7\amd64, NetKVM\w7\amd64, vioserial\w7\amd64 & viostor\w7\amd64 drivers since this was a 64 bit Win7 OS. Boots fine no driver problems with signing. See attached image.

When you edited the memory the VM's XML would have removed any custom edits. Limetech has said they will put a warning about that in a future version. So that could be why the XML edits disappeared but does NOT explain the "go" file.

Just an FYI. I am currently using a Windows 7 VM that I did NOT have to use the VFIO Bind process on my passed through Nic TO MAKE THIS POST. In device manager I see "Intel® 82574L Gigabit Network Connection #2" which happens to be the model of the MB nic on my Tyan S5512GM4NR MB. I do NOT have the virtual nic defined in the XML any more I removed it once the passed through nic was up and running. So I don't think you need the VFIO Bind process any more and you can do the simple passthrough outlined here EVEN FOR NICs. Here is my XML: <domain type='kvm' id='7'> <name>Online</name> <uuid>9e32368f-ae48-f3ce-a836-12a214836dd1</uuid> <description>Internet access from here</description> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/Online/Online.img'/> <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> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VMs/raw/Install.img'/> <backingStore/> <target dev='hdd' bus='virtio'/> <alias name='virtio-disk3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/VMs/ISOs/en_windows_7_professional_with_sp1_x86_dvd_u_677056.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/VMs/ISOs/virtio-win-0.1.96.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Online.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </memballoon> </devices> </domain> Here is what I added to my XML for the NIC (you can find it above with the address type line added): <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> </hostdev> Here is what I removed from my XML to remove the Virtual NIC: <interface type='bridge'> <mac address='52:54:00:26:17:ac'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Here are my PCI devices: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 7 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation C204 Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 02:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 09:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 02) 0a:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10) I also attached my syslinux.cfg so that you can see it is still the stock one. syslinux.cfg

HGST are still selling 5TB 7200rpm Deskstar NAS drives. Possibly 6TB as well? I have a N54L unRAID server composed of HGST NAS 6TB drives.

Yes and no. Looks like for most people it isn't needed and while it helps me out I can live without it. Once SageTV releases it's open source version I can change the code for me to eliminate it as much as possible. Plus I will be able to switch to a linux version and can further eliminate what appears to be a windows problem. In other words I'm OK if it disappears because it doesn't completely eliminate my problems anyway.

Like this. I get pauses in playback on SageTV all the time if I don't have spinup groups installed and do a scan for new media. SageTV will read each existing media file (just a few bytes) to make sure it exists before deleting it from the database. If you are playing back a file at the same time it will pause while unRAID spins up the drive(s) that the scanner is currently trying to read from.

Do not have one myself just posted an alternate link. I have 4 of the Kingston G2's licensed. Was hoping this would be a good AVAILABLE substitute but guess not.

Here is link on Amazon since Buy.com is out: http://www.amazon.com/Lexar-High-Performance-microSDHC-Mobile-LSDMI16GBSBNA600R/dp/B00BQ5UWXI/ref=sr_1_5?ie=UTF8&qid=1435581490&sr=8-5&keywords=Lexar+High-Performance+MicroSDHC+633x