I just had e2fsck grind up the / partition on the 250Gb drive that came in the ARK boxes I bought with D-525MW boards in them.
So I ran up to staples and brought home a 2Tbyte drive wearing the Toshiba label, mainly because it had a 2 year warranty as opposed to WD's 2 year on a 1Tbyte. Brought it home, and based on previous experience with the installers partitioning & formatting, I did that while plugged into this machine. And while it is a native 4k block size, so far that has not been a problem. But I had forgotten that you, in your infinite wisdom, had configured the iso to use IPV6 only. For normal networking, I did my usual hosts file and interfaces hacks by hand, and got that working with my local 192.168.xx.xx net on ipv4, but then ran into the same problem when trying to make amanda, the network backup/recover program work. It took 3 days to locate that problem as I had to go into /etc/init.d/xinetd and comment out those 3 lines that restricted xinetd from working with IPV4 addresses. It was not illuminated in any way by amcheck or the rest of the amanda utilities as the only error reported was "connection refused", with no clue in the amanda logs on either machine that it was xinetd doing the refusal. I had forgotten as it has been 2 or 3 years since I did those installs, that all this needed to be fixed by someone with a working knowledge of networking, which only just barely included me. Simply put, for 99% of us, I suspect IPV6 will not arrive in our shops within our remaining lifetimes. Doing that, to a now 4+ year old ubuntu release whose ipv6 implementation was not well checked and probably broken, is exactly the sort of a nightmare that will drive a newbie coming from windoze away from some great machine driver software. The offending option, actually found with "grep -R ipv6 /etc" is: /etc/init.d/xinetd:# XINETD_OPTS="$XINETD_OPTS -inetd_ipv6" Comment, or nuke, that line _and_ the if line above it, _and_ the fi line below it. Then xinetd works with IPV4. Please do _not_ do that ipv6 only restriction to the next iso spin. Side comment for Seb, who answered my squawk about the black screen crashes: I am beginning to think that spurious interrupts from that drive as it was dying might have been the cause of my black screen lockups. I have ran stuff, and stopped them again, without having the lockup following the exit since the new drive went in, linuxcnc has been started and shut down 20 times at least, and gedit, which on its save & exit could also trigger the lockup, has been run and exited at least 100 times in the last 5 days. The only reboots were reboots I have triggered on purpose. With the older drive, I would have had 15 or 20 such crashes by now. If this holds true for another 2 or 3 weeks, I'll replace the drive in the milling machines identical but 3 months older box as it is also doing it, but at a much lower frequency. So far... Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
