Debian update fails with “Raid version incompatibleâ€
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
While installing proftpd, it dropped with following error:
[....] Starting ftp server: proftpdhexadecacordis proftpd[26849]: mod_tls_memcache/0.1: notice: unable to register 'memcache' SSL session cache: Memcache support not enabled
. ok
Setting up proftpd-mod-vroot (0.9.2-2+b2) ...
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I first did not notice linux-image-3.2.0-4-amd64 error, so I tried to set up libmemcache, and it dropped with same error.
So, I ran an upgrade, and everything updated, except following. So I ran it again, to display clear view of error:
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
xserver-xorg-input-all
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-runlilo 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Warning: LBA32 addressing assumed
Fatal: Incompatible Raid version information on /dev/md0 (RV=0.90 GAI=1.2)
run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-amd64.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I can't find any solution connected with "Incompatible Raid version information".
Please, explain me how to solve this problem.
debian raid
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
asked Sep 16 '13 at 13:16
Deele
173119
add a comment |Â
up vote
1
down vote
favorite
While installing proftpd, it dropped with following error:
[....] Starting ftp server: proftpdhexadecacordis proftpd[26849]: mod_tls_memcache/0.1: notice: unable to register 'memcache' SSL session cache: Memcache support not enabled
. ok
Setting up proftpd-mod-vroot (0.9.2-2+b2) ...
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I first did not notice linux-image-3.2.0-4-amd64 error, so I tried to set up libmemcache, and it dropped with same error.
So, I ran an upgrade, and everything updated, except following. So I ran it again, to display clear view of error:
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
xserver-xorg-input-all
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-runlilo 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Warning: LBA32 addressing assumed
Fatal: Incompatible Raid version information on /dev/md0 (RV=0.90 GAI=1.2)
run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-amd64.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I can't find any solution connected with "Incompatible Raid version information".
Please, explain me how to solve this problem.
debian raid
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
asked Sep 16 '13 at 13:16
Deele
173119
Actually, there are quite a few Google hits when searching "Fatal: Incompatible Raid version information on /dev/md0" . It seems you're using lilo as a bootloader (any special reason?) and your problem is soft RAID + lilo - specific. If you want to continue using lilo, please paste the output of# mdadm -E /dev/md0and we'll take it from there.
– schaiba
Sep 16 '13 at 13:32
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
While installing proftpd, it dropped with following error:
[....] Starting ftp server: proftpdhexadecacordis proftpd[26849]: mod_tls_memcache/0.1: notice: unable to register 'memcache' SSL session cache: Memcache support not enabled
. ok
Setting up proftpd-mod-vroot (0.9.2-2+b2) ...
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I first did not notice linux-image-3.2.0-4-amd64 error, so I tried to set up libmemcache, and it dropped with same error.
So, I ran an upgrade, and everything updated, except following. So I ran it again, to display clear view of error:
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
xserver-xorg-input-all
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-runlilo 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Warning: LBA32 addressing assumed
Fatal: Incompatible Raid version information on /dev/md0 (RV=0.90 GAI=1.2)
run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-amd64.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I can't find any solution connected with "Incompatible Raid version information".
Please, explain me how to solve this problem.
debian raid
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
asked Sep 16 '13 at 13:16
Deele
173119
While installing proftpd, it dropped with following error:
[....] Starting ftp server: proftpdhexadecacordis proftpd[26849]: mod_tls_memcache/0.1: notice: unable to register 'memcache' SSL session cache: Memcache support not enabled
. ok
Setting up proftpd-mod-vroot (0.9.2-2+b2) ...
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I first did not notice linux-image-3.2.0-4-amd64 error, so I tried to set up libmemcache, and it dropped with same error.
So, I ran an upgrade, and everything updated, except following. So I ran it again, to display clear view of error:
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
xserver-xorg-input-all
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up linux-image-3.2.0-4-amd64 (3.2.46-1+deb7u1) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postinst.d/zz-runlilo 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Warning: LBA32 addressing assumed
Fatal: Incompatible Raid version information on /dev/md0 (RV=0.90 GAI=1.2)
run-parts: /etc/kernel/postinst.d/zz-runlilo exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.2.0-4-amd64.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-3.2.0-4-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I can't find any solution connected with "Incompatible Raid version information".
Please, explain me how to solve this problem.
debian raid
debian raid
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
asked Sep 16 '13 at 13:16
Deele
173119
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
asked Sep 16 '13 at 13:16
Deele
173119
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
edited Aug 21 at 3:02
Rui F Ribeiro
36.7k1271116
36.7k1271116
asked Sep 16 '13 at 13:16
Deele
173119
asked Sep 16 '13 at 13:16
Deele
173119
asked Sep 16 '13 at 13:16
Deele
173119
173119
Actually, there are quite a few Google hits when searching "Fatal: Incompatible Raid version information on /dev/md0" . It seems you're using lilo as a bootloader (any special reason?) and your problem is soft RAID + lilo - specific. If you want to continue using lilo, please paste the output of# mdadm -E /dev/md0and we'll take it from there.
– schaiba
Sep 16 '13 at 13:32
add a comment |Â
Actually, there are quite a few Google hits when searching "Fatal: Incompatible Raid version information on /dev/md0" . It seems you're using lilo as a bootloader (any special reason?) and your problem is soft RAID + lilo - specific. If you want to continue using lilo, please paste the output of# mdadm -E /dev/md0and we'll take it from there.
– schaiba
Sep 16 '13 at 13:32
Actually, there are quite a few Google hits when searching "Fatal: Incompatible Raid version information on /dev/md0" . It seems you're using lilo as a bootloader (any special reason?) and your problem is soft RAID + lilo - specific. If you want to continue using lilo, please paste the output of
# mdadm -E /dev/md0 and we'll take it from there.– schaiba
Sep 16 '13 at 13:32
Actually, there are quite a few Google hits when searching "Fatal: Incompatible Raid version information on /dev/md0" . It seems you're using lilo as a bootloader (any special reason?) and your problem is soft RAID + lilo - specific. If you want to continue using lilo, please paste the output of
# mdadm -E /dev/md0 and we'll take it from there.– schaiba
Sep 16 '13 at 13:32
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
It appears that you are using LILO to boot, and it does not understand the new mdadm metadata format. You should switch to grub2 instead.
answered Sep 16 '13 at 14:18
psusi
13.2k22439
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
It appears that you are using LILO to boot, and it does not understand the new mdadm metadata format. You should switch to grub2 instead.
answered Sep 16 '13 at 14:18
psusi
13.2k22439
add a comment |Â
up vote
1
down vote
It appears that you are using LILO to boot, and it does not understand the new mdadm metadata format. You should switch to grub2 instead.
answered Sep 16 '13 at 14:18
psusi
13.2k22439
add a comment |Â
up vote
1
down vote
up vote
1
down vote
It appears that you are using LILO to boot, and it does not understand the new mdadm metadata format. You should switch to grub2 instead.
answered Sep 16 '13 at 14:18
psusi
13.2k22439
It appears that you are using LILO to boot, and it does not understand the new mdadm metadata format. You should switch to grub2 instead.
answered Sep 16 '13 at 14:18
psusi
13.2k22439
answered Sep 16 '13 at 14:18
psusi
13.2k22439
answered Sep 16 '13 at 14:18
psusi
13.2k22439
answered Sep 16 '13 at 14:18
psusi
13.2k22439
13.2k22439
add a comment |Â
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f90880%2fdebian-update-fails-with-raid-version-incompatible%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Actually, there are quite a few Google hits when searching "Fatal: Incompatible Raid version information on /dev/md0" . It seems you're using lilo as a bootloader (any special reason?) and your problem is soft RAID + lilo - specific. If you want to continue using lilo, please paste the output of
# mdadm -E /dev/md0and we'll take it from there.– schaiba
Sep 16 '13 at 13:32