Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #165204 > unrolled thread

LVM disappeared after upgrade in jessie

Started bySebastian Weckend <sebastian.weckend@posteo.de>
First post2016-03-10 13:20 +0100
Last post2016-03-10 15:20 +0100
Articles 5 — 2 participants

Back to article view | Back to linux.debian.user

Contents

  LVM disappeared after upgrade in jessie Sebastian Weckend <sebastian.weckend@posteo.de> - 2016-03-10 13:20 +0100
    Update: LVM disappeared after upgrade in jessie Sebastian Weckend <sebastian.weckend@posteo.de> - 2016-03-10 13:40 +0100
    Re: LVM disappeared after upgrade in jessie Sebastian Weckend <sebastian.weckend@posteo.de> - 2016-03-10 14:00 +0100
      Re: LVM disappeared after upgrade in jessie Dan Ritter <dsr@randomstring.org> - 2016-03-10 14:50 +0100
        Re: LVM disappeared after upgrade in jessie Sebastian Weckend <sebastian.weckend@posteo.de> - 2016-03-10 15:20 +0100

#165204 — LVM disappeared after upgrade in jessie

FromSebastian Weckend <sebastian.weckend@posteo.de>
Date2016-03-10 13:20 +0100
SubjectLVM disappeared after upgrade in jessie
Message-ID<rb7Jn-6ST-9@gated-at.bofh.it>
Hello,

after the last upgrade and rebooting I lost my LVM Container.

following packets were upgraded:

bind9-host 1:9.9.5.dfsg-9+deb8u6
dnsutils 1:9.9.5.dfsg-9+deb8u6
host 1:9.9.5.dfsg-9+deb8u6
libbind9-90 1:9.9.5.dfsg-9+deb8u6
libdns100 1:9.9.5.dfsg-9+deb8u6
libdns-export100 1:9.9.5.dfsg-9+deb8u6
libirs-export91 1:9.9.5.dfsg-9+deb8u6
libisc95 1:9.9.5.dfsg-9+deb8u6
libisccc90 1:9.9.5.dfsg-9+deb8u6
libisccfg90 1:9.9.5.dfsg-9+deb8u6
libisccfg-export90 1:9.9.5.dfsg-9+deb8u6
libisc-export95 1:9.9.5.dfsg-9+deb8u6
liblwres90 1:9.9.5.dfsg-9+deb8u6
linux-image-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u4
xen-linux-system-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u4

# pvscan
   No matching physical volumes found

It seems the software-raid of the PV cannot be found anymore

Any ideas how to get access to the LVM back? Or what else to check? It 
seems still to be on sda7 and sdb7. Unfortunately I dont have access to 
my documentation to check how I configured the LVM in the first place.

# fdisk -l
Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 592AB453-29D1-4BAE-B799-6A66EDFCCE98

Device        Start        End    Sectors  Size Type
/dev/sdb1      4096   16781311   16777216    8G Linux RAID
/dev/sdb2  16781312   17829887    1048576  512M Linux RAID
/dev/sdb3  17829888   38801407   20971520   10G Linux RAID
/dev/sdb4  38801408   59772927   20971520   10G Linux RAID
/dev/sdb5  59772928   61870079    2097152    1G Linux RAID
/dev/sdb6      2048       4095       2048    1M BIOS boot
/dev/sdb7  61870080 5860533134 5798663055  2.7T Linux LVM

Partition table entries are not in disk order.
Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 71504D20-CE2D-499B-B052-76817310B91E

Device        Start        End    Sectors  Size Type
/dev/sda1      4096   16781311   16777216    8G Linux RAID
/dev/sda2  16781312   17829887    1048576  512M Linux RAID
/dev/sda3  17829888   38801407   20971520   10G Linux RAID
/dev/sda4  38801408   59772927   20971520   10G Linux RAID
/dev/sda5  59772928   61870079    2097152    1G Linux RAID
/dev/sda6      2048       4095       2048    1M BIOS boot
/dev/sda7  61870080 5860533134 5798663055  2.7T Linux LVM

Partition table entries are not in disk order.
Disk /dev/md0: 8 GiB, 8585674752 bytes, 16768896 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md1: 511.7 MiB, 536543232 bytes, 1047936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md2: 10 GiB, 10728898560 bytes, 20954880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md3: 10 GiB, 10728898560 bytes, 20954880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/md4: 1023.4 MiB, 1073152000 bytes, 2096000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Thanks, Sebastian

[toc] | [next] | [standalone]

#165205 — Update: LVM disappeared after upgrade in jessie

FromSebastian Weckend <sebastian.weckend@posteo.de>
Date2016-03-10 13:40 +0100
SubjectUpdate: LVM disappeared after upgrade in jessie
Message-ID<rb82J-71L-5@gated-at.bofh.it>
In reply to#165204
In the backup of the LVM configuration I found

physical_volumes {
	pv0 {
		id = "zKO1Xq-VGmI-nX8P-Rwh3-wiFn-GuD4-26dAoZ"
		device = "/dev/md127"   # Hint only
		status = ["ALLOCATABLE"]
		flags = []
		dev_size = 5798400896   # 2.70009 Terabytes
		pe_start = 2048
		pe_count = 707812       # 2.70009 Terabytes
	}
}

but there is no /dev/md127. So it seems it is a software-raid problem.

Did I configure the software-raid wrong? And why did it disappear just 
now? Any idea how I get the partition back?


Am 10.03.2016 um 12:56 schrieb Sebastian Weckend:
> Hello,
>
> after the last upgrade and rebooting I lost my LVM Container.
>
> following packets were upgraded:
>
> bind9-host 1:9.9.5.dfsg-9+deb8u6
> dnsutils 1:9.9.5.dfsg-9+deb8u6
> host 1:9.9.5.dfsg-9+deb8u6
> libbind9-90 1:9.9.5.dfsg-9+deb8u6
> libdns100 1:9.9.5.dfsg-9+deb8u6
> libdns-export100 1:9.9.5.dfsg-9+deb8u6
> libirs-export91 1:9.9.5.dfsg-9+deb8u6
> libisc95 1:9.9.5.dfsg-9+deb8u6
> libisccc90 1:9.9.5.dfsg-9+deb8u6
> libisccfg90 1:9.9.5.dfsg-9+deb8u6
> libisccfg-export90 1:9.9.5.dfsg-9+deb8u6
> libisc-export95 1:9.9.5.dfsg-9+deb8u6
> liblwres90 1:9.9.5.dfsg-9+deb8u6
> linux-image-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u4
> xen-linux-system-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u4
>
> # pvscan
>    No matching physical volumes found
>
> It seems the software-raid of the PV cannot be found anymore
>
> Any ideas how to get access to the LVM back? Or what else to check? It
> seems still to be on sda7 and sdb7. Unfortunately I dont have access to
> my documentation to check how I configured the LVM in the first place.
>
> # fdisk -l
> Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 592AB453-29D1-4BAE-B799-6A66EDFCCE98
>
> Device        Start        End    Sectors  Size Type
> /dev/sdb1      4096   16781311   16777216    8G Linux RAID
> /dev/sdb2  16781312   17829887    1048576  512M Linux RAID
> /dev/sdb3  17829888   38801407   20971520   10G Linux RAID
> /dev/sdb4  38801408   59772927   20971520   10G Linux RAID
> /dev/sdb5  59772928   61870079    2097152    1G Linux RAID
> /dev/sdb6      2048       4095       2048    1M BIOS boot
> /dev/sdb7  61870080 5860533134 5798663055  2.7T Linux LVM
>
> Partition table entries are not in disk order.
> Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 71504D20-CE2D-499B-B052-76817310B91E
>
> Device        Start        End    Sectors  Size Type
> /dev/sda1      4096   16781311   16777216    8G Linux RAID
> /dev/sda2  16781312   17829887    1048576  512M Linux RAID
> /dev/sda3  17829888   38801407   20971520   10G Linux RAID
> /dev/sda4  38801408   59772927   20971520   10G Linux RAID
> /dev/sda5  59772928   61870079    2097152    1G Linux RAID
> /dev/sda6      2048       4095       2048    1M BIOS boot
> /dev/sda7  61870080 5860533134 5798663055  2.7T Linux LVM
>
> Partition table entries are not in disk order.
> Disk /dev/md0: 8 GiB, 8585674752 bytes, 16768896 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md1: 511.7 MiB, 536543232 bytes, 1047936 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md2: 10 GiB, 10728898560 bytes, 20954880 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md3: 10 GiB, 10728898560 bytes, 20954880 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md4: 1023.4 MiB, 1073152000 bytes, 2096000 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Thanks, Sebastian
>

[toc] | [prev] | [next] | [standalone]

#165206

FromSebastian Weckend <sebastian.weckend@posteo.de>
Date2016-03-10 14:00 +0100
Message-ID<rb8m7-78l-31@gated-at.bofh.it>
In reply to#165204
In the backup of the LVM configuration I found

physical_volumes {
     pv0 {
         id = "zKO1Xq-VGmI-nX8P-Rwh3-wiFn-GuD4-26dAoZ"
         device = "/dev/md127"   # Hint only
         status = ["ALLOCATABLE"]
         flags = []
         dev_size = 5798400896   # 2.70009 Terabytes
         pe_start = 2048
         pe_count = 707812       # 2.70009 Terabytes
     }
}

but there is no /dev/md127. So it seems it is a software-raid problem.

Did I configure the software-raid wrong? And why did it disappear just 
now? Any idea how I get the partition back?


Am 10.03.2016 um 12:56 schrieb Sebastian Weckend:
> Hello,
>
> after the last upgrade and rebooting I lost my LVM Container.
>
> following packets were upgraded:
>
> bind9-host 1:9.9.5.dfsg-9+deb8u6
> dnsutils 1:9.9.5.dfsg-9+deb8u6
> host 1:9.9.5.dfsg-9+deb8u6
> libbind9-90 1:9.9.5.dfsg-9+deb8u6
> libdns100 1:9.9.5.dfsg-9+deb8u6
> libdns-export100 1:9.9.5.dfsg-9+deb8u6
> libirs-export91 1:9.9.5.dfsg-9+deb8u6
> libisc95 1:9.9.5.dfsg-9+deb8u6
> libisccc90 1:9.9.5.dfsg-9+deb8u6
> libisccfg90 1:9.9.5.dfsg-9+deb8u6
> libisccfg-export90 1:9.9.5.dfsg-9+deb8u6
> libisc-export95 1:9.9.5.dfsg-9+deb8u6
> liblwres90 1:9.9.5.dfsg-9+deb8u6
> linux-image-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u4
> xen-linux-system-3.16.0-4-amd64 3.16.7-ckt20-1+deb8u4
>
> # pvscan
>    No matching physical volumes found
>
> It seems the software-raid of the PV cannot be found anymore
>
> Any ideas how to get access to the LVM back? Or what else to check? It
> seems still to be on sda7 and sdb7. Unfortunately I dont have access to
> my documentation to check how I configured the LVM in the first place.
>
> # fdisk -l
> Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 592AB453-29D1-4BAE-B799-6A66EDFCCE98
>
> Device        Start        End    Sectors  Size Type
> /dev/sdb1      4096   16781311   16777216    8G Linux RAID
> /dev/sdb2  16781312   17829887    1048576  512M Linux RAID
> /dev/sdb3  17829888   38801407   20971520   10G Linux RAID
> /dev/sdb4  38801408   59772927   20971520   10G Linux RAID
> /dev/sdb5  59772928   61870079    2097152    1G Linux RAID
> /dev/sdb6      2048       4095       2048    1M BIOS boot
> /dev/sdb7  61870080 5860533134 5798663055  2.7T Linux LVM
>
> Partition table entries are not in disk order.
> Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identifier: 71504D20-CE2D-499B-B052-76817310B91E
>
> Device        Start        End    Sectors  Size Type
> /dev/sda1      4096   16781311   16777216    8G Linux RAID
> /dev/sda2  16781312   17829887    1048576  512M Linux RAID
> /dev/sda3  17829888   38801407   20971520   10G Linux RAID
> /dev/sda4  38801408   59772927   20971520   10G Linux RAID
> /dev/sda5  59772928   61870079    2097152    1G Linux RAID
> /dev/sda6      2048       4095       2048    1M BIOS boot
> /dev/sda7  61870080 5860533134 5798663055  2.7T Linux LVM
>
> Partition table entries are not in disk order.
> Disk /dev/md0: 8 GiB, 8585674752 bytes, 16768896 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md1: 511.7 MiB, 536543232 bytes, 1047936 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md2: 10 GiB, 10728898560 bytes, 20954880 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md3: 10 GiB, 10728898560 bytes, 20954880 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk /dev/md4: 1023.4 MiB, 1073152000 bytes, 2096000 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Thanks, Sebastian
>

[toc] | [prev] | [next] | [standalone]

#165208

FromDan Ritter <dsr@randomstring.org>
Date2016-03-10 14:50 +0100
Message-ID<rb98u-7FW-17@gated-at.bofh.it>
In reply to#165206
On Thu, Mar 10, 2016 at 01:37:06PM +0100, Sebastian Weckend wrote:
> In the backup of the LVM configuration I found
> 
> physical_volumes {
>     pv0 {
>         id = "zKO1Xq-VGmI-nX8P-Rwh3-wiFn-GuD4-26dAoZ"
>         device = "/dev/md127"   # Hint only
>         status = ["ALLOCATABLE"]
>         flags = []
>         dev_size = 5798400896   # 2.70009 Terabytes
>         pe_start = 2048
>         pe_count = 707812       # 2.70009 Terabytes
>     }
> }
> 
> but there is no /dev/md127. So it seems it is a software-raid problem.
> 
> Did I configure the software-raid wrong? And why did it disappear
> just now? Any idea how I get the partition back?


Does it appear in /proc/mdstat in any form? I suspect that the
device got renamed.

Any mentions of mdadm in dmesg output?

You can examine specific partitions with mdadm -Q /dev/sdXX

-dsr-

[toc] | [prev] | [next] | [standalone]

#165210

FromSebastian Weckend <sebastian.weckend@posteo.de>
Date2016-03-10 15:20 +0100
Message-ID<rb9Bw-85J-9@gated-at.bofh.it>
In reply to#165208
I found the problem, here is what happened:

When first creating the raid partition for the lvm, I saved the config 
to /etc/mdadm.conf

Everything worked fine, because somehow it still got detected and was 
assembled as md127. I didnt notice and went on.

It seems that after an update (not shure which) it does not do the 
automated search and assembling of the unconfigured raid partitions 
anymore. I put the missing configuration in /etc/mdadm/mdadm.conf and 
everything is fine again.

thanks, Sebastian


Am 10.03.2016 um 14:43 schrieb Dan Ritter:
> On Thu, Mar 10, 2016 at 01:37:06PM +0100, Sebastian Weckend wrote:
>> In the backup of the LVM configuration I found
>>
>> physical_volumes {
>>      pv0 {
>>          id = "zKO1Xq-VGmI-nX8P-Rwh3-wiFn-GuD4-26dAoZ"
>>          device = "/dev/md127"   # Hint only
>>          status = ["ALLOCATABLE"]
>>          flags = []
>>          dev_size = 5798400896   # 2.70009 Terabytes
>>          pe_start = 2048
>>          pe_count = 707812       # 2.70009 Terabytes
>>      }
>> }
>>
>> but there is no /dev/md127. So it seems it is a software-raid problem.
>>
>> Did I configure the software-raid wrong? And why did it disappear
>> just now? Any idea how I get the partition back?
>
>
> Does it appear in /proc/mdstat in any form? I suspect that the
> device got renamed.
>
> Any mentions of mdadm in dmesg output?
>
> You can examine specific partitions with mdadm -Q /dev/sdXX
>
> -dsr-
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web