morbidpete

Members
  • Posts

    142
  • Joined

  • Last visited

Everything posted by morbidpete

  1. When I initially installed the i5, PC wouldn't even boot. I then found that my bios was at F5, I installed the i3 and updated to F9. after rebooting to verify everything worked. Then switched to the i5 and found this issue.
  2. BTW, System specs Unraid 6.0-beta14b Model: Custom System: Gigabyte Technology Co., Ltd. - Z87X-UD3H-CF Flash GUID: 0781-5530-2908-130F11007ABA CPU: Intel® Core™ i3-4130 CPU @ 3.40GHz Cache: 128 kB, 512 kB, 3072 kB Memory: 8192 MB (max. installable capacity 32 GB) Network: eth0: 1000Mb/s - Full Duplex Xen Version: 4.4.1 Dom0 Kernel: Linux 3.18.5-unRAID x86_64 OpenSSL: 1.0.1k Uptime: 12:05:47 00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation Device 041e (rev 06) 00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation Lynx Point USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation Lynx Point MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04) 00:1a.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #1 (rev d4) 00:1c.4 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #5 (rev d4) 00:1c.5 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #6 (rev d4) 00:1d.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation Lynx Point LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation Lynx Point SMBus Controller (rev 04) 01:00.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba) 01:00.1 System peripheral: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba) 02:01.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba) 02:05.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba) 02:07.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba) 02:09.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba) 03:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 640 4 Port SATA-III Controller (rev 01) 04:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 640 4 Port SATA-III Controller (rev 01) 07:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41) 09:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 11) [0:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sda [1:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sdb [2:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sdc [3:0:0:0] disk ATA WDC WD2003FYYS-0 1D01 /dev/sdd [4:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sde [5:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sdf [6:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sdg [7:0:0:0] disk ATA WDC WD2003FYYS-0 1D01 /dev/sdh [8:0:0:0] disk SanDisk Cruzer 1.26 /dev/sdi [9:0:0:0] disk ATA WDC WD2000F9YZ-0 1A01 /dev/sdj [10:0:0:0] disk ATA WDC WD5000AZRX-0 1A01 /dev/sdk [11:0:0:0] disk ATA ST31000524AS JC4A /dev/sdl [12:0:0:0] disk ATA WDC WD1002FBYS-1 0C09 /dev/sdm Bus 004 Device 002: ID 8087:8000 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 045b:0210 Hitachi, Ltd Bus 002 Device 002: ID 045b:0210 Hitachi, Ltd Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0781:5530 SanDisk Corp. Cruzer Bus 001 Device 002: ID 045b:0209 Hitachi, Ltd Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 006: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 003: ID 045b:0209 Hitachi, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  3. Agreed, get a full smart reports. Also just for safe measure. With the 5tb Parity drive in place. and all the old drives in place. Run another parity check with error correction just to be on the safe side.
  4. Gigabyte Technology Co., Ltd. - Z87X-UD3H-CF v1 I wanted to blame the cables or something. But it has been running all night with no issues on the i3, After tons of googling and checking this forums. Only lead I can find is that VT-D messes with Xen and I am running a VM. I am going to try the work around and home it works. Or even boots (i'm at work right now) EDIT: Cant try it, Cant put the i5 back in while I am at work now can I :-P Will have to wait until I get home lol but for reference. going to try this https://lime-technology.com/forum/index.php?topic=33511.msg308869#msg308869
  5. Hello! So my i3- was not keeping up with transcoding. So I grabbed an i5-4690k. Server booted, noticed a bunch of errors in the boot. ata3.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) no idea why. I updated my bios as i was 5 versions behind. same issue. cleared the bios to defaults, same issue. tried sata controller as raid,ide and ahci. no change. Drives on the PCI-E card are showing up fine, all drives show in the bios no issue. its only unraid that wont see them. any ideas? I am currently running back on the i-3 just fine. boots without issue
  6. I'm using Xen, I am very familiar with using vmware esxi as I currently have 5 guests on an HP g6 host. I do not want to do nic teaming. I want each nic to show to the guest as 2 different nic's -Pete #KCCO
  7. So my Mobo currently has 1 NIC. If I add a PCI-e card to add another nic, will I be able to creat another bridge for that nic and assign a VM to just that nic? What if I wanted said VM to attach to both nic's. Is that possible? -Pete #KCCO
  8. Plex messed up the release. Tons of people having issues with it. they are aware and working on a new release
  9. I just wanted to thank you for this, working beautifully for my HPT 640 on 5.0!