morbidpete Posted April 13, 2015 Share Posted April 13, 2015 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 Link to comment
garycase Posted April 13, 2015 Share Posted April 13, 2015 What motherboard do you have [Exact make/model and revision #] ?? Link to comment
morbidpete Posted April 13, 2015 Author Share Posted April 13, 2015 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 Link to comment
morbidpete Posted April 13, 2015 Author Share Posted April 13, 2015 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 Link to comment
garycase Posted April 13, 2015 Share Posted April 13, 2015 Did you do the BIOS update with the i3 installed? The i5-4690k requires BIOS F9 to be supported by your motherboard ... but if you had a version before that you should NOT do the update with the unsupported CPU installed. If that's what you did, I'd rerun the BIOS update with the i3 installed before switching back to the i5. Link to comment
morbidpete Posted April 13, 2015 Author Share Posted April 13, 2015 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. Link to comment
morbidpete Posted April 15, 2015 Author Share Posted April 15, 2015 Holding off on this CPU swap. I have 3 1TB drives I'm replacing with 4TB drives. I rather not mess around during parity and data rebuilds. Keeping the stable system until the upgrade is compete. Then I will mess around with it. Link to comment
morbidpete Posted April 16, 2015 Author Share Posted April 16, 2015 So an update. Messed with it today after the data rebuild. Threw the i5 in. Disabled Intel VT-D. Was expecting my zen VM to not start. This test was recommended by the thread I mentioned above. All the drives showed up AND my VM started with no issue. So I'm leaving it as is. Running great. Hope this helps someone in the future. Link to comment
garycase Posted April 16, 2015 Share Posted April 16, 2015 Interesting ... and it may simply be that there's an interaction with vt-d that needs to be avoided. But just to be certain nothing else changed along the way I'd re-enable vt-d and confirm that the problem returns ... and if it does, then disable it. Of course if you're certain you won't need to pass through any devices to your VM's, you can simply leave everything as is ... but I'd still think it'd be nice to know for sure whether or not that's the issue. Link to comment
morbidpete Posted April 16, 2015 Author Share Posted April 16, 2015 Interesting ... and it may simply be that there's an interaction with vt-d that needs to be avoided. But just to be certain nothing else changed along the way I'd re-enable vt-d and confirm that the problem returns ... and if it does, then disable it. Of course if you're certain you won't need to pass through any devices to your VM's, you can simply leave everything as is ... but I'd still think it'd be nice to know for sure whether or not that's the issue. Good idea, I'll turn it back on in the morning and see what happens. To many people use my plex at night. Dont want to cut them all off. All the Vm does is run win 8.1, MediaCenterMaster and utorrent. So I dont pass anything into it. Plus side, Vm runs a ton better with the SSD and new CPU. Just waiting for my new ram to show up! Ill post results tomorrow Link to comment
morbidpete Posted April 16, 2015 Author Share Posted April 16, 2015 All drives are good to go. Shit down server. Enabled VT-D. Same errors, came Sara ports even with different drives. Tried RAID, IDE and ACHI. Dame effect. Disabled intels storage controller crap also. Same issue. Disabled VT-D. Everything is working well again. Link to comment
garycase Posted April 16, 2015 Share Posted April 16, 2015 As you've already confirmed, the lack of vt-d is not an issue for your application ... so all's well. And you've confirmed that this was indeed the issue, so there's no "guesswork" about just what was causing it. I've seen a few other setups that required disabling vt-d as well ... not sure just what the set of circumstances is that requires this; but clearly there is some interaction between this feature and some chipsets. Link to comment
RobJ Posted April 16, 2015 Share Posted April 16, 2015 Probably your only hope is to watch for another BIOS update. Let them hear from you, so they know there's at least one user with that issue and that motherboard. If they hear from enough ... Link to comment
morbidpete Posted April 16, 2015 Author Share Posted April 16, 2015 Probably your only hope is to watch for another BIOS update. Let them hear from you, so they know there's at least one user with that issue and that motherboard. If they hear from enough ... When you say they. Do you mean Lime tech or Gigabyte? I upgraded to the 10b bios also. Forgto to mention that. same issue. I noticed it added better support for xxxxk CPU's so thought it might help since i have a 4690k. no luck. Link to comment
morbidpete Posted April 16, 2015 Author Share Posted April 16, 2015 A bit more info as I look into this because I hate not knowing why things dont work. The i3-4130 did not have VT-D support. So it was never an issue. The i3 has VT-x. the i5 has VT-D along with VT-x. so that explains why the change all of a sudden. Now to really figure out why xen hates VT-D Link to comment
CHBMB Posted April 16, 2015 Share Posted April 16, 2015 A bit more info as I look into this because I hate not knowing why things dont work. The i3-4130 did not have VT-D support. So it was never an issue. The i3 has VT-x. the i5 has VT-D along with VT-x. so that explains why the change all of a sudden. Now to really figure out why xen hates VT-D Tried KVM? Link to comment
morbidpete Posted April 17, 2015 Author Share Posted April 17, 2015 A bit more info as I look into this because I hate not knowing why things dont work. The i3-4130 did not have VT-D support. So it was never an issue. The i3 has VT-x. the i5 has VT-D along with VT-x. so that explains why the change all of a sudden. Now to really figure out why xen hates VT-D Tried KVM? Once beta 15 drops I will Link to comment
garycase Posted April 18, 2015 Share Posted April 18, 2015 I had the same thought r.e. KVM => let us know if that makes a difference. It would be nice to have pass-through available as an option. Link to comment
garycase Posted April 18, 2015 Share Posted April 18, 2015 FWIW, I was reading the details on Xen vs. KVM vis-à-vis UnRAID support for these; and apparently KVM explicitly supports vt-d pass-through, whereas Xen does not. Sounds like there's a very good chance that with KVM you'll be able to turn on vt-d and then be able to use pass-through for your devices. May or my not be a meaningful capability for your specific uses; but certainly nice to have that feature available. Let us know if you get a chance to confirm that's in fact the case with your specific hardware configuration. Link to comment
morbidpete Posted April 20, 2015 Author Share Posted April 20, 2015 FWIW, I was reading the details on Xen vs. KVM vis-à-vis UnRAID support for these; and apparently KVM explicitly supports vt-d pass-through, whereas Xen does not. Sounds like there's a very good chance that with KVM you'll be able to turn on vt-d and then be able to use pass-through for your devices. May or my not be a meaningful capability for your specific uses; but certainly nice to have that feature available. Let us know if you get a chance to confirm that's in fact the case with your specific hardware configuration. I'll be working on the conversion tonight. going to use acronis to do it, dont want to set up all my apps again! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.