Page: 1, 2, 3  Next

EricTID
Status: Interested
Joined: 17 Aug 2011
Posts: 13
Back to top
Posted: Aug 18, 11, 0:27    Liquorix 3.0-1 doesn't detect my LVM
Hi,

First of all, let me say that I like the Liquorix kernel a lot and never had trouble with it, until today. Earlier this week I got a kernel update from the Debian testing repos to version linux-image-3.0.0-1-amd64 which worked as a charm.

This morning I got an update from Liquorix and I installed linux-image-3.0-1.dmz.3-liquorix-amd64.

After rebooting however with the new Liquorix kernel my LVM /dev/datagroup/data cannot be found and hence is not mounted.

Any ideas on what might be wrong? I suspect it being a bug referring to the kernel number being 3.0 instead of 3.0.0.

All help is highly appreciated.

Kind regards,

Eric
EricTID
Status: Interested
Joined: 17 Aug 2011
Posts: 13
Back to top
Posted: Aug 18, 11, 22:09    Update: Liquorix 3.0-3 problem persists
Hi,

A small update: This morning I installed the newly available 3.0-3 Liquorix kernel. The problem persists. I'm sure it has to do with how the kernel version is mentioned. I also have, as already indicated, kernel 3.0.0-1 installed from Debian testing repos and that one works flawless. When booting Liquorix 3.0-3 I saw the following error:

Could not determine kernel version used

My datagroup gets detected apparently but no LVM partitions, hence I get a failed error message.

Any ideas, workarounds, ....?

Kind regards,

Eric
evilerick
Status: New User - Welcome
Joined: 19 Aug 2011
Posts: 2
Location: Mexico
Back to top
Posted: Aug 19, 11, 5:12    Same problem here
I can confirm the problem. I'm using encrypted LVM on both my notebook and desktop, with the same result. I'm attaching a picture of the error message.

Best regards

techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3477
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Aug 19, 11, 10:12    
Please verify some basic things:

show /etc/fstab

make sure drives are mounted using correct new syntax, best just post the entire contents here so we can look at it.

You want to be sure that no /dev/sdax or /dev/hdax type syntax is used in mounts, only labels or uuid. lmv I don't remember the right syntax for, but let's take a look at yours.

Second, boot into a working kernel, and run:

update-initramfs -u -k <new kernel> (like: 3.0-1.dmz.4-amd64)

Then try rebooting.
evilerick
Status: New User - Welcome
Joined: 19 Aug 2011
Posts: 2
Location: Mexico
Back to top
Posted: Aug 19, 11, 15:26    More info
First of all, my last post was not as clear as it should have been, and I apologize for that. My setup (on a notebook) is as follows:

    1 hard drive, fully encrypted

    1 volume group created from the encrypted volume

    3 logical volumes created from the volume group


A correct boot sequence is:

You can notice the LVM messages, which are normal, because the encrypted volume has not been unlocked. Also there's a prompt for the decryption password.

Returning to the problem, I dist-upgraded today, installing 3.0-3.dmz.1-liquorix-amd64, and the boot messages are somewhat different:

As you can see, dm-mod is not loaded, and the prompt for the decryption password doesn't work at all. The message about the kernel version persists.

In addition, as ErickTID mentioned in his post, both the Debian 3.0.0-1-amd64 and the Liquorix 2.6.39-4.dmz.1-liquorix-amd64 kernels work as expected.

I executed (successfully) the command you suggested, but the problem persists.

My /etc/fstab is:
:: Code ::
proc            /proc           proc    defaults        0       0
/dev/mapper/vg--fs-lv--root /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda1 during installation
UUID=59bc1363-06db-479e-aa5b-630a8c38f126 /boot           ext4    defaults        0       2
/dev/mapper/vg--fs-lv--home /home           ext4    defaults        0       2
/dev/mapper/vg--fs-lv--swap none            swap    sw              0       0
/dev/scd0       /media/cdrom1   udf,iso9660 user,noauto     0       0


# vgdisplay
:: Code ::
  VG Name               vg-fs
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  4
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                3
  Open LV               3
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               595.93 GiB
  PE Size               4.00 MiB
  Total PE              152558
  Alloc PE / Size       152558 / 595.93 GiB
  Free  PE / Size       0 / 0   
  VG UUID               k3B5Af-GqCk-GgfL-P2Eb-lAnC-ipYT-tLOo28


# lvdisplay
:: Code ::
  --- Logical volume ---
  LV Name                /dev/vg-fs/lv-swap
  VG Name                vg-fs
  LV UUID                c5IRKE-NnWt-cIh4-4mTQ-qaWG-uqKf-FwZ9ho
  LV Write Access        read/write
  LV Status              available
  # open                 2
  LV Size                3.72 GiB
  Current LE             953
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:1
   
  --- Logical volume ---
  LV Name                /dev/vg-fs/lv-root
  VG Name                vg-fs
  LV UUID                2fP4Yk-7fZq-anLO-3mFV-QDju-dZZX-hZAX51
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                18.62 GiB
  Current LE             4768
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:2
   
  --- Logical volume ---
  LV Name                /dev/vg-fs/lv-home
  VG Name                vg-fs
  LV UUID                u2d8sz-ZlX2-AskF-mTof-RkaI-B5Me-HW5XoI
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                573.58 GiB
  Current LE             146837
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:3


Thanks a lot for your help. And, specially thanks a lot for Liquorix.

Best regards
EricTID
Status: Interested
Joined: 17 Aug 2011
Posts: 13
Back to top
Posted: Aug 22, 11, 22:12    Problem persisting
Hi,

Thanks for the replies and help. I also have tried your suggestions. Here's my fstab and related info. Everything works as expected using the 3.0.0 kernel from the Debian repos but the Liquorix kernel seems to have a problem with LVM.

:: Code ::
eric@ericvs-laptop ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=385ecae6-bd34-41c3-a524-974b8cd6d17f /               ext3    errors=remount-ro,user_xattr 0       1
# swap was on /dev/sda2 during installation
UUID=c6876978-438f-4a1e-ae53-dacdf22d1e4a none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
proc   /proc   proc   nodev,noexec,nosuid   0   0
# /dev/sda5   swap   swap   sw   0   0
UUID=b052ca42-42e0-4017-8ab1-3749bfbc5d95   swap   swap   sw   0   0
# /dev/sda1   /boot   ext3   rw,errors=remount-ro   0   0
UUID=cb352e77-ac0b-4ac3-81b3-4c5c26ae2cdb   /boot   ext3   rw,errors=remount-ro   0   0
# /dev/sda2   /   ext4   rw,errors=remount-ro   0   0
UUID=c6f6a925-1180-4a18-bc19-45e9ccb9740a   /   ext4   rw,errors=remount-ro,user_xattr   0   0
# DATA Share LVM2
#/dev/datagroup/data   /home/eric/DATA   ext4   rw,user   0   0
UUID=25fcac10-e659-4964-ad27-688694c23b51   /home/eric/DATA   ext4   rw,user   0   0
eric@ericvs-laptop ~ $ mount
/dev/sda2 on / type ext4 (rw,errors=remount-ro,user_xattr,commit=0)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,size=5242880,mode=755,size=5242880,mode=755)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=755,size=10%,mode=755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,size=20%,mode=1777,size=20%,mode=1777)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw,errors=remount-ro,commit=0)
/dev/mapper/datagroup-data on /home/eric/DATA type ext4 (rw,noexec,nosuid,nodev,commit=0)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
cgroup on /dev/cgroup/cpu type cgroup (rw,cpu)
eric@ericvs-laptop ~ $ uname -a
Linux ericvs-laptop 3.0.0-1-amd64 #1 SMP Sun Jul 24 02:24:44 UTC 2011 x86_64 GNU/Linux
eric@ericvs-laptop ~ $

:: Code ::

eric@ericvs-laptop ~ $ sudo vgdisplay
  --- Volume group ---
  VG Name               datagroup
  System ID             
  Format                lvm2
  Metadata Areas        1
  Metadata Sequence No  2
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                1
  Open LV               1
  Max PV                0
  Cur PV                1
  Act PV                1
  VG Size               412.53 GiB
  PE Size               4.00 MiB
  Total PE              105608
  Alloc PE / Size       64000 / 250.00 GiB
  Free  PE / Size       41608 / 162.53 GiB
  VG UUID               RSwkWM-fZl6-TRJ9-6Uui-7KKi-gkLu-H0IixM
   
eric@ericvs-laptop ~ $ sudo lvdisplay
  --- Logical volume ---
  LV Name                /dev/datagroup/data
  VG Name                datagroup
  LV UUID                KvVIyA-xhTQ-Gxms-L0Cp-9usD-k7Je-GuhnVZ
  LV Write Access        read/write
  LV Status              available
  # open                 1
  LV Size                250.00 GiB
  Current LE             64000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           254:0

In my case the update-initramfs executed without errors but rebooting in the kernel gave the same error.

Kind regards,

Eric
EricTID
Status: Interested
Joined: 17 Aug 2011
Posts: 13
Back to top
Posted: Aug 22, 11, 23:33    Latest update, problem persists
Hi,

Just installed the latest update from today but the problem mentioned persists.

Kind regards,

Eric
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3477
Location: East Coast, West Coast? I know it's one of them.
Back to top
Posted: Aug 23, 11, 9:49    
EricTID, this is unrelated to this problem, but you have a fairly unique system, and it would be useful to get that data for inxi for partitions.

Could you do me a favor, install / update inxi (inxi -U) to latest version, then run:

inxi -xx@ 14

this will create a system data dump and then upload it to the inxi dev server, this data will let me check and tweak some settings in inxi for your type of system.
EricTID
Status: Interested
Joined: 17 Aug 2011
Posts: 13
Back to top
Posted: Aug 23, 11, 9:58    Unrelated
Hi,

Thanks for your reply. In what way is this unrelated to this problem since I opened the thread indicating this behavior? Or are you referring to the solution offered? Could you please elaborate? I ran inxi as indicated by you but got this error:
:: Code ::

eric@ericvs-laptop ~ $ inxi -xx@ 14
Error 9: unsupported debugging level: 14

Some more information derived from inxi:
:: Code ::

eric@ericvs-laptop ~ $ inxi help
CPU[-Dual core Intel Core i3 M 380 (-HT-MCP-) clocked at Min:933.000Mhz Max:2533.000Mhz-] Kernel[-3.0.0-1-amd64 x86_64-] Up[-12:01-] Mem[-918.6/3765.3MB-] HDD[-500.1GB(31.2% used)-] Procs[-171-] Client[-Shell-] inxi[-1.4.23-]


Kind regards,

Eric
EricTID
Status: Interested
Joined: 17 Aug 2011
Posts: 13
Back to top
Posted: Aug 23, 11, 10:25    Inxi success
Hi,

Got inxi to work, sorry for the 'noob' mistake of not updating inxi first. Took me an entire 15 minutes to figure that one out.
<edited out unnecessary output data - admin>

Thanks for your help.

Kind regards,

Eric
Display posts from previous:   
Page: 1, 2, 3  Next
All times are GMT - 8 Hours