BobPhoenix

I have a 16GB cruzer fit that died. It is no longer recognized by any machine you plug it into. It is the only flash drive that has done this to me so far. But I would still buy them and have (32GB version). I just got a lemon with my 16GB.

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

You could always try passing through the USB controller if nobody has a better idea. That does mean that anything else on the same controller gets passed through so make sure it doesn't have your unRAID boot flash drive attached before attempting to pass through the controller. I would consider this a brute force last try approach unless no other ideas are suggested. Another thought I just had: Powered hub.

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.

I've got 5 on order from Amazon so will see what those serial numbers look like ~Aug11th.

I have two dead ones that end in GS as well so maybe they expanded the last two into the last 4 with the 5TB drives.

Nope must be new. Here are my Toshiba Drives all appear to have unique last 4.

I'll look tonight at my 3TB Toshiba's but I believe it is NEW. I don't remember it being the same when I bring up myMain on my Toshiba drive server.

Sorry I answered what I felt qualified to answer. Hopefully a more knowledgeable user will be able to answer them for you.

Look here on how to transfer your USB key to a new USB flash drive: http://lime-technology.com/replace-key/

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.

My cache is a 250GB Samsung SSD. Would it be wise for me to have the vm use that much space? Also, should I just add my "camera storage" disk that I had lying around into the array and create a share that only lives oh that disk? Can I turn parity protection off on that share since it will constantly be written to? I wanted to keep this non critical, captured data separate which is why I was attempting to keep it off the array. If all you have on it is software installs and no data then NO I wouldn't use all 250GB for it. You may want to install other VMs and you get the best performance (I've read anyway) from RAW format rather than QCOW2 so so the image would actually occupy whatever you give it. You could add your camera storage to an array disk but NO you cannot turn off parity protection on a single array disk. You could use the Unassigned Devices plugin to mount it outside the array and not have parity protection on it. I believe the plugin will allow sharing from the devices it mounts but I've never used it so far so I could be wrong. I always wanted more than one disk and the fastest access to the drives so I always have passed through a controller. But if you just want a single device the plugin would probably be the best option for you.

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.

Actually I though the "ACS? (sorry not at home so can't get exact title) override" would allow this as long as the option doesn't cause instability on your system?

Here is what I've done in the past on 6b5 (back to ESXi currently but will switch to 6 stable eventually): [*]Setup the virtual disk on my cache drive with enough space for Windows to run and have some expansion available (50GB for Windows 7 x64) [*]Pass through a controller where I connect my recording drives for SageTV (also passed through the tuners that SageTV used to record TV). Maybe something like that will work for you.

Another though is a SAS expander if your controller will work with one (Do have and IBM1015/LSI 9240-8i/LSI 9211-8i class controller connected to your drives?). You then get a external cabnet that has a SAS connection an route a cable from the expander to the external cabnet. SAS expanders allow much faster access but still reduce the parity check speeds by about 25% based on my analysis on a 16 drive array.

Also I would use the Red drives (and do) because they have a longer warranty.

Didn't see the reply until now - sorry. I have them ordered now. Some are just ordered for the sake of ordering them as I would think they would have to be implemented at the same time or not at all. Add Weebo's to the list as well. Probably should be first.

I thought that might be the answer. However unless we keep asking for it it is always going to be unlikely to make the priority list. I'm just glad it is now a low priority now instead of no chance at all (my impression from last discussion I took part in).

I asked for this too but all they said they would do is add a warning that custom edits to the XML would be lost when selecting the edit option. Not sure the warning has even made it in yet.

Just use any old flash drive and boot up with 5.0 or 6.0 unRAID and preclear your disks on the other machine. You don't need a key for that as far as I know but I will say I've only used unRAID 5.0 for this so cannot confirm about 6.0. I do know 4.7 would be limited to 2.2TB disks in the array so likely it wouldn't preclear > 2.2TB correctly.