Jump to content

zodde

Members
  • Content Count

    37
  • Joined

  • Last visited

Community Reputation

0 Neutral

About zodde

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well done! Nice to see people doing this succesfully. I am in this thread becuse i was looking for information nice in handy when my LSI card arrived, got a 9200 8i on ebay, and went with a NON pre flashed cuz i thought that i wanted to do my self, and when it arrived i plugged it in and booted up into LSI Utility to check. Turned out it was allready with IT firmware. Probably a old one but Unraid finds the drives and it workes great. Some day i will look into the versions of fw and se if i update it. But afraid to mess up in some way now instead Great job !
  2. I posted some weeks ago that i waited for my LSI card and said that i was gonna update how it went with it. The LSI card is now in the machine, actully it was allready in IT mode firmware. I orderd a card without any descripten whit "FREENAS- UNRAID - ZFS READY" becuse i thought that i wanted to exprimentet with that part my self. But i got a flashed anyway. No worries, kind of nice to just plugg it in and start without any problems for once. So now the LSI take cares of 8 drives to the array and the sata ports are to ssds, 2 SSDs are plugged in and 2 m.2 NVME and it runs really good actully. This was a good expansion to the main build. The card is IBM LSI not sure what the model no are but i remember that the firmware was 10 something, and i guess that is a old fw but it works without any problems.
  3. The issues are located and fixed. The first issue was that the server went to some kind of C-State, when that was fixed it stopped responding random, every time i didnt used the server it did not respond when i was gonna use it again. And also, it could stop responding when i was watching a movie with my kids, just like that. Turns out the m.2 drives i use as cache caused this, now with one Samsung 970 EVO PLUS it runs again, I have one more to put in and run the cache in a raid 1 pool. Problem solved!
  4. This have happend to me aswell, i have been looking for the problem for weeks, and today i saw your old post and got me thinking, i have 2 x WD SN500 in my unraid build, but those uses wd in house controller but they might cause issues aswell, i have now put in another 2.5" insted of the 2 m.2 and for 24 h it havent crashed yet so the problem might be found. Did you figure out your issue?
  5. Forgot that one node-diagnostics-20191202-0013.zip
  6. I have now tried to put my finger on why the server stops responding suddenly for several weeks, the motherboard is replaced as hardware problems were to be expected. The card is a server motherboard, asus p11c-m / 4l for information purposes. The server both spins and lights off the fans but does not respond to ping, nor keyboard so the screen can respond. Could this be the BIOS setup problem? The BIOS is for me advanced with some things I don't understand even after searching (several different forms of C-State, under the power management section. Also, since I don't have the screen in front of me, I can't mention more choices that I don't understand right now, but when it's set to deafult, nothing should usually be noticeably wrong. During the CPU section everything looks okay. In the logs I can see strange behavior but I can't be wise exactly when it locks. All help and ideas are sparked. I run out of ideas. syslog-1 syslog-192.168.0.110-1.log
  7. Absolutly! Delivery is 12-26 dec. And right after that i will report. I got all i need so it should go well
  8. Hi! I had some issues with my server that stops responding, i thought hardware problem, like many other in here, i got a new MB from ASUS sent to me and i started it up and everything worked fine, exept some no respond the last days but it have been long time between, today it had run plex for the kids all day and everything worked like it supposed to, and then it died, i have syslogg server and have checked the logg, 00.24 i looked at the clock to check the time, and i cold reset. Any Unraid master on loggs that can help me check the logg and see if there is anything major error? Please help me out and let this nightmare of a new build server end..:S syslog(1) is from the flashdrive, and syslog-192.168... is from the cachedrives folder, i dont know why the loggs is different to eachother.. Why does the server just goes down like this? syslog(1) syslog-192.168.0.110.log
  9. Good thinking there. But all can be lernd and figure out. I had and it workes. Thanks, it will be all good as soon as the card is here
  10. I have read alot in here and couldent figure out witch of the all post i should go with, got help in email so when the card is here i know what to do.
  11. So i jumped on the train and bought my self a LSI 9200 8i, and it is not pre flashed with IT mode fw. I have been reading about it to get some kind of knowlage how to do it when it arrives, but it cant hurt to ask in here aswell if anyone have any good guide or just read in this thread and follow a little here and a little there and hope for the best? But if anyone knows or have a how to do list or a website with information is more then welcome to tell me and help me out. Thanks
  12. Hi! I have 4 LANs on the server but i only get one (eth0) in unraid, How can that be? In BIOS all 4 is shown. I post diagnostic. System device is: IOMMU group 0:[8086:3ec6] 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) IOMMU group 1:[8086:1911] 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model IOMMU group 2:[8086:a379] 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) IOMMU group 3:[8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) [8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) IOMMU group 4:[8086:a368] 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10) [8086:a369] 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10) IOMMU group 5:[8086:a360] 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) [8086:a364] 00:16.4 Communication controller: Intel Corporation Device a364 (rev 10) IOMMU group 6:[8086:a352] 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) IOMMU group 7:[8086:a32c] 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0) IOMMU group 8:[8086:a32d] 00:1b.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #22 (rev f0) IOMMU group 9:[8086:a32e] 00:1b.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #23 (rev f0) IOMMU group 10:[8086:a32f] 00:1b.7 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #24 (rev f0) IOMMU group 11:[8086:a338] 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) IOMMU group 12:[8086:a330] 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) IOMMU group 13:[8086:a332] 00:1d.2 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #11 (rev f0) IOMMU group 14:[8086:a328] 00:1e.0 Communication controller: Intel Corporation Device a328 (rev 10) IOMMU group 15:[8086:a30a] 00:1f.0 ISA bridge: Intel Corporation Device a30a (rev 10) [8086:a323] 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) [8086:a324] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) IOMMU group 16:[8086:1533] 01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 17:[8086:1533] 02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 18:[8086:1533] 03:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 19:[8086:1533] 04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 20:[1a03:1150] 05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04) [1a03:2000] 06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41) IOMMU group 21:[15b7:5003] 07:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN520 NVMe SSD (rev 01) IOMMU group 22:[15b7:5003] 08:00.0 Non-Volatile memory controller: Sandisk Corp WD Black 2018/PC SN520 NVMe SSD (rev 01) node-diagnostics-20191119-1816.zip
  13. IT`S ALIVE! I mixed with BIOS, plugged a cabel into all of the ports, recreated a usb, and started. It actully got an IP. I have to be something with the new BIOS that was released yesterday, and after update, i didnt tryed UnRAID again, i started up FreeNAS cuz i was so tired of fighting with this. Today it all clear up! Iam a verry happy man once again. My second UnRAID machine is back up, just start over with array and set it up but thats no issue. The machine will actully be what the thought was when i bought all the parts and designed it. Amazing! Thanks to ya all! BIG THUMBS UP!
  14. Post some pictures aswell so you can see what i get in the same time that i remember as unraid didnt get a ip anymore. I had many small problems and dont remember to 100 % what en when it all happend, what camed first and what camed second as problem. FreeNAS and Windows both works, not unraid. Re-created usb. changed usb port, set default settings in BIOS.
  15. I having some issues in the boot with Intel Boot Agent that have been changed since i build the machine 2 weeks ago. Intel Boot Agent says PXE-05 NVM file is corrupted or have not been configuerd. What i remember this happend when i updated the BIOS and after that Unraid didnt give me an IP anymore, and since i had issues with UnRaid with stability i troubelshoot it and afteter many nights with that i decided to reinstall and start fresh, that didnt go well. But Intel Boot Agent dont have ANYTHING with this to do right? When i first build the machine in the boot, the CPU and memory etc showed up like it should, and after that there was a screen with text something like, Intel Boot Agent v1.5 etc etc and a / that spinned around and under that a quick text with Press CTRL + S to configure (It shown for like a sec) and then disaperd and then it booted up. Is this just a coincidence that the Intel Boot Agent got corrupted and Unraid got more errors or does it have a connection with eachother? I have been in touch with ASUS Server support since it it a ASUS P11 server MB and they have said the MB is defective, but other OS works to get IP etc but not UnRaid. a.t.m I have FreeNAS on a device in the machine cuz i got tired to fight with this, but i dont want to run FreeNAS, i want to run UnRaid on this machine as well 🙂 I will plugg in the monitor to the machine once again today and see, but i have tryed EVERYTHING that i can think of. I will plugg in ethernet cabel in all 5 Lan ports and see. But if it dosent give me an IP this time, then what ? Thanks for the support to all, i hope there is someone that can spare some time today and help me figure this out.