Re: [gentoo-user] Re: Again - problem on installing Gentoo (Gentoo started)

[Stephen Liu]

Hi folks,

Fruther to my late posting, now Gentoo started finally, but still
having problem on mounting Logcial Volumes;
/dev/vg/usr
/dev/vg/home
etc.

"localhost login" started.  Root login was possble.


/etc/fstab now looks like as follow:
tmpfs /newroot tmpfs rw 0 0
/dev/hdd /newroot/mnt/cdrom iso9660 ro 0 0
/dev/loop/0 /newroot/mnt/livecd squashfs ro 0 0
proc /newroot/proc proc rw,nodiratime 0 0
sysfs /newroot/sys sysfs rw 0 0
udev /newroot/dev tmpfs rw,nosuid 0 0
devpts /newroot/dev/pts devpts rw 0 0
cachedir /newroot/mnt/livecd/lib64/splash/cache tmpfs rw 0 0
tmpfs /newroot/mnt/livecd/lib64/splash/tmp tmpfs rw 0 0
tmpfs /newroot/mnt/livecd/lib64/firmware tmpfs rw 0 0
tmpfs /newroot/mnt/livecd/usr/portage tmpfs rw 0 0
usbfs /newroot/proc/bus/usb usbfs rw 0 0
/dev/hda2 / ext3 rw,data=ordered 0 0
/dev/hda1 /boot ext2 rw,nogrpid 0 0
/dev/vg/usr /usr ext3 rw,data=ordered 0 0
/dev/vg/home /home ext3 rw,data=ordered 0 0
/dev/vg/var /var ext3 rw,data=ordered 0 0
/dev/vg/opt /opt ext3 rw,data=ordered 0 0
/dev/vg/tmp /tmp ext3 rw,data=ordered 0 0
none /proc proc rw,nodiratime 0 0
udev /dev tmpfs rw,nosuid 0 0
* end *


"tmpfs /newroot" not created during booting.

I think following warning is critical;
device-mapper : dm-linear : Device lookup failed
device-mapper : error adding target to table

Any advice???  TIA

B.R.
SL




--- Stephen Liu <satimis@×××××.com> wrote:

> Hi Jean-Marc,
>
> > Do you follow the installation guide from gentoo.org?
>
> There are several documents on Gentoo website.  I followed 2
> documents:
>
> Partitioning HD with LVM
> Gentoo LVM2 installation
> http://www.gentoo.org/doc/en/lvm2.xml
>
> Installation
> Gentoo Linux AMD64 Handbook
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml
>
>
> > I mean, do you use a
> > "standard" scheme?
>
> I made some adjustment for my case.  I did not emerge LVM2.
>
> If fail again.  I'll run a final test according their HD config (w/o
> slave), not running LVM.
>
> B.R.
> SL
>
>
>
> >
> >
> > On 9/5/06, Stephen Liu <satimis@×××××.com> wrote:
> > >
> > > Hi Neil,
> > >
> > > > /usr/src contains the source to the kernel (as you'd expect
> form
> > the
> > > > name). The actual kernels live in /boot, this is the version
> that
> > > > must
> > > > match.
> > >
> > > Gentoo started booting after changing following line;
> > > kernel (hd0,0)/boot/kernel-2.6.17-gentoo-r7  root=/dev/hda2
> > > to
> > > kernel (hd0,0)/boot/linux-2.6.17-gentoo-r7  root=/dev/hda2
> > >
> > > But still having following problems;
> > >
> > >
> > > 1)
> > > Engine: Unable to open the engine block file
> /var/lock/evms-engine
> > :
> > > Read only filesystem.  The engine is not protected against other
> > > instances of the Engine being opened at the same time.  Error
> > returned
> > > from evms_commit_changes ( ) : No such device [!!]
> > >
> > >
> > > 2)
> > > Loading module 3c59x ....
> > > Failed to load 3c59x  [!!]
> > >
> > >
> > > 3)
> > > All
> > > /dev/vg/usr
> > > /dev/vg/home
> > > /dev/vg/opt
> > > /dev/vg/var
> > > /dev/vg/tmp
> > >
> > > have same problem as listed follow;
> > > e2fsck: No such file or directory which trying to open
> /dev/vg/usr.
> > > The super block could not be read or does not describe a correct
> > ext2
> > > filesystem.  If the device is valid and it really contains an
> ext2
> > > filesystem (and not swap or ufs or something else).  There the
> > > superblock is corrupt, and your might trying e2fsck with an
> > alternative
> > > superblock :
> > > e2fsck -b 8193
> > >
> > > # e2fsck -b 8193 /dev/vg/usr
> > > fsck.ext3: No such file or directory while trying to open
> > /dev/vg/usr
> > >
> > > Please advise how to fix them.  TIA
> > >
> > > B.R.
> > > SL
> > > --
> > > gentoo-user@g.o mailing list
> > >
> > >
> >
> >
> > --
> > /JM
> >
>
> --
> gentoo-user@g.o mailing list
>
>

-- 
gentoo-user@g.o mailing list