April 2, 200818 yr Just attempted loading the new Beta 4 and it hangs during startup... Had been working fine under all of the previous 4.3 Betas.... I added an eSata 300 GB HD that I planned on using as my Swap disk, but otherwise no changes to anything else (I'm rebooting without the eSATA drive in there now). P5B-VM DO Motherboard Last 3 Lines (How do get a full log if I can't get it to boot) Going multiuser... Updating shared library link: /sbin/ldconfig & Starting sysklogd daemons: /usr/sbin/syslogd -m0 *** EDIT *** Same result without the eSATA drive plugged in.... *** EDIT #2 *** Going back to Beta3 allowed me to boot normally and it did see the new eSATA drive that I plan to use for my cache disk...
April 2, 200818 yr Same for me. I have the Asus P5B-VM DO. Reinstalling beta3 worked fine. I don't have the pro license, just the regular one (5 data 1 parity)
April 2, 200818 yr I used to use version 4.2.1. Tried beta4 last night and got the same problem. Then I use beta3 instead and everything works. So I believe beta4 still has some bugs that need to be fixed. The motherboard that I used is P5K-VM DO.
April 3, 200818 yr This problem does not happen on all motherboards. It's not an unRAID issue, but a linux issue - been working on this all day & will post -beta5 when there's a solution.
April 3, 200818 yr This problem has been fixed in 4.3-beta5, now available. It only took 12 hours to figure this one out.... Has nothing to do with which motherboard... <begin linux discussion> During development of cache disk feature we wanted to do a series of performance tests & it became desirable to resolve netbios host names via non-Samba utilities (like ping). To do this, what you do is edit the /etc/nsswitch.conf file and add 'wins' to the end of the 'hosts:' line like this: hosts: files dns wins This is just dandy - say you have 2 unRAID servers, 'tower' and 'tower2'. Then from 'tower' you can type: ping 'tower2' This was kind of a nice feature so we just left in -beta4. Well..... turns out that syslogd calls 'gethostbyname()' which attempts to resolve the fqdn of the local host. But apparently, if there is no WINS server on your local network, then the 'wins' resolution just 'hangs', which causes syslogd invokation to hang, which causes the whole system to hang, which causes disgruntled user to post on this message board So why does wins resolution hang if there's no WINS server?? I have no idea... & I'm not too interested is scouring the libnsswins code, so our solution is to simply remove that 'wins' token from the nsswitch.conf file. <end linux discussion> BTW - reason we never saw this bug before releasing 4.3-beta4 was that our own development network has a running WINS server. As soon as we set up a simple network to start testing different motherboards was the problem apparent.
April 3, 200818 yr This problem has been fixed in 4.3-beta5, now available. It only took 12 hours to figure this one out.... Has nothing to do with which motherboard... ... Looks like a VERY late night! Thanks so much for all your hard work. We appreciate it!!! -Brian
April 3, 200818 yr This problem has been fixed in 4.3-beta5, now available. It only took 12 hours to figure this one out.... Has nothing to do with which motherboard... ... Looks like a VERY late night! Thanks so much for all your hard work. We appreciate it!!! -Brian Yes it was... Also included was much cursing, alcohol, then caffeine, more cursing, about 500 system reboots and finally "slaps forehead" the 'aha' moment
April 4, 200818 yr > about 500 system reboots I can deal with everything else... It's the wasted time through reboots that kills me !!! LOL... thanks for all the hard work.
April 4, 200818 yr Wow... I hope your hard work pays off. Its very re-assuring to have guys that work so hard behind their products. I hope your rich if not, keep up the good work and you will be someday.... You should keep an eye on that power switch, it will probably be the first thing to go on that PC
Archived
This topic is now archived and is closed to further replies.