pyrater

think i found the error... NOTE: If you do NOT have a cache device, you will need to add those three shares manually if you wish to utilize apps or VMs on unRAID.

root@Icarus:/mnt/disk8/Windows_NoVPN_VirtDriver# find / . -type f -name "*.conf" find: WARNING: Hard link count is wrong for `/proc/fs' (saw only st_nlink=10 but we already saw 8 subdirectories): this may be a bug in your file system driver. Automatically turning on find's -noleaf option. Earlier results may have failed to include directories that should have been searched. find: `/proc/20742': No such file or directory /boot/config/plugins/dynamix.system.temp/drivers.conf /boot/config/plugins/dynamix.system.temp/sensors.conf /usr/share/dbus-1/session.conf /usr/share/dbus-1/system.conf /usr/share/samba/setup/olc_syncrepl.conf /usr/share/samba/setup/modules.conf /usr/share/samba/setup/olc_mmr.conf /usr/share/samba/setup/olc_syncrepl_seed.conf /usr/share/samba/setup/mmr_serverids.conf /usr/share/samba/setup/memberof.conf /usr/share/samba/setup/slapd.conf /usr/share/samba/setup/named.conf /usr/share/samba/setup/mmr_syncrepl.conf /usr/share/samba/setup/krb5.conf /usr/share/samba/setup/refint.conf /usr/share/samba/setup/olc_serverid.conf /var/lib/netatalk/afp_signature.conf /mnt/user/Data/Apps/Operating_Systems/Windows 7 USB Method/WAIK Files/UsbBootWatcher.conf /mnt/user/Data/Apps/Buffalo drivers/tool/ClientMgr3/ConfProc.conf /mnt/disk4/Data/Apps/Operating_Systems/Windows 7 USB Method/WAIK Files/UsbBootWatcher.conf /mnt/disk2/Data/Apps/Buffalo drivers/tool/ClientMgr3/ConfProc.conf /lib/modprobe.d/evbug.conf /lib/modprobe.d/8139cp.conf /lib/modprobe.d/watchdog.conf /lib/modprobe.d/framebuffers.conf /lib/modprobe.d/isdn.conf /lib/modprobe.d/psmouse.conf /lib/modprobe.d/hostap.conf /lib/modprobe.d/isapnp.conf /lib/modprobe.d/hw_random.conf /lib/modprobe.d/scsi-sata-controllers.conf /lib/modprobe.d/tulip.conf /lib/modprobe.d/pcspkr.conf /lib/modprobe.d/sound-modems.conf /lib/modprobe.d/bcm43xx.conf /lib/modprobe.d/usb-controller.conf /lib/modprobe.d/oss.conf /lib/modprobe.d/via-ircc.conf /lib/modprobe.d/eepro100.conf /lib/modprobe.d/eth1394.conf /lib/dhcpcd/dhcpcd-hooks/50-ntp.conf /lib/dhcpcd/dhcpcd-hooks/50-yp.conf /lib/dhcpcd/dhcpcd-hooks/20-resolv.conf /etc/cache_dirs.conf /etc/cgconfig.conf /etc/resolv.conf /etc/host.conf /etc/inetd.conf /etc/logrotate.conf /etc/php-fpm/php-fpm.conf /etc/libvirt-/virtlogd.conf /etc/libvirt-/virtlockd.conf /etc/libvirt-/libvirt.conf /etc/libvirt-/libvirt-admin.conf /etc/libvirt-/qemu-lockd.conf /etc/libvirt-/libvirtd.conf /etc/libvirt-/qemu.conf /etc/libvirt-/virt-login-shell.conf /etc/dnsmasq.conf /etc/serial.conf /etc/mtools.conf /etc/genpowerd.conf /etc/apcupsd/apcupsd.conf /etc/ntp.conf /etc/ld.so.conf /etc/openldap/ldap.conf /etc/netatalk/afp.conf /etc/netatalk/dbus-session.conf /etc/netatalk/extmap.conf /etc/sysctl.d/60-libvirtd.conf /etc/sysctl.conf /etc/sensors.d/sensors.conf /etc/modprobe.d/kvm-intel.conf /etc/modprobe.d/scsi-sata-controllers.conf /etc/modprobe.d/kvm.conf /etc/modprobe.d/kvm-amd.conf /etc/ca-certificates.conf /etc/cgrules.conf /etc/dhcpcd.conf /etc/dbus-1/session.conf /etc/dbus-1/system.conf /etc/dbus-1/system.d/avahi-dbus.conf /etc/vsftpd.conf /etc/sensors3.conf /etc/cgsnapshot_blacklist.conf /etc/nfsmount.conf /etc/nscd.conf /etc/rsyslog.conf /etc/mke2fs.conf /etc/smartd.conf /etc/ssmtp/ssmtp.conf /etc/sasl2/libvirt.conf /etc/samba/smb-names.conf /etc/samba/smb.conf /etc/samba/smb-shares.conf /etc/avahi/avahi-daemon.conf /etc/request-key.conf /etc/cgred.conf /etc/udev/udev.conf /etc/rc.d/rc.inet1.conf /etc/nsswitch.conf /etc/lvm/lvm.conf /etc/lvm/lvmlocal.conf

I do not see any config file anymore. I thought the configs were with the img. I have 2 VMS /mnt/disk8/Windows_NoVPN_VirtDriver/vdisk1.img /mnt/disk9/Windows_VPN_VirtDriver/vdisk1.img Unless you mean \flash\config\plugins\dynamix.kvm.manager\qemu

upgraded from 6.1.9 to this and now the VM Manager is gone..... I had VM's set up and now theres a new UI that wants me to specify new locations..?

Just goto a full blown VM and profit.

IT WILL BE A SLAUGHTER!

We used it due to the small size yes, i do not remember if the stock one fit but i do not believe so.

Thanx JonP ! I will post the steps that I used to this thread if successful for others.

Has anyone done this? Is it possible? If not is it possible to convert it to a .img and boot it that way? I know that a OVA file is nothing more than a TAR file, containing the .OVF and .VMDK file.... So i am not sure the correct method to do this; and i REALLY do not want to rebuild this image from scratch. Would it be as simple as the web describes? $ tar xvf MyAppliance.ova $ qemu-img convert -O qcow2 MyAppliance-disk1.vmdk MyAppliance.qcow2

Happy to report that with the SSD's connected directly to the mobo and not the ADD-IN cards 6.1.3 works. The problem is related to those cards and the latest update... SAT2-MV8 Raid cards + Unraid 6.1.3 = NOT WORKING FOR SSD'S

Seems like a software issue, it runs 100% smooth on 6.0.1 with everything on the add-in cards. It only crashes when its on the latest version of unraid... I now have the SSD's installed directly to the mobo, i will try the latest version of unraid now.... :cross fingers:

They are all using add-on controllers, none are on the on-board ports, they are all connected to 3 x SAT2-MV8 Raid cards. Which is why i am confused as to why the motherboard would be the issue... I did try using different ports, but i haven't tried to connect the SSD'd to the MOBO directly... Seemed like the better issue was to report the bug and try and see if they could do a quick patch or fix it in the next release.... http://www.supermicro.com/products/accessories/addon/AOC-SAT2-MV8.cfm

So im stuck with 6.0.1 or i have to buy new hardware that doesn't seem right... and its expensive.

Rob, thank you for the reply; this setup has worked for years until something changed in unraid.... like i said it works fine on 6.0.1

Full syslog here http://pastebin.com/W8KQSnw4 If i roll ALL THE WAY back to unRAIDServer-6.0.1-x86_64.zip it works... It is indeed not a problem with my hardware with is annoying to say the least... Does anyone have the download links to the 6.1-RC1 - RC 6 for testing... .This bug was introduced by limetech at some point.... Can i get an official response from JonP or Limetech, is there hope for a fix down the road? 6.1.3 Hangs on boot 6.1.2 Hangs on boot as well

OK so i am at a loss, i replaced ALL MY SSD's with brand new SSD's and its still crashing!!!!! Even when booting safe mode it goes to login: then crash with the text as seen below. I can login VIA putty but not the webgui... I got the log please see below... Oct 2 18:29:04 Icarus kernel: sdh: sdh1 Oct 2 18:29:04 Icarus kernel: sd 21:0:0:0: [sdh] Attached SCSI disk Oct 2 18:29:05 Icarus kernel: ata26: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 2 18:29:05 Icarus kernel: ata26.00: ATA-9: SanDisk SDSSDA240G, 153611406099, U21010RL, max UDMA/133 Oct 2 18:29:05 Icarus kernel: ata26.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 31/32) Oct 2 18:29:05 Icarus kernel: ------------[ cut here ]------------ Oct 2 18:29:05 Icarus kernel: kernel BUG at drivers/ata/sata_mv.c:2120! Oct 2 18:29:05 Icarus kernel: invalid opcode: 0000 [#1] PREEMPT SMP Oct 2 18:29:05 Icarus kernel: Modules linked in: md_mod(-) w83627hf hwmon_vid k10temp sata_mv forcedeth sata_nv pata_amd acpi_cpufreq Oct 2 18:29:05 Icarus kernel: CPU: 1 PID: 1149 Comm: scsi_eh_25 Not tainted 4.1.7-unRAID #3 Oct 2 18:29:05 Icarus kernel: Hardware name: Supermicro H8DM8-2/H8DM8-2, BIOS 080014 10/22/2009 Oct 2 18:29:05 Icarus kernel: task: ffff88011af41920 ti: ffff88021a7cc000 task.ti: ffff88021a7cc000 Oct 2 18:29:05 Icarus kernel: RIP: 0010:[<ffffffffa008c634>] [<ffffffffa008c634>] mv_qc_prep+0x147/0x1f2 [sata_mv] Oct 2 18:29:05 Icarus kernel: RSP: 0018:ffff88021a7cf868 EFLAGS: 00010006 Oct 2 18:29:05 Icarus kernel: RAX: ffff8800d9def40a RBX: ffff8800d9e41d58 RCX: ffff8800d9def400 Oct 2 18:29:05 Icarus kernel: RDX: ffff8800d9def447 RSI: 0000000000000001 RDI: ffff8800d9e41d58 Oct 2 18:29:05 Icarus kernel: RBP: ffff88021a7cf888 R08: ffff8800db90b060 R09: 0000000000000046 Oct 2 18:29:05 Icarus kernel: R10: 00000000d9e4377f R11: ffff8800db90b098 R12: ffff8800d9e15818 Oct 2 18:29:05 Icarus kernel: R13: 0000000000000001 R14: ffffffff81810a80 R15: ffff8800db90b098 Oct 2 18:29:05 Icarus kernel: FS: 00002af014b03600(0000) GS:ffff88011bc40000(0000) knlGS:0000000000000000 Oct 2 18:29:05 Icarus kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Oct 2 18:29:05 Icarus kernel: CR2: 00000000006e4c88 CR3: 00000000017f9000 CR4: 00000000000006e0 Oct 2 18:29:05 Icarus kernel: Stack: Oct 2 18:29:05 Icarus kernel: ffff8800d9e41e58 ffff8800d9e41d58 ffff8800d9e41e58 ffff8800d9e40000 Oct 2 18:29:05 Icarus kernel: ffff88021a7cf8e8 ffffffff8145d238 ffff88021a7cf8b8 ffff88021a7cf9b8 Oct 2 18:29:05 Icarus kernel: 0000000100000000 0000000100000002 ffff88021a7cf8c8 ffff8800d9e42268 Oct 2 18:29:05 Icarus kernel: Call Trace: Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d238>] ata_qc_issue+0x268/0x2c7 Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d515>] ata_exec_internal_sg+0x27e/0x478 Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d78d>] ata_exec_internal+0x7e/0x8b Oct 2 18:29:05 Icarus kernel: [<ffffffff810783f1>] ? vprintk_default+0x18/0x1a Oct 2 18:29:05 Icarus kernel: [<ffffffff81465f33>] ata_read_log_page+0xdf/0x11d Oct 2 18:29:05 Icarus kernel: [<ffffffff8145eb30>] ata_dev_configure+0x9ed/0xee3 Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d7bf>] ? ata_do_dev_read_id+0x25/0x27 Oct 2 18:29:05 Icarus kernel: [<ffffffff814684b6>] ata_eh_recover+0x77f/0xf86 Oct 2 18:29:05 Icarus kernel: [<ffffffff8146b07d>] ? ata_sff_softreset+0x166/0x166 Oct 2 18:29:05 Icarus kernel: [<ffffffffa008d627>] ? mv5_reset_hc+0x10d/0x10d [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffffa008b731>] ? mv_pmp_hardreset+0x58/0x58 [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffff8146cb5c>] ? ata_bmdma_interrupt+0x184/0x184 Oct 2 18:29:05 Icarus kernel: [<ffffffff8146d65a>] sata_pmp_error_handler+0xfb/0x82d Oct 2 18:29:05 Icarus kernel: [<ffffffff81057498>] ? try_to_grab_pending+0x45/0x146 Oct 2 18:29:05 Icarus kernel: [<ffffffff81082a85>] ? lock_timer_base.isra.25+0x26/0x4a Oct 2 18:29:05 Icarus kernel: [<ffffffffa008ac88>] mv_pmp_error_handler+0x7b/0x84 [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffff81468f7e>] ata_scsi_port_error_handler+0x21b/0x55f Oct 2 18:29:05 Icarus kernel: [<ffffffff8146934e>] ata_scsi_error+0x8c/0xb7 Oct 2 18:29:05 Icarus kernel: [<ffffffff81448b30>] scsi_error_handler+0xac/0x4a0 Oct 2 18:29:05 Icarus kernel: [<ffffffff81448a84>] ? scsi_eh_get_sense+0xd4/0xd4 Oct 2 18:29:05 Icarus kernel: [<ffffffff81448a84>] ? scsi_eh_get_sense+0xd4/0xd4 Oct 2 18:29:05 Icarus kernel: [<ffffffff8105c792>] kthread+0xd6/0xde Oct 2 18:29:05 Icarus kernel: [<ffffffff8105c6bc>] ? kthread_create_on_node+0x172/0x172 Oct 2 18:29:05 Icarus kernel: [<ffffffff815f5a12>] ret_from_fork+0x42/0x70 Oct 2 18:29:05 Icarus kernel: [<ffffffff8105c6bc>] ? kthread_create_on_node+0x172/0x172 Oct 2 18:29:05 Icarus kernel: Code: 12 66 89 51 0a eb 26 0f b6 43 2a 80 cc 11 66 89 41 0a 48 8d 41 0e 0f b6 53 2f 80 ce 11 66 89 51 0c eb 0a 48 8d 41 0a 84 d2 74 02 <0f> 0b 0f b6 53 30 80 ce 12 66 89 10 0f b6 53 2c 80 ce 13 66 89 Oct 2 18:29:05 Icarus kernel: RIP [<ffffffffa008c634>] mv_qc_prep+0x147/0x1f2 [sata_mv] Oct 2 18:29:05 Icarus kernel: RSP <ffff88021a7cf868> Oct 2 18:29:05 Icarus kernel: ---[ end trace bf441de84c1a7ded ]--- Oct 2 18:29:05 Icarus kernel: note: scsi_eh_25[1149] exited with preempt_count 1 Oct 2 18:29:05 Icarus kernel: ------------[ cut here ]------------ Oct 2 18:29:05 Icarus kernel: WARNING: CPU: 1 PID: 1149 at kernel/smp.c:292 smp_call_function_single+0x81/0xef() Oct 2 18:29:05 Icarus kernel: Modules linked in: md_mod(-) w83627hf hwmon_vid k10temp sata_mv forcedeth sata_nv pata_amd acpi_cpufreq Oct 2 18:29:05 Icarus kernel: CPU: 1 PID: 1149 Comm: scsi_eh_25 Tainted: G D 4.1.7-unRAID #3 Oct 2 18:29:05 Icarus kernel: Hardware name: Supermicro H8DM8-2/H8DM8-2, BIOS 080014 10/22/2009 Oct 2 18:29:05 Icarus kernel: 0000000000000009 ffff88021a7cf478 ffffffff815eff9a 0000000000000000 Oct 2 18:29:05 Icarus kernel: 0000000000000000 ffff88021a7cf4b8 ffffffff810477cb ffff88011bc55ec0 Oct 2 18:29:05 Icarus kernel: ffffffff81092c4d ffff88011af41920 0000000000000001 0000000000000001 Oct 2 18:29:05 Icarus kernel: Call Trace: Oct 2 18:29:05 Icarus kernel: [<ffffffff815eff9a>] dump_stack+0x4c/0x6e Oct 2 18:29:05 Icarus kernel: [<ffffffff810477cb>] warn_slowpath_common+0x97/0xb1 Oct 2 18:29:05 Icarus kernel: [<ffffffff81092c4d>] ? smp_call_function_single+0x81/0xef Oct 2 18:29:05 Icarus kernel: [<ffffffff810a73c2>] ? perf_event_refresh+0x39/0x39 Oct 2 18:29:05 Icarus kernel: [<ffffffff81047879>] warn_slowpath_null+0x15/0x17 Oct 2 18:29:05 Icarus kernel: [<ffffffff81092c4d>] smp_call_function_single+0x81/0xef Oct 2 18:29:05 Icarus kernel: [<ffffffff810a5e9b>] task_function_call+0x44/0x4e Oct 2 18:29:05 Icarus kernel: [<ffffffff810ab285>] ? __perf_event_task_sched_out+0x35b/0x35b Oct 2 18:29:05 Icarus kernel: [<ffffffff810a74d8>] perf_cgroup_exit+0x19/0x1b Oct 2 18:29:05 Icarus kernel: [<ffffffff8109cd09>] cgroup_exit+0xa9/0xc8 Oct 2 18:29:05 Icarus kernel: [<ffffffff810497fc>] do_exit+0x3e0/0x8db Oct 2 18:29:05 Icarus kernel: [<ffffffff810789cc>] ? kmsg_dump+0xa7/0xb0 Oct 2 18:29:05 Icarus kernel: [<ffffffff8100e19b>] oops_end+0xb5/0xba Oct 2 18:29:05 Icarus kernel: [<ffffffff8100e2d4>] die+0x55/0x61 Oct 2 18:29:05 Icarus kernel: [<ffffffff8100b55e>] do_trap+0x66/0x11e Oct 2 18:29:05 Icarus kernel: [<ffffffff8100b6e0>] do_error_trap+0xca/0xdc Oct 2 18:29:05 Icarus kernel: [<ffffffffa008c634>] ? mv_qc_prep+0x147/0x1f2 [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffff81356e41>] ? put_dec+0x53/0x58 Oct 2 18:29:05 Icarus kernel: [<ffffffff8135819c>] ? number.isra.13+0x11e/0x216 Oct 2 18:29:05 Icarus kernel: [<ffffffff8106d55f>] ? pick_next_task_fair+0x106/0x41a Oct 2 18:29:05 Icarus kernel: [<ffffffff81357a38>] ? string.isra.3+0x3d/0xa4 Oct 2 18:29:05 Icarus kernel: [<ffffffff8100a49b>] ? __switch_to+0x43c/0x4c8 Oct 2 18:29:05 Icarus kernel: [<ffffffff8100bafe>] do_invalid_op+0x1b/0x1d Oct 2 18:29:05 Icarus kernel: [<ffffffff815f6a1e>] invalid_op+0x1e/0x30 Oct 2 18:29:05 Icarus kernel: [<ffffffffa008c634>] ? mv_qc_prep+0x147/0x1f2 [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d238>] ata_qc_issue+0x268/0x2c7 Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d515>] ata_exec_internal_sg+0x27e/0x478 Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d78d>] ata_exec_internal+0x7e/0x8b Oct 2 18:29:05 Icarus kernel: [<ffffffff810783f1>] ? vprintk_default+0x18/0x1a Oct 2 18:29:05 Icarus kernel: [<ffffffff81465f33>] ata_read_log_page+0xdf/0x11d Oct 2 18:29:05 Icarus kernel: [<ffffffff8145eb30>] ata_dev_configure+0x9ed/0xee3 Oct 2 18:29:05 Icarus kernel: [<ffffffff8145d7bf>] ? ata_do_dev_read_id+0x25/0x27 Oct 2 18:29:05 Icarus kernel: [<ffffffff814684b6>] ata_eh_recover+0x77f/0xf86 Oct 2 18:29:05 Icarus kernel: [<ffffffff8146b07d>] ? ata_sff_softreset+0x166/0x166 Oct 2 18:29:05 Icarus kernel: [<ffffffffa008d627>] ? mv5_reset_hc+0x10d/0x10d [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffffa008b731>] ? mv_pmp_hardreset+0x58/0x58 [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffff8146cb5c>] ? ata_bmdma_interrupt+0x184/0x184 Oct 2 18:29:05 Icarus kernel: [<ffffffff8146d65a>] sata_pmp_error_handler+0xfb/0x82d Oct 2 18:29:05 Icarus kernel: [<ffffffff81057498>] ? try_to_grab_pending+0x45/0x146 Oct 2 18:29:05 Icarus kernel: [<ffffffff81082a85>] ? lock_timer_base.isra.25+0x26/0x4a Oct 2 18:29:05 Icarus kernel: [<ffffffffa008ac88>] mv_pmp_error_handler+0x7b/0x84 [sata_mv] Oct 2 18:29:05 Icarus kernel: [<ffffffff81468f7e>] ata_scsi_port_error_handler+0x21b/0x55f Oct 2 18:29:05 Icarus kernel: [<ffffffff8146934e>] ata_scsi_error+0x8c/0xb7 Oct 2 18:29:05 Icarus kernel: [<ffffffff81448b30>] scsi_error_handler+0xac/0x4a0 Oct 2 18:29:05 Icarus kernel: [<ffffffff81448a84>] ? scsi_eh_get_sense+0xd4/0xd4 Oct 2 18:29:05 Icarus kernel: [<ffffffff81448a84>] ? scsi_eh_get_sense+0xd4/0xd4 Oct 2 18:29:05 Icarus kernel: [<ffffffff8105c792>] kthread+0xd6/0xde Oct 2 18:29:05 Icarus kernel: [<ffffffff8105c6bc>] ? kthread_create_on_node+0x172/0x172 Oct 2 18:29:05 Icarus kernel: [<ffffffff815f5a12>] ret_from_fork+0x42/0x70 Oct 2 18:29:05 Icarus kernel: [<ffffffff8105c6bc>] ? kthread_create_on_node+0x172/0x172 Oct 2 18:29:05 Icarus kernel: ---[ end trace bf441de84c1a7dee ]---

I tested them in another computer, pulled the data off one of them, the other failed to read the data. Bios sees the drives, tried them in different spots on my 24 bay server, Server is protected by a 1500w UPS. All i know is the server DOES NOT like these two drives. Either one of them, glad to know someone else had the same problem. lr5v did it work with another SSD? I am wondering if replacing the SSDs will work or if i should try to RMA them. they are 4 months old for crying out loud.

i agree 100% but i have no clue where to start to fix it. All i know is it works fine without them the second i put one in it crashes / will not boot.

Protip, change the bus to IDE from VIRTIO and delete the line <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

After installing windows on a VM disk it just sits at finalizing settings.... anyone got any pro tips?

Can i get any support at all?... this is kind of a big deal not being able to use ANY ssds SSD's are both 4 months old: Sandisk SDSSDA-240G SSD Plus

If you shutdown the array and plug in the SSD you get this... Also does this on boot if you remove #1 SSD.....

Weird ok thank you for the replies i will continue to troubleshoot now that i know my "data" is safe and its just the VM drives....

Was there a SSD bug introduced? As soon as i rebooted my server it will not boot with ANY ssd's installed. REF: http://lime-technology.com/forum/index.php?topic=43150.0

narrowed it down to my two VM SSD's..... Comes up now without those two... Obviously the array wont start but i can now get to the webgui... (missing too many drives)