Ghostearror

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by Ghostearror

  1. My frustration level is at its breaking point. I've tried everything I can think of and I just can't figure out why unraid won't get an ip address. My only recourse at this point is to put all the old hardware back together and restore the flash drive. At least then I can get the server back up while I troubleshoot the new hardware.

  2. I was finally able to get the syslog.  I put the new NIC in and still no address.  My thinking is there is something in my bios that needs adjusting, because this board has a mix of 3.1, 3.0, 2.0 ports.  I have the flash plugged into a 2.0 port, and when anything else is plugged into the 3.1 or 3.0 ports the system won't boot.  I'm hoping one of you gurus can read the log and tell me what the heck is going on.  Thanks for everyones assistance on this. 

    syslog.txt

  3. I'll check, but if it wasn't, would I even be able to get into unraid?  I've logged in, ran command diagnostics, it says it writes the file but when i move the flash drive to my pc there is no folder for logs or any file that is written.  I also noticed that its not creating the network.cfg, which I removed that as part of troubleshooting earlier, expecting it to recreate itself upon boot.  I was able to get into the gui, I checked the network settings and its showing: 

    Jun 20 19:23:36 Tower: kernel: alx 0000:04:00.0 eth0: fatal interrupt 0x200, resetting

     

    Does this mean there is an irq conflict?  I've checked in bios and I don't see any way to change irq assignments... 

     

    This whole move has really frustrated me, I'm half tempted to put all the drives back in the old box, just to get it working again.  I have a feeling this is an issue with the Killer onboard nic my Gigabyte board has.  I've ordered a pcix network card that should be coming today, I'm gonna pop that in and see if it will at least pull an address.

  4. So as a test, I plugged a drive with windows on it, and it pulls an address. When I throw unraid back in, it does not. I have tried to get the diag log, but I must being doing something wrong because it doesn't write the file. I've ordered a network card, with the hope that the new mac will pull a dhcp address... Because I'm running out of ideas.

  5. Hello all, 

     

     This is probably my first time posting here, but i'm stumped and I need assistance.  I have moved unraid from an old HP DL350 G3, to a not as old desktop i wasn't using. The problem is when i booted up the new hardware its not pulling a 192.x.x.x address, its now getting an 164.x.x.x address.  No network link on nic.  The console said something about bond0, so I pulled the usb drive popped it into another pc and found that bonding was set to "yes" in the config.  I changed it to no, however upon boot, it still doesn't pull an address.  I have tried getting the syslog, but I must be doing something wrong because i can't get the syslog.zip.  At the console I tried "diagnostics", which said it wrote a file, but i couldn't find it in the root of the usb, then i tried another command "cp /var/log/syslog /boot", but that did nothing as well, no file on the root of usb...  I suspect the board in my new hardware setup may be the issue as the nic is not intel, its made by killer, its a gigabyte board and i'm using the onboard.  I'd really love to give you all the syslog, as i'm sure someone could quickly identify my problem, but i'm at a loss for how to get it.

  6. Thanks johathanm.  I have small drives mostly because i have a very tight budget.  Unraid is basically just hosting Plex at the moment, and I have a small library, so not much need for more capacity at the moment.  I know I'm way under-utilizing the server, but for now thats all I have use for.  Thanks again.

  7. Hello everyone.  I have a scenario that I haven't be able to find an answer to through my searching here.

    On my server I currently have:

    1TB WD blue (Parity)

    1TB WD blue (Data)

    1TB WD blue (Data)

    120gb WD SSD (Cache) 1 docker running

    2 empty disk slots

     

    I have a new 1TB WD Red on its way to replace the current parity drive, the old is not bad.  So what I want to do is use the old 1TB WD blue parity drive, and reassign it to a data drive, and use the new 1TB WD Red, as the new parity disc.  What procedure do I need to follow to do this properly. My apologies is this has already been asked, but I searched and couldn't find a related topic.  Thanks for any help in advance.