Re: Problem with LVM on fresh Sarge installation

[Benedict Verheyen <benedict.verheyen@sjki.be>]

Benedict Verheyen wrote:

> > I start it manually after login to system (line "/dev/mapper/SYSTEM-HOME
> > /opt            ext3    defaults        0       2" in /etc/fstab is
> > deleted).
> >
> >
> > twiki:~# /etc/init.d/lvm start
> > Setting up LVM Volume Groups...
> >  Reading all physical volumes.  This may take a while...
> >  Found volume group "SYSTEM" using metadata type lvm2
> >  4 logical volume(s) in volume group "SYSTEM" now active
> > twiki:~# vgdisplay
> >  --- Volume group ---
> >  VG Name               SYSTEM
> >  System ID
> >  Format                lvm2
> >  Metadata Areas        1
> >  Metadata Sequence No  9
> >  VG Access             read/write
> >  VG Status             resizable
> >  MAX LV                0
> >  Cur LV                4
> >  Open LV               0
> >  Max PV                0
> >  Cur PV                1
> >  Act PV                1
> >  VG Size               37.25 GB
> >  PE Size               4.00 MB
> >  Total PE              9536
> >  Alloc PE / Size       9536 / 37.25 GB
> >  Free  PE / Size       0 / 0
> >  VG UUID               dKWH4d-fe1l-S5cf-x76v-lIhr-lTHy-CvRrW5
> > twiki:~# lvdisplay
> >  --- Logical volume ---
> >  LV Name                /dev/SYSTEM/HOME
> >  VG Name                SYSTEM
> >  LV UUID                pjOqOX-WbX9-qpxP-5NS3-2cyO-UbMD-ZJVN86
> >  LV Write Access        read/write
> >  LV Status              available
> >  # open                 0
> >  LV Size                10.00 GB
> >  Current LE             2560
> >  Segments               1
> >  Allocation             inherit
> >  Read ahead sectors     0
> >  Block device           254:0
> >
> >  --- Logical volume ---
> >  LV Name                /dev/SYSTEM/USR
> >  VG Name                SYSTEM
> >  LV UUID                elD16s-SgVP-M6nd-m5e2-mcL9-g1ei-MTaVQk
> >  LV Write Access        read/write
> >  LV Status              available
> >  # open                 0
> >  LV Size                5.00 GB
> >  Current LE             1280
> >  Segments               1
> >  Allocation             inherit
> >  Read ahead sectors     0
> >  Block device           254:1
> >
> >  --- Logical volume ---
> >  LV Name                /dev/SYSTEM/VAR
> >  VG Name                SYSTEM
> >  LV UUID                lofDQh-23Tc-s195-2NiE-oZeh-m5oH-9JYtod
> >  LV Write Access        read/write
> >  LV Status              available
> >  # open                 0
> >  LV Size                18.00 GB
> >  Current LE             4608
> >  Segments               1
> >  Allocation             inherit
> >  Read ahead sectors     0
> >  Block device           254:2
> >
> >  --- Logical volume ---
> >  LV Name                /dev/SYSTEM/TMP
> >  VG Name                SYSTEM
> >  LV UUID                KdmMq1-rBQU-5r5b-7aUv-4d7x-UiO8-R23F7b
> >  LV Write Access        read/write
> >  LV Status              available
> >  # open                 0
> >  LV Size                4.25 GB
> >  Current LE             1088
> >  Segments               1
> >  Allocation             inherit
> >  Read ahead sectors     0
> >  Block device           254:3
> >
> >
> > Regards.
> > Jura
My last message seems to have gone wrong so i'll try again. I'm sorry 
for that.
What i said is that i saw that there where people that had to use sata_nv to
get a sata drive working.
From what i can see, it seems that on boot your sata drive is not 
accessible.
I would try once with lsmod to see if there are sata related modules loaded
after your system starts.
Since it all works after the initial boot, i guess the way the system is 
set up,
it can't acces the drive and your sata is ok.
If this is the case, you'll have to find a kernel that support sata 
(built in) or
build your own kernel with sata support of make an initrd with sata in and
adjust grubs menu.lst to load the initrd.

Regards,
Benedict