hello

 

I have an old PC, with 2 HDD (1 IDE and 1 SATA), and the NIC is (RTL8110SC / 82684S1)

 

I tried this version of unRAID (5.0-rc6-r8168-test), but it did not detect my NIC, I was getting "lo" when i was trying ifconfig eth0.

 

I then went and tried this version of unRAID (5.0-rc5 AiO), and it worked.

 

Just thought of reporting this issue.

 

Ooops - a genuine case where the r8169 driver is needed?

^^Yup...seen one other post of this happening on older hardware

This is a quiet thread for a rc, so this is very close to FINAL from the looks of it.  Solid build so far for me.  The only thing I haven't tested was NFS, but others have so good enough.

 

1 vote for FINAL here. 

Indeed. Should we expect an rc7 soon or will we likely go straight from -test2 to final?

 

I vote for one more (hopefully) RC and we can take it home with a simple rename for final.

I propose the moment 5 goes final we all agree to have drink at the same time :-)

Was the intention of this release to get us to a final though or just a temporary bug fix for the rc5 issue?

Was the intention of this release to get us to a final though or just a temporary bug fix for the rc5 issue?

closer to a final

I propose the moment 5 goes final we all agree to have drink at the same time :-)

 

AGREED!  :-)

+1

Must be close now....what do you think Tom?

I almost hate to post this, as there's a chance it's a non-5.0-rc6-r8168-related issue (and it'll be hard to determine for sure until I get home tonight and force-reboot it, assuming that's the recommendation here), but just in case it's a bug:

 

I've been up and running without issue for well over a week now, transferring files and checking parity without issue since the last weird webgui-related crash (see earlier in this thread).

 

I decided to restart it this morning to hot swap a new drive, but never made it that far - after stopping the array, and selecting restart from the main webgui, everything hung.  I can't access the webgui anymore (hell, the entire tower is missing from my network list now), and my unraid-equipped USB stick is flashing nonstop (at regular intervals; one flash, nothing, one flash, nothing, one flash, nothing).

 

With that sort of activity on the flash drive, I'm loathe to force-reboot at this point - it seems like it's the only way to get a syslog, though.  If anyone has any ideas on how to handle without a force-reboot, please let me know; otherwise, I'll have a full syslog up tonight.

Have you tried connecting a monitor up to your server and seeing what messages are being displayed on it?

That was actually one of the first things I did - unfortunately, the monitor was receiving no signal.  It's all pretty weird...

Or just connect using putty and do a nice controlled powerdown and reboot...

That sounds like a plan - I'll research the steps during lunch and implement as soon as I get home.  Thanks for the suggestion!

I almost hate to post this, as there's a chance it's a non-5.0-rc6-r8168-related issue (and it'll be hard to determine for sure until I get home tonight and force-reboot it, assuming that's the recommendation here), but just in case it's a bug:

 

I've been up and running without issue for well over a week now, transferring files and checking parity without issue since the last weird webgui-related crash (see earlier in this thread).

 

I decided to restart it this morning to hot swap a new drive, but never made it that far - after stopping the array, and selecting restart from the main webgui, everything hung.  I can't access the webgui anymore (hell, the entire tower is missing from my network list now), and my unraid-equipped USB stick is flashing nonstop (at regular intervals; one flash, nothing, one flash, nothing, one flash, nothing).

 

With that sort of activity on the flash drive, I'm loathe to force-reboot at this point - it seems like it's the only way to get a syslog, though.  If anyone has any ideas on how to handle without a force-reboot, please let me know; otherwise, I'll have a full syslog up tonight.

 

I realize that you never got that far, BUT I didn't think that unRAID supported 'hot swapping'.  If it doesn't, you could create a real mess!

BUT I didn't think that unRAID supported 'hot swapping'. 

It does not.

I probably used the wrong language (or I've been doing the wrong thing in the past) - I've "hot swapped" by placing a new drive in an empty hot swap slot and restarting the system (at which point it's picked up by the MARVELL cards and reported to unraid).

 

This time, I went for the reboot without actually placing the drive in the slot (even though that was my original plan - rough morning), so even if I've been doing this wrong, the "hot swap" itself shouldn't be a factor on this error... Hope this clears things up!

You can 'hot-swap' in that if you 'Stop' the array, you can perform any disk movements and then 'Start' the array.  No need to reboot - unRAID will recognise new devices on starting the array.

 

I think that's what you are saying that you did.

You can 'hot-swap' in that if you 'Stop' the array, you can perform any disk movements and then 'Start' the array.  No need to reboot - unRAID will recognise new devices on starting the array.

Is that true? Can you just pull out drives if the array is stopped, and the os etc is still running? No need to powerdown first? I thought you should at least enable AHCI in the BIOS as well?

PeterB: that's exactly what I've been doing (plus reboot for drives on the MARVELL cards).  Thanks for the clarification!

You can 'hot-swap' in that if you 'Stop' the array, you can perform any disk movements and then 'Start' the array.  No need to reboot - unRAID will recognise new devices on starting the array.

Is that true? Can you just pull out drives if the array is stopped, and the os etc is still running? No need to powerdown first? I thought you should at least enable AHCI in the BIOS as well?

 

I do it all the time, it's been working great with the later 5.0 builds. I assume you should have AHCI enabled in the BIOS anyway, not sure why anyone would run on IDE mode.

 

There are very few reasons why you should actually shut the server completely down.

So, I managed a bit of research on PuTTY at lunch - it seems like my tower's missing IP address might be a deal-breaker for this approach (it's not showing up on the network at all).  Does anyone else have any other ideas before I go for the forced-restart in a few hours when I make it home?

I thought you should at least enable AHCI in the BIOS as well?

 

I do it all the time, it's been working great with the later 5.0 builds. I assume you should have AHCI enabled in the BIOS anyway, not sure why anyone would run on IDE mode.

 

Exactly!

Forced restart, syslog attached - everything seems good... but what the hell could have caused this?  Definitely left field...  Hope the log helps development!

syslog8-9-12.txt

Maybe in 5.1 - unRAID should support mirror features.. like in Raid 10.