> But you've been using Gentoo for some time now, so you would be expected
> to have a grasp of the fundamentals. After all, you passed the Gentoo
> Entrance Exam :)
True enough, but I have a lot of hobbies. I may leave gentoo for a
while and go on to something else completely different as the ha
On Tue, 23 Jun 2009 15:59:02 -0600, Maxim Wexler wrote:
> > It's really not that hard, but you seem to be trying to find clever
>
> Walking's hard -- until you learn.
But you've been using Gentoo for some time now, so you would be expected
to have a grasp of the fundamentals. After all, you pa
> Create two partitions on sdb
> mount /dev/sdb1 /mnt/gentoo/var
> mount /dev/sdb2 /mnt/gentoo/home
>
> It's really not that hard, but you seem to be trying to find clever
Walking's hard -- until you learn.
> solutions when the simple one will do.
Well, of course the simple things have a way of
On Tue, 23 Jun 2009 13:15:13 -0600, Maxim Wexler wrote:
> OK, been staring at this terminal for about an hour. I'm at
> r...@sysresccd /mnt/gentoo where sda1 is mounted. Do I just mount sdb1
> on /mnt/gentoo too? Do I delete home and var then mkdirs on sdb2?
> Won't they just be re-made on the sam
On Tuesday 23 June 2009 21:15:13 Maxim Wexler wrote:
> > I'd put /home and /var on the SD card to start with, you may need to
> > put /usr/src on there too or your SSD may fill up when installing or
> > compiling a second or third kernel.
> >
> > I'd also move the portage tree there, but you can do
> I'd put /home and /var on the SD card to start with, you may need to
> put /usr/src on there too or your SSD may fill up when installing or
> compiling a second or third kernel.
>
> I'd also move the portage tree there, but you can do that
> post-installation by moving /usr/portage to /var/portag
On Mon, 22 Jun 2009 20:12:01 -0600, Maxim Wexler wrote:
> Ok, I did it! No more LVM! Wiped the SSD and made one partition out of
> it. Mounted it on /mnt/gentoo and unpacked the stage3 tarball. Silly
> question: now what? Where do I mount the SD card prior to unpacking
> portage? Do I make separat
> Forget LVM, forget a separate /boot, just stick / on the SSD and mount
> the likes of /var on the SD card. I use LVM on my Eee, but that's because
> it has two SSDs, I wouldn't dream of including the SD card in there.
>
Ok, I did it! No more LVM! Wiped the SSD and made one partition out of
it. M
On Mon, 22 Jun 2009 12:09:52 -0600, Maxim Wexler wrote:
> >> Necessary? Don't know but is meant to spare the SSD too much r/w
> >> strain.
> >
> > How? By spanning an LVM across the two, you have no control over
> > which is written to the most. I'd put / on the SSD then mount
> > write-heavy di
On Mon, 22 Jun 2009 11:33:13 -0600, Maxim Wexler wrote:
> > dmesg output would also be a good thing to sort this out.
> 477 lines! Rather than post it, what sort of thing(s) should I look
> for. sda and sdb show up OK. All the usb stuff looks alright. grepping
> for scsi shows that the SSD and S
On Mon, 22 Jun 2009 11:42:05 -0600, Maxim Wexler wrote:
> > Actually, it's /etc/init.d/localmount, not bootmisc. Add a sleep
> > command just before No, you'de need to edit the bootmisc script and
> > add a sleep command just before
>
> Sorry, this doesn't scan well.
It doesn't, that not what
>
>> Necessary? Don't know but is meant to spare the SSD too much r/w strain.
>
> How? By spanning an LVM across the two, you have no control over which is
> written to the most. I'd put / on the SSD then mount write-heavy
> directories, like /var and /home, on the SD card. I'd also set $PORTDIR
>
> Actually, it's /etc/init.d/localmount, not bootmisc. Add a sleep command
> just before No, you'de need to edit the bootmisc script and add a sleep
> command just before
Sorry, this doesn't scan well. Do I put the sleep command in
localmount or not? Then edit bootmisc too?
How many seconds do I
> That could either mean that (not all of) the drivers needed to access this
> device are available (not compiled into the kernel), or what Neil already
> wrote: a delay in discovering the device.
>
> dmesg output would also be a good thing to sort this out.
>
477 lines! Rather than post it, what
> Are CONFIG_BLK_DEV_SD and CONFIG_SCSI also compiled in?
>
Yes
mw
Am Sonntag 21 Juni 2009 23:16:49 schrieb Maxim Wexler:
> Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-2lHroF'.
> Couldn't find all physical volumes for volume group vg.
That could either mean that (not all of) the drivers needed to access this
device are available (not com
Am Montag 22 Juni 2009 03:20:02 schrieb Maxim Wexler:
> > Would I be correct in thinking the SSD is a sata device while the SD is
> > a usb device??
> >
> > How are you USB drivers compiled in the kenrnel?
And what about:
> # NOTE: USB_STORAGE depends on SCSI but BLK_DEV_SD may also be needed;
>
On Sun, 21 Jun 2009 19:13:19 -0600, Maxim Wexler wrote:
> >> mount: /dev/vg/tmp already mounted on /tmp
> >> mount: tmpfs already mounted on /tmp
> >
> > It's nothing to do with your problem, but why are you mounting two
> > filesystems on /tmp?
>
> fstab:
> ...
> shm /dev/shm tmpfs nodev,nos
> Would I be correct in thinking the SSD is a sata device while the SD is
> a usb device??
>
> How are you USB drivers compiled in the kenrnel?
# CONFIG_USB_ZD1201 is not set
# CONFIG_USB_NET_RNDIS_WLAN is not set
CONFIG_RT2500USB=m
# CONFIG_RT73USB is not set
CONFIG_RT2X00_LIB_USB=m
# USB Network
On 6/21/09, Neil Bothwick wrote:
> On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:
>
>> mount: /dev/vg/tmp already mounted on /tmp
>> mount: tmpfs already mounted on /tmp
>
> It's nothing to do with your problem, but why are you mounting two
> filesystems on /tmp?
fstab:
...
shm /dev/shm
Neil Bothwick wrote:
On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:
mount: /dev/vg/tmp already mounted on /tmp
mount: tmpfs already mounted on /tmp
It's nothing to do with your problem, but why are you mounting two
filesystems on /tmp?
Couldn't find device with uuid 'ldwVeS-gwl4-
On Sun, 21 Jun 2009 15:16:49 -0600, Maxim Wexler wrote:
> mount: /dev/vg/tmp already mounted on /tmp
> mount: tmpfs already mounted on /tmp
It's nothing to do with your problem, but why are you mounting two
filesystems on /tmp?
> Couldn't find device with uuid 'ldwVeS-gwl4-HE4Z-M3Gw-DILI-Dbjh-
> differences: no device-mapper, no consolefont, no lvm, no root
My bad: root IS there.
> noted above) eg bootmisc -> /etc/init.d/bootmisc. Maybe if I add the
> missing links to /usr/share/openrc/runlevels that'll fix things...I'll
> try that in the meantime.
No change whatever. Back to the draw
> Could you please remove rc.log, reboot and post the fresh rc.log?
Done:
rc shutdown logging started at Sun Jun 21 14:40:55 2009
* Stopping local...
[ ok ]
* Saving random seed...
[ ok ]
* Deactivating swap devices...
[ ok ]
* Unmounting network filesystems...
[ ok ]
* Bringing down interfa
Am Sonntag 21 Juni 2009 01:51:34 schrieb Maxim Wexler:
> > So you should really put device-mapper into the boot runlevel. And btw,
> > why do
> > compile things as modules which you need in any case? Doesn't make sense
> > to me.
>
> I put device-mapper into the boot runlevel. I re-compiled the ker
> So you should really put device-mapper into the boot runlevel. And btw, why
> do
> compile things as modules which you need in any case? Doesn't make sense to
> me.
>
I put device-mapper into the boot runlevel. I re-compiled the kernel
with dm-mod=<*>, dm_crypt=<*>, mmc_block=<*> and rebooted.
Am Samstag 20 Juni 2009 22:23:58 schrieb Dirk Heinrichs:
> > No good. rc-update shows udev, devfs, dmesg, device-mapper in sysinit
> > runlevel.
>
> device-mapper is wrong, there.
After reading your initial post in this thread again, that explains the
problem. You have dm-crypt and dm-mod compile
Am Samstag 20 Juni 2009 22:26:31 schrieb Dirk Heinrichs:
> Am Samstag 20 Juni 2009 21:23:29 schrieb Maxim Wexler:
> > > As said above, it's not not needed. Maybe it's better to investigate
> > > wether there are any leftovers from baselayout 1 in the runlevels. This
> > > was at
> >
> > How?
>
> Yo
Am Samstag 20 Juni 2009 21:23:29 schrieb Maxim Wexler:
> > As said above, it's not not needed. Maybe it's better to investigate
> > wether there are any leftovers from baselayout 1 in the runlevels. This
> > was at
>
> How?
You could start by comparing the contents of the bl2 and openrc packages w
Am Samstag 20 Juni 2009 21:14:35 schrieb Maxim Wexler:
> > Guess you can do the same, at least if you don't have dm-crypt
> > mappings, or you can try adding device-mapper to sysinit level directly.
> >
> >
> > Here's my boot sequence (from rc.log):
> >
> >
> > rc sysinit logging started at Fri J
> As said above, it's not not needed. Maybe it's better to investigate wether
> there are any leftovers from baselayout 1 in the runlevels. This was at
How?
> least
> the reason I got an unbootable system after switching to bl 2.
>
I upgraded to bl-2 to avoid this problem but it didn't help. The
> Guess you can do the same, at least if you don't have dm-crypt
> mappings, or you can try adding device-mapper to sysinit level directly.
>
>
> Here's my boot sequence (from rc.log):
>
>
> rc sysinit logging started at Fri Jun 12 04:24:55 2009
No good. rc-update shows udev, devfs, dmesg, devic
Am Samstag 20 Juni 2009 13:56:51 schrieb Mike Kazantsev:
> > > So LVM would start before dmcrypt? Great.
> >
> > Yes.
>
> No, because encrypted partitions hold LVM volumes as well.
Well, the usual way is to encrypt LVs, so LVM mut be first. Gentoo support's
this scheme as default. If you decide
On Sat, 20 Jun 2009 11:01:33 +0200
Dirk Heinrichs wrote:
> Am Samstag 20 Juni 2009 09:37:24 schrieb Mike Kazantsev:
>
> > Dirk Heinrichs wrote:
> > > > I believe there's "after device-mapper" line already in lvm-2.02.45, so
> > > > it should run fine, but as an additional precaution I have dm-c
Am Samstag 20 Juni 2009 09:37:24 schrieb Mike Kazantsev:
> Dirk Heinrichs wrote:
> > > I believe there's "after device-mapper" line already in lvm-2.02.45, so
> > > it should run fine, but as an additional precaution I have dm-crypt
> > > script at sysinit runlevel, which starts device-mapper and
On Sat, 20 Jun 2009 09:08:05 +0200
Dirk Heinrichs wrote:
> > I believe there's "after device-mapper" line already in lvm-2.02.45, so
> > it should run fine, but as an additional precaution I have dm-crypt
> > script at sysinit runlevel, which starts device-mapper and dm-crypt
> > before lvm or ev
Am Samstag 20 Juni 2009 07:33:38 schrieb Mike Kazantsev:
> On Fri, 19 Jun 2009 22:15:12 -0600
>
> Maxim Wexler wrote:
> > Seems if I add the commands:
> >
> > vgscan --mknodes
> > vgchange -a y
> > mount -a
> >
> > to /etc/conf.d/bootmisc and add it to the boot runlevel, the eee boots
> > to a coh
On Fri, 19 Jun 2009 22:15:12 -0600
Maxim Wexler wrote:
> Seems if I add the commands:
>
> vgscan --mknodes
> vgchange -a y
> mount -a
>
> to /etc/conf.d/bootmisc and add it to the boot runlevel, the eee boots
> to a coherent system BUT not before going through LVM failure, errors,
> inability t
Hi group,
Rather than resurrect an old thread though I'd start anew with a fresh clue.
Seems if I add the commands:
vgscan --mknodes
vgchange -a y
mount -a
to /etc/conf.d/bootmisc and add it to the boot runlevel, the eee boots
to a coherent system BUT not before going through LVM failure, error
>
> Locking type 1 initialisation failed
googling this finds precious little -- whether spelled with an 's' or
a 'z', but check this:
http://bugs.gentoo.org/show_bug.cgi?id=118275#c16
A lot like my situation: the unit boots, the above error flashes by, I
log into a crippled system and enter the
On Wed, 17 Jun 2009 18:14:11 +0200, Alan McKinnon wrote:
> The fact that it's aligned around desktop users is of no significance
> here, but looking back, it would be easy to miss that bit.
>
It was where you said
> I also find in general that rescue systems are not very good at these
> desktop
On Wednesday 17 June 2009 17:44:22 Neil Bothwick wrote:
> > > I never said you don't want hotplugging. Set rc_hotplug to
> >
> > you said "automatic" hotplugging; is that something else?
>
> I explained that in my previous post, Alan was referring to desktop
> hotplugging, like mounting removable
On Wed, 17 Jun 2009 09:41:14 -0600, Maxim Wexler wrote:
> >> Guess you're right, I don't want hotplugging.
> >
> > I never said you don't want hotplugging. Set rc_hotplug to
>
> you said "automatic" hotplugging; is that something else?
I explained that in my previous post, Alan was referring
>> Guess you're right, I don't want hotplugging.
>
> I never said you don't want hotplugging. Set rc_hotplug to
you said "automatic" hotplugging; is that something else?
> "!net.*" to disable network hotplugging, and add net.lo back to the boot
thanks Neil, speeds up the boot process a lot. May
On Tue, 16 Jun 2009 19:32:56 -0600, Maxim Wexler wrote:
> Going cuckoo here @!#>. I said it was fixed. I uncommented the
> rc_hotplug line in rc.conf and rebooted and it worked! The volumes
> were found and mounted. Fantasia! Now I rebooted again having tried to
> shut of dhcpcd, using rc-update
On Tue, 16 Jun 2009 18:57:32 -0600, Maxim Wexler wrote:
> > Except Maxim doesn't want automatic hotplugging, he wants to mount
> > the LV from init scripts.
> In /etc/rc.conf I uncommented the line rc_hotplug="*" on a hunch and
> it did the trick!
That's not the hotplugging Alan was referring to
On 6/16/09, Neil Bothwick wrote:
> On Tue, 16 Jun 2009 22:39:56 +0200, Alan McKinnon wrote:
>
>> I also find in general that rescue systems are not very good at these
>> desktopy things, and automagic SD card hotplugging is very much
>> something driven by desktop usage. Try by all means, I just t
On 6/16/09, Neil Bothwick wrote:
> On Tue, 16 Jun 2009 22:39:56 +0200, Alan McKinnon wrote:
>
>> I also find in general that rescue systems are not very good at these
>> desktopy things, and automagic SD card hotplugging is very much
>> something driven by desktop usage. Try by all means, I just t
On Tue, 16 Jun 2009 22:39:56 +0200, Alan McKinnon wrote:
> I also find in general that rescue systems are not very good at these
> desktopy things, and automagic SD card hotplugging is very much
> something driven by desktop usage. Try by all means, I just think YMMV.
Except Maxim doesn't want au
On Tuesday 16 June 2009 21:12:06 Maxim Wexler wrote:
> > If google or menuconfig's help function doesn't give me an answer in 10
> > minutes, I boot off Ubuntu Netbook Remix on a usb stick (it's a 1G
> > download),
> > and note which modules it loads and settings it uses for stuff. Boot back
> > in
>
> If google or menuconfig's help function doesn't give me an answer in 10
> minutes, I boot off Ubuntu Netbook Remix on a usb stick (it's a 1G
> download),
> and note which modules it loads and settings it uses for stuff. Boot back
> into
> gentoo, configure and build accordingly ... sorted
Does
On Tuesday 16 June 2009 17:52:28 Maxim Wexler wrote:
> >> FWIW only one device, the SD card, can't be found and it is listed
> >> about 20 times in the boot console before the LVM gives up.
> >
> > Is everything needed to use the SD card compiled into the kernel? As it
> > works after everything is
On Tue, 16 Jun 2009 09:52:28 -0600, Maxim Wexler wrote:
> Locking type 1 initialisation failed
> Couldn't find devices with uuid etc...
Just a guess, but it could be that it takes a while for the card reader
to recognise the card after the module is loaded.
I wouldn't put part of an LVM on an S
On 6/16/09, Maxim Wexler wrote:
>>> FWIW only one device, the SD card, can't be found and it is listed
>>> about 20 times in the boot console before the LVM gives up.
>>
>> Is everything needed to use the SD card compiled into the kernel? As it
>> works after everything is loaded, I suspect not. L
>> FWIW only one device, the SD card, can't be found and it is listed
>> about 20 times in the boot console before the LVM gives up.
>
> Is everything needed to use the SD card compiled into the kernel? As it
> works after everything is loaded, I suspect not. Look for anything
> relevant in the out
On Mon, 15 Jun 2009 18:33:22 -0600, Maxim Wexler wrote:
> How did I only get baselayout-1? I used the latest tarballs. And what
> init-script should I use?
Because the tarballs use stable packages and baselayout-2 is still in
testing.
> FWIW only one device, the SD card, can't be found and it is
On Tuesday 16 June 2009 02:33:22 Maxim Wexler wrote:
> > With baselayout2 and openrc, you need to explicitly put lvm into the boot
>
> Wow! I didn't even realize lvm was in init.d. There's nothing in the
> doc about it. So I went ahead and added to the boot-level and
> rebooted.
>
> Same as before
>
> So where is the second SSD. This is the 900 you have?
900A, maybe different from yours.
>> Cool! There's all my little dirs. Thanks Neil. But isn't it supposed
>> to do this automaticamente?
>
> Yes, but the duplicate filter line is preventing your VGs from being
> created, so mounting those
>
> #LVM should normally only be started after mdraid is available
> #this is because LVM physical volumes are very often MD devices
> RC_AFTER="mdraid"
>
> #vim: ft=gentoo-conf-d
>
> Well, I don't have mdraid, as far as I know. I'll just comment out
> that line and see where it leads.
>
> mw
nowh
>
> With baselayout2 and openrc, you need to explicitly put lvm into the boot
Wow! I didn't even realize lvm was in init.d. There's nothing in the
doc about it. So I went ahead and added to the boot-level and
rebooted.
Same as before with (looks like) one addition:
...
*The lvm init-script is wri
On Mon, 15 Jun 2009 10:51:54 -0600, Maxim Wexler wrote:
> > On an Eee 900, the SD card is sdc.
>
> Nope, sdb, just checked. It goes to sdc if you pop it out and push it
> back in again.
So where is the second SSD. This is the 900 you have?
> >> WARNING: Ignoring duplicate config node: filter
> Have you tried with the default filter
> filter = [ "r|/dev/nbd.*|", "a/.*/" ]
exact same result.
mw
On Monday 15 June 2009 18:51:54 Maxim Wexler wrote:
> > Did you mount -a after activating the VG?
>
> Cool! There's all my little dirs. Thanks Neil. But isn't it supposed
> to do this automaticamente?
> From the doc:
>
> Restart your machine and all partitions should be visible and mounted.
>
On 6/15/09, Neil Bothwick wrote:
> On Sun, 14 Jun 2009 19:04:35 -0600, Maxim Wexler wrote:
>
>> My fllter in lvm.conf : filter = [ "a|/dev/sd[ab]|", "r/.*/"] which
>> corresponds to my Phison SSD and a 8G SD card.
>
> On an Eee 900, the SD card is sdc.
Nope, sdb, just checked. It goes to sdc if y
On Sun, 2009-06-14 at 19:04 -0600, Maxim Wexler wrote:
> Hi group,
>
> My fresh install of 2.6.29-r5 goes kablooey just after 'Loading module dm-mod'
>
> Then the boot console reports:
>
> Couldn't find device with uuid 'ldwVeS-gw14-HE42-M3Gw-DILI-Dbjh-2lHroF'
>
> and
>
> Couldn't find all phy
On Sun, 14 Jun 2009 19:04:35 -0600, Maxim Wexler wrote:
> My fllter in lvm.conf : filter = [ "a|/dev/sd[ab]|", "r/.*/"] which
> corresponds to my Phison SSD and a 8G SD card.
On an Eee 900, the SD card is sdc.
> When I run the reactivate commands given at the end of the above
> document all goes
Hi group,
My fresh install of 2.6.29-r5 goes kablooey just after 'Loading module dm-mod'
Then the boot console reports:
Couldn't find device with uuid 'ldwVeS-gw14-HE42-M3Gw-DILI-Dbjh-2lHroF'
and
Couldn't find all physical volumes for volume group vg.
and
Volume group "vg" not found
The abo
I'm about to start using LVM. I setup a secondary partition with fdisk,
created a physical volume with pvcreate, made a group volume with
vgcreate (out of only that physical volume), created several logical
volumes with lvcreate, and installed filesystems on the logical volumes.
One volume is swap
68 matches
Mail list logo
