2) Assuming no to #1, and I have to move to another server- is there a way to determine with certainty which of the drives is the parity drive through those logs?  I am pretty sure I know which one (there are only 2 1.5tb drives) but I'd like to know with 100% certainty before I plop the drives into another tower...

If you only have two drives, one data and one parity and both are the same size then it doesn't matter which you choose as which. Your two drives are both exactly the same(parity is basically a mirror with two drives). If you were to plug the data or the parity by its self into a machine that can read the reiserfs filesystem then either one would have your data on it.

If you only have two drives, one data and one parity and both are the same size then it doesn't matter which you choose as which. Your two drives are both exactly the same(parity is basically a mirror with two drives). If you were to plug the data or the parity by its self into a machine that can read the reiserfs filesystem then either one would have your data on it.

 

I have several drives in the system, including two 1.5tb drives- one of which is parity.  Just not sure which, but it sounds like if I plug them into an ubuntu system and see which one has a real file system on it I'll know that the other is the parity drive.

I have several drives in the system, including two 1.5tb drives- one of which is parity.  Just not sure which, but it sounds like if I plug them into an ubuntu system and see which one has a real file system on it I'll know that the other is the parity drive.

Yeah in that case do what Purko said.

Any advice on a usb nic?  Is it possible either of these would work?  

http://www.belkin.com/IWCatProductPage.process?Product_Id=281799

That one has very bad reviews on newegg:

http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16833314025

 

No, the new router is assigning addresses in the 192.168.1.* range, while the old one used 192.168.0.*.  That being said, DHCP is enabled on the router and I edited network.cfg to retrieve an IP through DHCP rather than manually.

 

I just changed routers. I had to set the new router to the same network range and DHCP addresses as the old one to get my unRAID box to work.

 

My unRAID box was insisting on keeping it's old IP address of 192.168.1.100 and the new router was trying to use IP's in the range of 192.168.10.10-100 for DHCP. My config file had something like use DHCP with the other lines being blank so I'd like to know where unRAID is holding the IP address that it wouldn't work.

 

Peter

 

My unRAID box was insisting on keeping it's old IP address of 192.168.1.100 and the new router was trying to use IP's in the range of 192.168.10.10-100 for DHCP. My config file had something like use DHCP with the other lines being blank so I'd like to know where unRAID is holding the IP address that it wouldn't work.

Nowhere really.  Unless you enter a static IP in network.cfg, it doesn't remember any IP addresses upon reboot.

 

My unRAID box was insisting on keeping it's old IP address of 192.168.1.100 and the new router was trying to use IP's in the range of 192.168.10.10-100 for DHCP. My config file had something like use DHCP with the other lines being blank so I'd like to know where unRAID is holding the IP address that it wouldn't work.

Nowhere really.  Unless you enter a static IP in network.cfg, it doesn't remember any IP addresses upon reboot.

 

 

Y'know, I had a similar problem earlier on when I was first configuring the box.  I ended up setting a static IP for this very reason.  It seems very odd to me that the log file shows a link being detected but that it can't obtain a DHCP lease.  I really don't want to go to the trouble of putting a whole new box together if this is actually just a problem with unraid's config...  Maybe I'm being stubborn but I can't help but feel like there's something else going on here other than a broken nic.