RokleM

Looking forward to the upgrade form the 5.12 to 5.13 train. Personally, I'd love to see 5.13.9 so I can test (on this controller) some of the beta hardware.

Changed Status to Closed

I will however it is nearly 100% unlikely that a USB stick that has been 100% reliable for over 5 years somehow had an issue within seconds of clicking the upgrade button...The statistical improbability... There is something wrong with the update process, but hopefully other don't run into it.

Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot. Very odd.Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot. Very odd.

Changed Priority to Minor

Took a risk and rebooted and it's working... something in the upgrade process made the disk not accessible but somehow is restored during reboot. Very odd.

Re-created the flash disk in windows using the utility, copied the config directory over, same error.... Jan 12 11:54:37 nas root: cp: cannot create regular file '/boot/config': Input/output error Jan 12 11:54:37 nas kernel: FAT-fs (sda1): FAT read failed (blocknr 4913) Jan 12 11:54:38 nas kernel: usb 3-2: new high-speed USB device number 8 using xhci_hcd Jan 12 11:54:38 nas kernel: usb-storage 3-2:1.0: USB Mass Storage device detected Jan 12 11:54:38 nas kernel: scsi host11: usb-storage 3-2:1.0 Jan 12 11:54:38 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:54:38 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:54:39 nas kernel: scsi 11:0:0:0: Direct-Access SanDisk Cruzer Fit 1.27 PQ: 0 ANSI: 6 Jan 12 11:54:39 nas kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0 Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Write Protect is off Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Mode Sense: 43 00 00 00 Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:54:39 nas kernel: sdi: sdi1 Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:54:39 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:54:39 nas kernel: sd 11:0:0:0: [sdi] Attached SCSI removable disk Jan 12 11:54:39 nas root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: No such file or directory

can read in windows... Logs when I try to plug the disk in Jan 12 11:46:12 nas emhttpd: Starting services... Jan 12 11:46:12 nas emhttpd: shcmd (6546): /etc/rc.d/rc.samba restart Jan 12 11:46:12 nas root: cp: cannot create regular file '/boot/config': Input/output error Jan 12 11:46:12 nas kernel: FAT-fs (sda1): FAT read failed (blocknr 4913) Jan 12 11:46:12 nas kernel: usb 3-2: new high-speed USB device number 6 using xhci_hcd Jan 12 11:46:12 nas kernel: usb-storage 3-2:1.0: USB Mass Storage device detected Jan 12 11:46:12 nas kernel: scsi host11: usb-storage 3-2:1.0 Jan 12 11:46:12 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:46:12 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:46:13 nas kernel: scsi 11:0:0:0: Direct-Access SanDisk Cruzer Fit 1.27 PQ: 0 ANSI: 6 Jan 12 11:46:13 nas kernel: sd 11:0:0:0: Attached scsi generic sg0 type 0 Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] 31266816 512-byte logical blocks: (16.0 GB/14.9 GiB) Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Write Protect is off Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Mode Sense: 43 00 00 00 Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:46:13 nas kernel: sdi: sdi1 Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read data cache entry [89a6c4] Jan 12 11:46:13 nas kernel: SQUASHFS error: Unable to read page, block 89a6c4, size 3840 Jan 12 11:46:13 nas kernel: sd 11:0:0:0: [sdi] Attached SCSI removable disk Jan 12 11:46:14 nas root: /etc/rc.d/rc.samba: line 25: /boot/config/machine-id: No such file or directory Jan 12 11:46:14 nas root: cp: cannot stat '/boot/config/machine-id': No such file or directory Jan 12 11:46:14 nas root: Starting Samba: /usr/sbin/smbd -D Jan 12 11:46:14 nas root: /usr/sbin/nmbd -D

Literally never had a problem with that disk for 5 years until I started this upgrade. The sever will no longer see it but it works fine in windows. Jan 12 11:10:40 nas emhttpd: req (8): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=unRAIDServer.plg&csrf_token=**************** Jan 12 11:10:40 nas emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Jan 12 11:10:40 nas root: plugin: running: /tmp/unRAIDServer.sh Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Jan 12 11:10:49 nas root: plugin: running: /tmp/unRAIDServer.sh Jan 12 11:11:00 nas kernel: usb 5-1: USB disconnect, device number 2

Looks like the USB "disconnected" right at upgrade time, which makes no sense as it was working perfect for probably 5 years. I remove / re-insert and nothing shows up in /boot. It works in my windows machine. Jan 12 11:10:40 nas emhttpd: req (8): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=unRAIDServer.plg&csrf_token=**************** Jan 12 11:10:40 nas emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update unRAIDServer.plg Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Jan 12 11:10:40 nas root: plugin: running: /tmp/unRAIDServer.sh Jan 12 11:10:40 nas root: plugin: creating: /tmp/unRAIDServer.zip - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.md5 - downloading from URL https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 Jan 12 11:10:49 nas root: plugin: creating: /tmp/unRAIDServer.sh - from INLINE content Jan 12 11:10:49 nas root: plugin: running: /tmp/unRAIDServer.sh Jan 12 11:11:00 nas kernel: usb 5-1: USB disconnect, device number 2 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9830280 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9830520 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9830760 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831000 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831240 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831480 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831720 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9831960 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9832200 Jan 12 11:11:00 nas kernel: print_req_error: I/O error, dev sda, sector 9832440 Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4789, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4790, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4791, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4792, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4793, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4794, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4795, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4796, lost async page write Jan 12 11:11:00 nas kernel: Buffer I/O error on dev sda1, logical block 4797, lost async page write Jan 12 11:11:00 nas rc.diskinfo[23443]: SIGHUP received, forcing refresh of disks info. Jan 12 11:11:00 nas kernel: ------------[ cut here ]------------ Jan 12 11:11:00 nas kernel: bdi-block not registered Jan 12 11:11:00 nas kernel: WARNING: CPU: 8 PID: 24973 at fs/fs-writeback.c:2239 __mark_inode_dirty+0x151/0x1d5 Jan 12 11:11:00 nas kernel: Modules linked in: macvlan xt_nat xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap veth ipt_MASQUERADE iptable_filter iptable_nat nf _nat_ipv4 nf_nat ip_tables xfs md_mod nct6775 hwmon_vid k10temp bonding r8169 realtek edac_mce_amd kvm_amd kvm mpt3sas crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel ahci aes_x86_64 i2c_piix4 crypto_simd i2c_ core cryptd ccp libahci raid_class wmi_bmof glue_helper scsi_transport_sas nvme button pcc_cpufreq acpi_cpufreq nvme_core wmi [last unloaded: realtek] Jan 12 11:11:00 nas kernel: CPU: 8 PID: 24973 Comm: unzip Not tainted 4.19.88-Unraid #1 Jan 12 11:11:00 nas kernel: Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS (WI-FI), BIOS 1405 11/19/2019 Jan 12 11:11:00 nas kernel: RIP: 0010:__mark_inode_dirty+0x151/0x1d5 Jan 12 11:11:00 nas kernel: Code: ef e7 ff ff 49 89 c4 48 8b 00 f6 40 3c 02 75 1c 49 8b 54 24 08 80 e2 01 75 12 48 8b 70 30 48 c7 c7 b5 da d4 81 e8 fd db ed ff <0f> 0b 48 8b 05 94 2c c9 00 45 85 ed 48 89 85 c0 00 00 00 74 0e 48 Jan 12 11:11:00 nas kernel: RSP: 0018:ffffc9000f043d78 EFLAGS: 00010286 Jan 12 11:11:00 nas kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000007 Jan 12 11:11:00 nas kernel: RDX: 0000000000000519 RSI: 0000000000000002 RDI: ffff889f9e8164f0 Jan 12 11:11:00 nas kernel: RBP: ffff889f5b34f6a8 R08: 0000000000000003 R09: 0000000000019a00 Jan 12 11:11:00 nas kernel: R10: 0000000000000000 R11: 0000000000000038 R12: ffff889f9468b858 Jan 12 11:11:00 nas kernel: R13: 0000000000000000 R14: ffff889f5b34f728 R15: 0000000000000000 Jan 12 11:11:00 nas kernel: FS: 000014ab42f2c740(0000) GS:ffff889f9e800000(0000) knlGS:0000000000000000 Jan 12 11:11:00 nas kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 12 11:11:00 nas kernel: CR2: 0000150a58b20899 CR3: 0000001eebd56000 CR4: 0000000000340ee0 Jan 12 11:11:00 nas kernel: Call Trace: Jan 12 11:11:00 nas kernel: fat_setattr+0x1fc/0x20f Jan 12 11:11:00 nas kernel: notify_change+0x269/0x352 Jan 12 11:11:00 nas kernel: utimes_common+0x12c/0x190 Jan 12 11:11:00 nas kernel: do_utimes+0xf6/0x136 Jan 12 11:11:00 nas kernel: __se_sys_utime+0x77/0x8e Jan 12 11:11:00 nas kernel: do_syscall_64+0x57/0xf2 Jan 12 11:11:00 nas kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 12 11:11:00 nas kernel: RIP: 0033:0x14ab43034d77 Jan 12 11:11:00 nas kernel: Code: 48 89 ef b8 35 01 00 00 0f 05 48 89 c2 48 3d 00 f0 ff ff 77 c9 48 83 c4 08 5d 41 5c c3 66 0f 1f 44 00 00 b8 84 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e9 90 0d 00 f7 d8 64 89 01 48 Jan 12 11:11:00 nas kernel: RSP: 002b:00007ffe88ee3f78 EFLAGS: 00000297 ORIG_RAX: 0000000000000084 Jan 12 11:11:00 nas kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014ab43034d77 Jan 12 11:11:00 nas kernel: RDX: 0000000000000000 RSI: 00007ffe88ee3fa0 RDI: 000000000051d6b8 Jan 12 11:11:00 nas kernel: RBP: 0000000000000002 R08: 000000000052004a R09: 0000000000000000 Jan 12 11:11:00 nas kernel: R10: 00007ffe88ee35e0 R11: 0000000000000297 R12: 0000000000000000 Jan 12 11:11:00 nas kernel: R13: 000000000042674b R14: 0000000000000000 R15: 00007ffe88ee40d0 Jan 12 11:11:00 nas kernel: ---[ end trace 330187821b978133 ]--- Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732312) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732313) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732314) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732315) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732316) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732317) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732318) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732319) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732320) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): Directory bread(block 9732321) failed Jan 12 11:11:00 nas kernel: FAT-fs (sda1): FAT read failed (blocknr 4913)

My Dockers are also now down after the failed upgrade: Warning: parse_ini_file(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 Warning: array_replace_recursive(): Expected parameter 2 to be an array, bool given in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 43 And my VM's: Warning: parse_ini_file(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460 root@nas:/boot# ls -alh total 8.0K drwx------ 10 root root 8.0K Jan 12 11:10 ./ drwxr-xr-x 20 root root 440 Jan 11 19:47 ../

First upgrade failure I think ever... my other server worked. plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 ... done writing flash device - please wait... Archive: /tmp/unRAIDServer.zip plugin: run failed: /bin/bash retval: 1

Good question I'm having a hard time finding an official answer to It seems some have got it to work.

Hello all, maybe I'm missing it, but anyway to add local host entries? There are plenty of ways to add local DNS lookup (need to resolve *nix boxes and other that don't do netbios) when running on a full VM/host, but not finding a way to do this in an unraid docker.

Seems unraid OS sees the card, but do not appear to be able to use it via the GUI. <node id="network" class="network" handle="PCI:0000:02:00.0"> <description>Ethernet controller</description> <product>TN9510 10GBase-T/NBASE-T Ethernet Adapter</product> <vendor>Tehuti Networks Ltd.</vendor> <physid>0</physid> <businfo>pci@0000:02:00.0</businfo> <version>00</version> <width units="bits">64</width> <clock units="Hz">33000000</clock> <configuration> <setting id="latency" value="0" /> </configuration> <capabilities> <capability id="msi" >Message Signalled Interrupts</capability> <capability id="pm" >Power Management</capability> <capability id="pciexpress" >PCI Express</capability> <capability id="bus_master" >bus mastering</capability> <capability id="cap_list" >PCI capabilities listing</capability> </capabilities> <resources> <resource type="memory" value="f0100000-f010ffff" /> </resources> </node> <node id="network" claimed="true" class="network" handle="PCI:0000:05:00.0"> <description>Ethernet interface</description> <product>RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller</product> <vendor>Realtek Semiconductor Co., Ltd.</vendor> <physid>0</physid> <businfo>pci@0000:05:00.0</businfo> <logicalname>eth0</logicalname> <version>06</version> <serial>[REMOVED]</serial> <size units="bit/s">1000000000</size> <capacity>1000000000</capacity> <width units="bits">64</width> <clock units="Hz">33000000</clock> <configuration> <setting id="autonegotiation" value="on" /> <setting id="broadcast" value="yes" /> <setting id="driver" value="r8169" /> <setting id="driverversion" value="2.3LK-NAPI" /> <setting id="duplex" value="full" /> <setting id="firmware" value="rtl8168e-3_0.0.4 03/27/12" /> <setting id="latency" value="0" /> <setting id="link" value="yes" /> <setting id="multicast" value="yes" /> <setting id="port" value="MII" /> <setting id="slave" value="yes" /> <setting id="speed" value="1Gbit/s" /> </configuration> <capabilities> <capability id="pm" >Power Management</capability> <capability id="msi" >Message Signalled Interrupts</capability> <capability id="pciexpress" >PCI Express</capability> <capability id="msix" >MSI-X</capability> <capability id="vpd" >Vital Product Data</capability> <capability id="bus_master" >bus mastering</capability> <capability id="cap_list" >PCI capabilities listing</capability> <capability id="ethernet" /> <capability id="physical" >Physical interface</capability> <capability id="tp" >twisted pair</capability> <capability id="mii" >Media Independant Interface</capability> <capability id="10bt" >10Mbit/s</capability> <capability id="10bt-fd" >10Mbit/s (full duplex)</capability> <capability id="100bt" >100Mbit/s</capability> <capability id="100bt-fd" >100Mbit/s (full duplex)</capability> <capability id="1000bt" >1Gbit/s</capability> <capability id="1000bt-fd" >1Gbit/s (full duplex)</capability> <capability id="autonegotiation" >Auto-negotiation</capability> </capabilities> <resources> <resource type="irq" value="42" /> <resource type="ioport" value="d000(size=256)" /> <resource type="memory" value="f0004000-f0004fff" /> <resource type="memory" value="f0000000-f0003fff" /> </resources> </node>

Thanks for the feedback guys/gals. Seems like there are some deficiencies IMO, but in general it appears most believe things are working.

Well not sure if things will work out, but made some decisions and proceeding... Guess no further feedback is required at this point.

I've come back after a couple year hiatus and am looking at building a new box. I've been browsing around the forums and things are... different. 1) It seems many sections have turned overly hostile and "go google it", "go search for it" type of answers. 2) The actual technical sections seem to be heavily abandoned. 3) Hardware suggestion sections have volumes of posts with little to no assistance / responses, or maybe a quick minor attempt from one or two individuals and then silence. Even seemingly simple questions from people are ignored. 4) It appears (from a general view), the most commonly viewed and participated areas are actually just related to unraid and not unraid itself. It doesn't seem like the product is dead, but it appears that the community mentality has changed quite a bit and isn't actually focused on one of the main reasons the forum exists.

Another alternative... I'm probably going to replace my gaming rig, which while older, is quite a bit of beast and actually has more umph than the i5-7500 I posted (and that's without the healthy stable 4.4 GHz overclock it typically runs)... I guess much of this going back to the case and, if things can be sandwiched in, if I should replace the Norco, and what to do about add-on SATA ports. I wish there were more good reviews of the case.

Some possibilities? Not knowing what I want to do processor / VM / Docker / etc wise, hard to tell which would be logical. Price jump is pretty huge. Also 1x8g, can add another 1x8g later if I determine it's needed. Board is smaller and will fit well, has m.2, 6 ports for initial support, relatively lower power usage, etc. Use current SATA card, use different? Compatible?

Current setup: Old tower case with 2x 4-in-3 Norco cages (aftermarket fans) (SS-400 I think ???) Supermicro X8SIL-F i5 750 @ 2.67GHz 4g RAM 5x 3-4TB drives that should be slowly replaced Old 2TB junk cache disk sy-pex40039 (2 port SATA card) Corsair CX430 Goal: Get the current one off the floor. It does a GREAT job at collecting dust, getting kicked, and everything else. I'm a network engineer by hobby and profession (40 years old with 25y in the field, do the math), and have a wall mounted 19" short depth cabinet next to my desk, which also has a Thermaltake wall mounted PC next to it. Cabinet is only 13" deep, but know this will NOT hold any decent 19" case what so ever. I can / will replace with an adjustable frame rack (star tech RK812WALLOA, 20" depth MAX). I have QNAP's for DVR (HDHomeRun), so the primary use is backup of computers, movie storage, etc. VM / Docker / KVM would be nice, some unix distro's for logging, perl scripts, testing, etc. It is however not a KEY factor, a nice to have, and if run would not likely be incredibly intensive. I would like to host some internal games for the kids via Steam client, however that currently is most 32 bit supported in Unix, which makes it quite difficult on this platform. So point here is: Storage primary, VM's nice to have. Price, not looking to spend a fortune. As flexible as unraid is, and I love it, if price gets out of hand there is no reason not to go buy a QNAP instead. Keep the suggestions within reason guys. 10g network (eventually) would be nice, or at least an option (already have PCI-E N-Base 1g/2.5g/5g/10g card) Headless / KVMless is NEARLY a must. If I HAVE to absolutely plug something in I will, but this honestly is pretty stupid with any modern computer to even require a monitor and keyboard anymore in a USB world. Manufactures that do this need to be beaten. BONUS POINTS: KVM / ILO / OOB / IDRAC / EIEIO / etc over IP. I do have some spare M.2 chips that could be used (for example, possible great replacement for cache disk), so if supported that would be cool. Hardware so far: Cases, this has been the biggest PAIN so far. Remember sort depth wall mounted rack... Norco RPC-4308 - Good: Cool little case, 8 drives, plenty of motherboard space Bad: Price, and ZERO drive cooling (of all vendors to not understand importance of drive cooling) Verdict: Probably pass Chenbro rm42300-f Good: Price is excellent. Layout looks really good, ability for me to (maybe) re-use my Norco units Bad: I really don't think I can get my current board, or another good sized full board, into this case with the 8.5" deep Norco units. Reviews with this combination, I have not been able to find Verdict: Think this is the one, but maybe limits me to Micro or Mini boards instead of full sized Board? Intel preferred, m.2 capabilities a bonus CPU? Intel preferred RAM? You tell me. Need probably at lest a couple of gig for UnRaid, if VM/KVM/Docker, sounds like 16+ would be nice, but with RAM prices being stupid, again the build has to support something cost effective Drives, import old for now. Possibly looking at a few new 6-10TB drives. Support for at least the 8 bays I have would be ideal, 12 better (there are internal areas for drives in the above case too) 4-in-3 Norco cages (aftermarket fans) (SS-400 I think ???). I'm pretty fond of these, so wouldn't mind re-using if possible unless there is a compelling reason to replace. For example if a shorter depth cage would allow a full sized board that is absolutely critical for the build and worth the change, I would consider. Power Supply - Reuse Corsair CX-430 if possible, if not, replace with

Copied bzroot, bzimage, make_boot, and syslinux over. Then did a make bootable and it appears to have worked.

Followed step 1. Could not find kernel image: linux boot: Make Bootable v1.2 Volume in drive E is UNRAID Volume Serial Number is asdf Press any key to continue . . . E:\syslinux\syslinux.exe -maf E: The system cannot find the path specified. Completed Press any key to continue . . .

Something I should keep an eye on? Was going to make this one the parity becuase of the speed...