Date: Wed, 14 May 2008 10:12:53 +0200 From: oxy <oxy@field.hu> To: Christian Baer <christian.baer@uni-dortmund.de> Cc: freebsd-geom@freebsd.org Subject: Re: Kernel with crypto and geli won't mount / Message-ID: <482A9F05.1060909@field.hu> In-Reply-To: <g0e52u$j94$2@nermal.rz1.convenimus.net> References: <g0e52u$j94$2@nermal.rz1.convenimus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
in your dmesg i don't see the mirrors.. did you compiled it in the kernel too? (or just load the module) after you load gmirror, geli will work too Christian Baer írta: > Hi there, people! > > I hope this isn't a double post! I noticed that my eMail-address in > the original post was wrong, so I'm guessing it was filtered. > > I have a little problem here that is bringing me some headaches. :-( > I am not sure if this is a GEOM-problem or one caused by the current > -STABLE fork, so I'll put this question in here too. Please excuse my > haste. The computer I tried to "remake" has been down for several days > now and that's never good. > > Sunday I set up a new FreeBSD 7.0 system (sparc64). This is a Sun U60 > and worked fine for me for ages under 6.3. Installing went without any > problems. The problems started, when I updated the sources (due to a > security issue) to RELENG_7. I made a new world and a new kernel. I > did change the kernel-config by adding two lines: > > options GEOM_ELI > device crypto > > Well, technically I did a fair bit more than that, but when I ran into > problems, I went back to a generic kernel with just these two extra > lines. What this boils down to is that adding GEOM_ELI and crypto to > the kernel seems to make my / unmountable (see dmesg after my sig). > The generic kernel works fine but that isn't quite good enough because > I have two encrypted providers on the drives - these were created > under the old Version though. > > One other thing might be worth mentioning: The system has two > configured gmirrors (the encrypted providers are on top of those). > These are not needed at boot time though and AFAIK no atempts to > configure them are being made. Although I did back up my data it would > be a lot easier to just keep them as they are instead of having to > remake them. > > Did I mess up somewhere or am I missing the point. > > Regards > Chris > > Here the dmesg: > Booting [/boot/kernel/kernel]... > nothing to autoload yet. > jumping to kernel entry at 0xc0078000. > stray vector interrupt 2029 > Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.0-STABLE #3: Tue May 13 09:32:42 CEST 2008 > root@sunny.rz1.convenimus.net:/usr/obj/usr/src/sys/SUNNY > real memory = 2147483648 (2048 MB) > avail memory = 2080759808 (1984 MB) > cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > registered firmware set <isp_1000> > registered firmware set <isp_1040> > registered firmware set <isp_1040_it> > registered firmware set <isp_1080> > registered firmware set <isp_1080_it> > registered firmware set <isp_12160> > registered firmware set <isp_12160_it> > registered firmware set <isp_2100> > registered firmware set <isp_2200> > registered firmware set <isp_2300> > registered firmware set <isp_2322> > registered firmware set <isp_2400> > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, > RF5413, REGOPS_FUNC) > nexus0: <Open Firmware Nexus device> > cryptosoft1: <software crypto> mem > 0x1fe00004000-0x1fe00005fff,0x1fe01000000-0x1fe010000ff,0x1fe00000000-0x1fe0000cfff > irq 2033,2030,2031,2021,2024,2034 on nexus0 > cryptosoft2: <software crypto> mem > 0x1fe00002000-0x1fe00003fff,0x1fe01800000-0x1fe018000ff,0x1fe00000000-0x1fe0000cfff > irq 2032,2030,2031,2021,2024,2034 on nexus0 > cryptosoft3: <software crypto> mem > 0x1fc00000000-0x1fc000003ff,0x1fc00400000-0x1fc005fffff,0x1fc00600000-0x1fc007fffff,0x1fc01000000-0x1fc013fffff,0x1fc01400000-0x1fc017fffff,0x1fc01800000-0x1fc01bfffff,0x1fc01c00000-0x1fc01ffffff,0x1fc02000000-0x1fc02ffffff,0x1fc03000000-0x1fc03ffffff,0x1fc04000000-0x1fc043fffff,0x1fc04400000-0x1fc047fffff,0x1fc04800000-0x1fc04bfffff,0x1fc04c00000-0x1fc04ffffff,0x1fc05000000-0x1fc05ffffff,0x1fc06000000-0x1fc07ffffff,0x1fc09000000-0x1fc097fffff,0x1fc09800000-0x1fc09ffffff,0x1fc0a000000-0x1fc0affffff,0x1fc0b000000-0x1fc0b7fffff,0x1fc0b800000-0x1fc0bffffff,0x1fc0c000000-0x1fc0c3fffff,0x1fc0c800000-0x1fc0cffffff,0x1fc0d000000-0x1fc0d7fffff,0x1fc0d800000-0x1fc0dffffff > irq 1925 on nexus0 > cryptosoft0: <software crypto> on nexus0 > nexus0: <syscons> type unknown (no driver attached) > Timecounters tick every 1.000 msec > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/da0a > > Manual root filesystem specification: > <fstype>:<device> Mount <device> using filesystem <fstype> > eg. ufs:/dev/da0a > ? List valid disk boot devices > <empty line> Abort manual input > > mountroot> > _______________________________________________ > freebsd-geom@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-geom > To unsubscribe, send any mail to "freebsd-geom-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?482A9F05.1060909>