[gentoo-user] Raid 5 creation is slow - Can this be done quicker?
Hi All, I am currently installing a new server and am using Linux software raid to merge 6 * 1.5TB drives in a RAID5 configuration. Creating the RAID5 takes over 20 hours (according to cat /proc/mdstat ) Is there a way that will speed this up? The drives are new, but contain random data left over from some speed and reliability tests I did. I don't care about keeping the current 'data', as long as when the array is reliable later. Can I use the --assume-clean option with mdadm and then expect it to keep working, even through reboots? Or is this a really bad idea? Many thanks, Joost Roeleveld
Re: [gentoo-user] Raid 5 creation is slow - Can this be done quicker?
Most of the wait I would assume is due to the size of the volume and creating parity. If it was my array I'd probably just sit tight and wait it out. On 2/1/10, J. Roeleveld jo...@antarean.org wrote: Hi All, I am currently installing a new server and am using Linux software raid to merge 6 * 1.5TB drives in a RAID5 configuration. Creating the RAID5 takes over 20 hours (according to cat /proc/mdstat ) Is there a way that will speed this up? The drives are new, but contain random data left over from some speed and reliability tests I did. I don't care about keeping the current 'data', as long as when the array is reliable later. Can I use the --assume-clean option with mdadm and then expect it to keep working, even through reboots? Or is this a really bad idea? Many thanks, Joost Roeleveld -- Sent from my mobile device Kyle
Re: [gentoo-user] Raid 5 creation is slow - Can this be done quicker?
On 1 Feb 2010, at 11:58, J. Roeleveld wrote: ... I am currently installing a new server and am using Linux software raid to merge 6 * 1.5TB drives in a RAID5 configuration. Creating the RAID5 takes over 20 hours (according to cat /proc/ mdstat ) Is there a way that will speed this up? The drives are new, but contain random data left over from some speed and reliability tests I did. I don't care about keeping the current 'data', as long as when the array is reliable later. Can I use the --assume-clean option with mdadm and then expect it to keep working, even through reboots? Or is this a really bad idea? It wasn't my intention to chide you - I don't use software RAID myself, and your question piqued my curiosity - but the first three Google hits for assume-clean indicate that this isn't safe to use with RAID5. The 4th Google hit contains an extract from the manpage: ... It can also be used when creating a RAID1 or RAID10 if you want to avoid the initial resync, however this practice -- while normally safe -- is not recommended. Use this only if you really know what you are doing. I have to say that I don't fully understand this. I would have thought that one could pretend the entire array was empty, and the RAID driver would just overwrite the disk as you write to the filesystem. The parts used by the filesystem are the only parts you care about, and I wouldn't have thought it would matter if the unused parts weren't in sync. I would be delighted if someone could explain me. I kinda expected this 20 hours to be spent verifying that the disks contain no bad sectors, which would really hose you if it were the case. But OTOH, 20 hours does not seem an outrageous amount of time for building a 7.5TB array. You're not going to do this often, and you want it done right. It would be interesting to know whether hardware RAID would behave any differently or allow the sync to perform in the background. I have only 1.5TB in RAID5 across 4 x 500gb drives at present; IIRC the expansion from 3 x drives took some hours, but I can't recall the initial setup. Stroller.
Re: [gentoo-user] OT: I want to get excited, but I just *know* they're going to mess it up...
On Sat, 30 Jan 2010 17:09:09 +0200, Alan McKinnon wrote: We don't have average idiots in /our/ civil service! What? You actively seek out the *special* idiots then? Not personally, although I do seem to attract them :( -- Neil Bothwick Idaho - It's not the end of the world, but you can see it from there. signature.asc Description: PGP signature
[gentoo-user] Transition to baselayout2 / openrc failed due to udev issues
Hi, Yesterday I faced a problem when trying to switch to baselayout2/openrc on a machine with lvm and raid. The scenario: Server has software raid with mdadm and lvm2 and is currently mostly stable amd64. Root partition is on md1 and most other partitions (also /usr, that might matter) on some lvm partitions. I added baselayout, openrc and sysvinit to package.keywords (later also tried with additionally adding lvm2, udev and mdadm, but that didn't change things) and followed the migration guide at http://www.gentoo.org/doc/en/openrc-migration.xml The system failed on boot. I think that the problem is that for some reason, udev isn't starting correctly. It is in the sysinit runlevel. The interesting part is probably * Populating /dev with ex/bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Setting system clock using the hardware clock [UTC] ... Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. * Failed to set the system clock [ !! ] I get a lot of more failures, raid and lvm isn't starting with errors. The LC_ALL-warnings are polluting everything, but that shouldn't be an issue (?). Any hints on what might be wrong? -- Hanno Böck Blog: http://www.hboeck.de/ GPG: 3DBD3B20 Jabber/Mail:ha...@hboeck.de http://schokokeks.org - professional webhosting signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Raid 5 creation is slow - Can this be done quicker?
On Monday 01 February 2010 14:20:28 Stroller wrote: On 1 Feb 2010, at 11:58, J. Roeleveld wrote: ... I am currently installing a new server and am using Linux software raid to merge 6 * 1.5TB drives in a RAID5 configuration. Creating the RAID5 takes over 20 hours (according to cat /proc/ mdstat ) Is there a way that will speed this up? The drives are new, but contain random data left over from some speed and reliability tests I did. I don't care about keeping the current 'data', as long as when the array is reliable later. Can I use the --assume-clean option with mdadm and then expect it to keep working, even through reboots? Or is this a really bad idea? It wasn't my intention to chide you - I don't use software RAID myself, and your question piqued my curiosity - but the first three Google hits for assume-clean indicate that this isn't safe to use with RAID5. The 4th Google hit contains an extract from the manpage: ... It can also be used when creating a RAID1 or RAID10 if you want to avoid the initial resync, however this practice -- while normally safe -- is not recommended. Use this only if you really know what you are doing. I did find the same results on Google, but not really a proper explanation as to why it's a bad idea. Unfortunately, my budget doesn't extend to a hardware raid solution. (The cheap cards offload it to the CPU anyway and are generally considered slower in various benchmarks) I kinda expected this 20 hours to be spent verifying that the disks contain no bad sectors, which would really hose you if it were the case. True, but I already ran badblocks twice on each disk to verify that the disks are fine. (No badblocks found). But OTOH, 20 hours does not seem an outrageous amount of time for building a 7.5TB array. You're not going to do this often, and you want it done right. Good point, and I agree, which is why I will let it finish it's course, but I also expected it could be done quicker. It would be interesting to know whether hardware RAID would behave any differently or allow the sync to perform in the background. I have only 1.5TB in RAID5 across 4 x 500gb drives at present; IIRC the expansion from 3 x drives took some hours, but I can't recall the initial setup. I'm hoping someone with more knowledge about RAID-systems can throw in his/her 2cents. Thanks, Joost
Re: [gentoo-user] Transition to baselayout2 / openrc failed due to udev issues
On Monday 01 February 2010 15:47:07 Hanno Böck wrote: Hi, Yesterday I faced a problem when trying to switch to baselayout2/openrc on a machine with lvm and raid. The scenario: Server has software raid with mdadm and lvm2 and is currently mostly stable amd64. Root partition is on md1 and most other partitions (also /usr, that might matter) on some lvm partitions. I added baselayout, openrc and sysvinit to package.keywords (later also tried with additionally adding lvm2, udev and mdadm, but that didn't change things) and followed the migration guide at http://www.gentoo.org/doc/en/openrc-migration.xml The system failed on boot. I think that the problem is that for some reason, udev isn't starting correctly. It is in the sysinit runlevel. The interesting part is probably * Populating /dev with ex/bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Setting system clock using the hardware clock [UTC] ... Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. * Failed to set the system clock [ !! ] I get a lot of more failures, raid and lvm isn't starting with errors. The LC_ALL-warnings are polluting everything, but that shouldn't be an issue (?). Any hints on what might be wrong? You have supplied a fair number of errors that are not related to the problem. Please post the errors that ARE related. Such as any lvm2, dm and mounting- root-filesystem errors -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Raid 5 creation is slow - Can this be done quicker?
It would be interesting to know whether hardware RAID would behave any differently or allow the sync to perform in the background. I have only 1.5TB in RAID5 across 4 x 500gb drives at present; IIRC the expansion from 3 x drives took some hours, but I can't recall the initial setup. LSI, 3ware and Areca hardware raid controllers are capable of doing a background init but their performance is impacted, I can't speak on other controllers as I haven't used them before. I've built many RAID6 arrays with all three controllers - 8x 1TB and 8x 1.5TB and I'll usually start a foreground init and let them run overnight because it does take a long time. Also, RAID10 is much faster to get up and running because it doesn't have to calculate parity. -- Kyle
Re: [gentoo-user] Transition to baselayout2 / openrc failed due to udev issues
Hanno Böck wrote: Am Montag 01 Februar 2010 schrieb Alan McKinnon: You have supplied a fair number of errors that are not related to the problem. Please post the errors that ARE related. Such as any lvm2, dm and mounting- root-filesystem errors Attached is the full log, but all others are probably followup errors caused by udev not creating devices. I'm pretty clueless on raid and all but did you find this? http://bugs.gentoo.org/290032 If I understand it correctly, it may be a problem with the upper/lower case in the settings. Hope that helps. Dale :-) :-)
Re: [gentoo-user] Bluetooth is impossible
All that is required is emerge bluez, reload dbus, start bluetooth, emerge blueman-1.21, config asound.conf as above, and restart alsasound. Has anyone gotten bluetooth pairing without a GUI tool such as blueman? That's the impossible part. Thanks Grant for sharing your experience (I'll try blueman version 1.21). I've also struggled with the bluetooth configuration, and I agree: the gentoo guide is outdated (have you contacted the author?). I tried to pair devices from the command line, but it was impossible for me too. Greetings, Damian.
[gentoo-user] libkdegames-3.5 won't compile
-3.5.10:20100201-172324.log'. * The ebuild environment file is located at '/var/tmp/portage/kde-base/libkdegames-3.5.10/temp/environment'. * S: '/var/tmp/portage/kde-base/libkdegames-3.5.10/work/libkdegames-3.5.10' Failed to emerge kde-base/libkdegames-3.5.10, Log file: '/var/log/portage/elog/kde-base:libkdegames-3.5.10:20100201-172324.log' * IMPORTANT: 1 news items need reading for repository 'gentoo'. * Use eselect news to read news items. r...@smoker / # I searched around on the forums, bgo and google and found suggestions to run lafilefixer --justfixit and revdep-rebuild. They don't help either. I also tried to use the skipfirst option and just come back to it but it complains about this missing package. I'm trying to hang onto KDE 3 and also have KDE 4 installed. I had to change some USE flags to get KDE 4 to upgrade. One of the flags was mDNSResponder. I don't know if that is related or not. Ideas? Should I shoot it? lol Thanks. Dale :-) :-)
[gentoo-user] configuring x2go on gentoo
Nikos Chantziaras wrote: On 01/22/2010 12:10 AM, Valmor de Almeida wrote: Hello, I would like to try a remote desktop server/client app (linux to linux). Would anyone have suggestions? freenx x ltsp x vnc x others? I use x2go, which is based on NX. FreeNX, which I used before, was semi-abandoned at some point. You can find it in the nx overlay. I am experimenting with it. I could not find config instructions for gentoo therefore I am following http://wiki.archlinux.org/index.php/X2go Is this sufficient? Does fuse need to be a module or can it be built into the kernel? I am follwing the latter. Thanks for inputs. -- Valmor
Re: [gentoo-user] Transition to baselayout2 / openrc failed due to udev issues
On Monday 01 February 2010 17:25:22 Hanno Böck wrote: INIT: version 2.87 booting /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) OpenRC rsec: mount of proc to /proc by /bin/mount[mount:616] uid/euid:0/0 gid/egid:0/0, parent /lib64/rc/sh/init.s0 1m0.6.0 is starting up Gentoo Linux (x86_64)rsec: mount of rc-svcdir to /lib64/rc/init.d by /bin/mount[mount:623] uid0 0m /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Mounting /proc ... [ ok ] * Caching service dependencies ... sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) [ ok ] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * /dev is already mounted /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Starting udevd ... [ ok ] * Populating /dev with ex/bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Setting system clock using the hardware clock [UTC] ... Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. * Failed to set the system clock [ !! ] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Starting up RAID devices ... [ !! ] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Setting up the Logical Volume Manager ... [ ok ] /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (de_DE.utf-8) * Setting up dm-crypt mappings ... * dm-crypt map crypt-cspace ... * cryptsetup will be called with : create crypt-cspace /dev/vg0/cspace Command failed: Error opening device: No such file or directory By this stage software raid has started correctly and found three raid arrays. But lvm has not started, I can tell because there are no errors about it. lvm must be in the boot runlevel, I suspect yours is not. IIRC this was a common issue with the migration to baselayout2. The locale errors must be fixed too, but that is a separate issue and I highly doubt it will interfere with lvm. Check if the locale de_DE.utf-8 is enabled in /etc/locale.gen - case is significant. -- alan dot mckinnon at gmail dot com
[gentoo-user] Re: configuring x2go on gentoo
On 02/01/2010 08:06 PM, Valmor de Almeida wrote: Nikos Chantziaras wrote: On 01/22/2010 12:10 AM, Valmor de Almeida wrote: Hello, I would like to try a remote desktop server/client app (linux to linux). Would anyone have suggestions? freenx x ltsp x vnc x others? I use x2go, which is based on NX. FreeNX, which I used before, was semi-abandoned at some point. You can find it in the nx overlay. I am experimenting with it. I could not find config instructions for gentoo therefore I am following http://wiki.archlinux.org/index.php/X2go Is this sufficient? Does fuse need to be a module or can it be built into the kernel? I am follwing the latter. Thanks for inputs. Don't know about the server configuration on Gentoo. I only run the client on my Gentoo box. The server runs on a Debian machine and IIRC the configuration was pretty much automatic there.
[gentoo-user] waiting for uevents...
Hello, Recently I bumped up (really) the number of HDD on a relatively old system (PATA IDE's) and I noticed that it took a while for gentoo to boot. After several weeks running, I tried to reboot and here is where I have a problem: *Populating /dev/ with existing devices through uevents... *Waiting for uevents to be processed... [34.7540621] Disabling IRQ #48 It just sits there for a very long time. Any inputs appreciated. Thanks. -- Valmor
Re: [gentoo-user] libkdegames-3.5 won't compile
On Monday 01 February 2010 19:47:27 Dale wrote: Well I synced and did a emerge -uvDN world. It said to run emerge @preserved-rebuild and I did. This is package number one and the error doesn't make much since to me. [snip] kgame/.libs/libkgame.a(kgamenetwork.o): In function `KGameNetwork::tryPublish()': kgamenetwork.cpp:(.text+0x56e): undefined reference to `DNSSD::PublicService::PublicService(QString const, QString const, unsigned int, QString const)' kgame/dialogs/.libs/libkgamedialogs.a(kgameconnectdialog.o): In function `KGameConnectWidget::setType(QString const)': kgameconnectdialog.cpp:(.text+0xdb0): undefined reference to `DNSSD::ServiceBrowser::ServiceBrowser(QString const, DNSSD::DomainBrowser*, bool)' This means that the code being built is trying to use a function called ServiceBrowser() and it's failing because it doesn't exist or is defined to be something different to what the code expects. [snip] I searched around on the forums, bgo and google and found suggestions to run lafilefixer --justfixit and revdep-rebuild. They don't help either. I also tried to use the skipfirst option and just come back to it but it complains about this missing package. Those are useful things to do often anyway, but all too often they are presented as the MagicBandAid(tm) solution to all build failures, world hunger and stuff that eats kittens. I doubt very much is they will help as none of those tips affect compiled libs already in place. I'm trying to hang onto KDE 3 and also have KDE 4 installed. I had to change some USE flags to get KDE 4 to upgrade. One of the flags was mDNSResponder. I don't know if that is related or not. kdelibs-3.5 on Gentoo had some outlandish requirements - zeroconf was one of them. I don't rightly recall which zeroconf method it was - zeroconf, mDNSResponder, avahi - but stuff broke horribly without it. What does eix say about KDE-3.5 packages using any of those flags? I don't have 3.5 around anymore to check here Also, KDE is heavily interlinked with Qt. A Qt upgrade usually implies a rebuild of all of KDE being a very good idea. It's not in DEPEND as KDE doesn't so much require a specific Qt version, it's that the built KDE now has to work with A higher version of Qt than it was build against. Did you recently upgrade Qt? Have you rebuilt kdelibs than tried building kdegames again? side-step workaround Have you asked the question Do I really need all of KDE games? /side-step workaround -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] libkdegames-3.5 won't compile
On 2/1/10, Dale rdalek1...@gmail.com wrote: /bin/sh ../libtool --silent --tag=CXX --mode=link i686-pc-linux-gnu-g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -march=athlon-xp -O2 -pipe -fomit-frame-pointer -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -Wl,-O1 -o libkdegames.la -rpath /usr/kde/3.5/lib -L/usr/kde/3.5/lib -L/usr/qt/3/lib -R /usr/kde/3.5/lib -R /usr/kde/3.5/lib -R /usr/qt/3/lib -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined -version-info 3:0:2 kcarddialog.lo kstdgameaction.lo kgamemisc.lo kchatbase.lo kchat.lo kchatdialog.lo kgameprogress.lo kcanvasrootpixmap.lo kgamelcd.lo highscore/libkhighscore.la kgame/libkgame.la kgame/dialogs/libkgamedialogs.la -lkio -lkdnssd A wild guess which might or might not do any good: cd into the directory where this happens, copy paste this monstrosity of a linking command it prints out, and switch the libs around from the end (lkio -lkdnssd = -lkdnssd -lkio). -- Arttu V.
Re: [gentoo-user] waiting for uevents...
100201 Valmor de Almeida wrote: Recently I bumped up the number of HDD on a relatively old system and I noticed that it took a while for Gentoo to boot. I tried to reboot and here is where I have a problem: *Populating /dev/ with existing devices through uevents... *Waiting for uevents to be processed... [34.7540621] Disabling IRQ #48 It just sits there for a very long time. I had this on my stand-by machine discovered it was waiting for a broken CD drive; when I unplugged the drive, all was well. Of course, your problem cb caused by something quite different. HTH -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] mysterious syslog message .
On Fri, 2010-01-29 at 17:29 +0200, Alan McKinnon wrote:
On Friday 29 January 2010 16:26:42 Iain Buchanan wrote:
I don't really care about any killswitch operation, but I'm interested
in why I'm getting a . message. NetworkManager bug or
misconfiguration error?
Run syslog-ng with the -d switch to enable it's debug output (normally to
messages), or use -dd to get even more debug output.
Beware, this adds up real quick, so don't run it for long like that. The
output may give you more of a clue as to what syslog-ng thinks the incoming
messages are.
Holy Debug Messages, Batman! Sure does add up real quick.
56,599 messages all with the same timestamp Feb 2 11:13:00; 100% cpu
usage, and 200+Mb before I killed it.
Shirley that's not right?
The 50k of messages all look like this:
Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation begins;
filter_rule='f_networkmanager'
Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter node evaluation result;
filter_result='not-match'
Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation result;
filter_result='not-match', filter_rule='f_networkmanager'
my syslog conf is directing network manager to a separate file:
@version: 3.0
# $Header:
/var/cvsroot/gentoo-x86/app-admin/syslog-ng/files/syslog-ng.conf.gentoo.3.0,v
1.1 2009/05/25 20:07:21 mr_bones_ Exp $
#
# Syslog-ng default configuration file for Gentoo Linux
options {
chain_hostnames(no);
# The default action of syslog-ng is to log a STATS line
# to the file every 10 minutes. That's pretty ugly after a while.
# Change it to every 12 hours so you get a nice daily update of
# how many messages syslog-ng missed (0).
stats_freq(43200);
};
source src {
unix-stream(/dev/log max-connections(256));
internal();
file(/proc/kmsg);
};
destination messages { file(/var/log/messages); };
# By default messages are logged to tty12...
destination console_all { file(/dev/tty12); };
# ...if you intend to use /dev/console for programs like xconsole
# you can comment out the destination line above that references /dev/tty12
# and uncomment the line below.
#destination console_all { file(/dev/console); };
# NetworkManager log to different file
log {
source(src);
filter(f_networkmanager);
destination(df_networkmanager);
flags(final);
};
log { source(src); destination(messages); };
log { source(src); destination(console_all); };
filter f_networkmanager { program(NetworkManager); };
destination df_networkmanager { file(/var/log/NetworkManager.log); };
any ideas? thanks,
--
Iain Buchanan iaindb at netspace dot net dot au
A synonym is a word you use when you can't spell the word you first
thought of.
-- Burt Bacharach
[gentoo-user] baselayout2/openrc question
G'day, I've been running baselayout-2 for several months and it's been working fine AFAICT. Over the weekend I noticed that my USB thumb drive is no longer automounting. This evening I ran /etc/init.d/udev status which reported: * status: stopped. Running /etc/init.d/udev start reported: * The udev init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: udev failed to start The message occurs because /etc/init.d/udev checks for /etc/init.d/sysfs, which is not present. Googling indicates that /etc/init.d/sysf comes from sys-apps/openrc. I have openrc-0.3.0-r1 installed (from long ago). openrc-0.6.0-r1 is available, though keyworded ~amd64. Unmasking it and running emerge -p ... shows that sysvinit is a blocker. Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely to get myself into troubleif I do this? If so, how much and how deep? Regards, David
Re: [gentoo-user] baselayout2/openrc question
On Tuesday 02 February 2010 06:03:10 David Relson wrote: G'day, I've been running baselayout-2 for several months and it's been working fine AFAICT. Over the weekend I noticed that my USB thumb drive is no longer automounting. This evening I ran /etc/init.d/udev status which reported: * status: stopped. Running /etc/init.d/udev start reported: * The udev init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: udev failed to start The message occurs because /etc/init.d/udev checks for /etc/init.d/sysfs, which is not present. Googling indicates that /etc/init.d/sysf comes from sys-apps/openrc. I have openrc-0.3.0-r1 installed (from long ago). openrc-0.6.0-r1 is available, though keyworded ~amd64. Unmasking it and running emerge -p ... shows that sysvinit is a blocker. Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely to get myself into troubleif I do this? If so, how much and how deep? very very very very deep trouble if you restart the machine and everything is not complete yet. Do not do that. all version of baselayout-2 are marked unstable and you likely have an old version of sysvinit that is not compatible with the ancient openrc you do have. That openrc is not in portage anymore. You should upgrade to the latest unstable portage (which supports automatically resolving blockers). You need baselayout, openrc and sysvinit as well as /etc/init.d/sysfs. I have none of these in world yet all are present. With the latest portage, try again and let portage figure out for itself what it wants to do. -- alan dot mckinnon at gmail dot com
