Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure
> If I find time I'll have a look at this (probably just by looking > through GRUB 2 for candidate backports and hoping that one of them > helps). However, I should warn you that GRUB Legacy is extremely very > unmaintained at this point; I've really just been doing last-resort > patching for years, and this normally hasn't included debugging its > filesystem code. It'd be in your interests to migrate to GRUB 2. Thanks for your response - I hadn't quite noticed that this was legacy grub (and had kinda made the assumption the Debian upgrades had forced the upgrade). I have migrated to GRUB 2 and can confirm this resolves the issue. cheers, Dan The Networking People (TNP) Limited. Registered office: Network House, Caton Rd, Lancaster, LA1 3PE. Registered in England & Wales with company number: 07667393 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure
Package: src:linux Version: 5.10.216-1 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading to linux-image-5.10.0-29 the system fails to boot with grub 'Error 16: Inconsistent filesystem structure'. Booting into linux-image-5.10.0-28-amd64 and the system is once again bootable The console displays: Booting 'Debian GNU/Linux, kernel 5.10.0-29-amd64' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-5.10.0-29-amd64 root=UUID=ca38e015-f8d1-4ef0-9dc9-b56d7c8 le0f1 ro [Linux-bzImage, setup=0x3c00, size=0x6b5f40] Initrd /boot/initrd. img-5.10.0-29-amd64 Error 16: Inconsistent filesystem structure Press any key to continue...- -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (i440FX + PIIX, 1996) product_version: pc-i440fx-8.1 chassis_vendor: QEMU chassis_version: pc-i440fx-8.1 bios_vendor: SeaBIOS bios_version: rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:05.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio SCSI [1af4:1004] Subsystem: Red Hat, Inc. Virtio SCSI [1af4:0008] Physical Slot: 5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:12.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] Physical Slot: 18 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:13.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] Physical Slot: 19 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:1e.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCI-PCI bridge [1b36:0001] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:1f.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCI-PCI bridge [1b36:0001] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: ** USB devices: not available -- System Information: Debian Release: 11.9 APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-28-amd64 (SMP w/6 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.10.0-29-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.140 ii kmod28-1 ii linux-base 4.6 Versions of packages linux-image-5.10.0-29-amd64 recommends: ii apparmor 2.13.6-10 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.10.0-29-amd64 suggests: pn debian-kernel-handbook pn grub-pc | grub-efi-amd64 | extlinux pn linux-doc-5.10 Versions of packages linux-image-5.10.0-29-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn
Bug#920018: Jessie Fix?
We are seeing this bug on the jessie ( systemd 215-17+deb8u10) and it's extremely serious, leading to systemd-journald eventually consuming all memory on the system. Is there a fix for jessie incoming? The Networking People (NorthWest) Limited. Registered office: c/o Hanleys, Spring Court, Hale, Cheshire, WA14 2UQ. Registered in England & Wales with company number: 07667393 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Bug#821534: moodle: PHP 7.0 Transition
Just a note that Moodle supports PHP7 from version 3.0.1: https://moodle.org/mod/forum/discuss.php?d=325088 -- Dan Poltawski Senior Analyst Developer d...@moodle.com +61894674167 | moodle.com The world's open source learning platform
Bug#754565: Fwd: future of Moodle in Debian stable/unstable (was: Re: [moodle-packaging] Bug#754565: Bug#754565: Bug#754565: Non free icc profile)
Hi Joost, On Wed, Feb 4, 2015 at 8:54 AM, Joost van Baal-Ilić joostvb+moo...@uvt.nl wrote: I am currently working on packaging latest moodle keeping it up to date in Debian unstable, see https://packages.debian.org/sid/moodle and especially http://metadata.ftp-master.debian.org/changelogs//main/m/moodle/moodle_2.7.5+dfsg-1_changelog for what I did. At Tilburg University we are running moodle on some Debian systems; we have an interest in keeping it working for us. I basically took over the work from Thijs. Thank you! Please feel free to get in touch with me if we can be of help. ps. Noting Rileys post on moodle.org was eventually posted here: https://moodle.org/mod/forum/discuss.php?d=278847 cheers, Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754565: [moodle-packaging] Bug#754565: Bug#754565: Non free icc profile
Hi Riley, On 22 January 2015 at 06:34, Riley Baird bm-2cvqnduybau5do2dfjtrn7zbaj246s4...@bitmessage.ch wrote: P.S. I tried writing a message on the moodle forums to give them a heads up on the situation, but the spam filter stopped me. It told me to send my post to he...@moodle.org, so hopefully it will still get through. 'Upstream' here. Apologies that you got hit by a spam filter (I'm afraid we were getting hit quite aggressively by first time link spammers which is probably the cause of your filtering). Thank you very much for trying to get in touch with us. I've been cc'd on the Moodle debian bugs for quite some time and i'm afraid that this is a bit of a cycle with the package. Quite some time ago I was part of a team to keep up with keeping the package in order, but eventually could not keep on top of it - then others like Tomasz Muras and Thijs Kinkhorst have valiantly tried to get it in order. See #494642 #647489 #747084 etc. So much as it saddens me - I think this is the right course of action. There is little evidence to suggest that the package is widely used which makes it even less motivating for contributors for the significant amount of work it takes to keep up with our wide ranging upstream security fixes. cheers, Dan Poltawski -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746594: [moodle-packaging] Bug#746594: Bug#746594: Embedded OLE is not DFSG-compliant (PHP-2.02)
forwarded 746594 https://tracker.moodle.org/browse/MDL-45395 On 2 May 2014 21:50, Thijs Kinkhorst th...@debian.org wrote: It's indeeed a second copy, it's under lib/phpexcel/PHPExcel/Shared/ Thanks! Grr! I've created https://tracker.moodle.org/browse/MDL-45395 cheers, Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746594: [moodle-packaging] Bug#746594: Embedded OLE is not DFSG-compliant (PHP-2.02)
Hi, On 2 May 2014 02:46, David Prévot taf...@debian.org wrote: The embedded PHPExcel copy (#718585) embeds OLE (#487558) which is not DFSG compliant (PHP-2.02)[1,2]. We have removed this library in upstream in version 2.6: https://tracker.moodle.org/browse/MDL-42381 http://git.moodle.org/gw?p=moodle.git;a=commit;h=383d414478f1f3129f243e4d047d4fa06b9a3b8f It wasn't used and can be safely deleted. Is there another instance of this library or is it a packaging problem? cheers, Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692626: non-free files in upstream tarball (The Software shall be used for Good, not Evil)
We have resolved this upstream in version 2.4 (http://tracker.moodle.org/browse/MDL-36457). We will consider back-porting this in http://tracker.moodle.org/browse/MDL-36463 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#581229: [moodle-packaging] Bug#581229: Needs to be actively maintained to be included in Squeeze
On Thu, Jun 24, 2010 at 10:23 PM, Moritz Muehlenhoff j...@inutil.org wrote: I'm reopening this bug for now: It's been now over a week that new Moodle security issues have been reported for which there is no visible action from your side. Plus, you haven't gotten in contact with the Security Team as how to fix the numerous open security bugs in stable. We require better for an application like Moodle. Just for info as it hasn't been mentioned on this bug yet before there is an (relatively recent orphan bug here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574969 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501306: update-grub fails with raid1 boot partition
On Thu, Oct 09, 2008 at 09:27:51PM +0200, Jeroen Dekkers wrote: It might be possible that the names sda to sdd were used for something that wasn't an hard disk during the install (a card reader with 4 different slots might be a good candidate). Then your system would still boot properly with your old device.map because grub detected that sde was the first hard disk, but then you wouldn't be able to run update-grub because your first hard disk is sda now. Could you check this in the installation log or by running the debian installer again to the point where it detects all the disks? You are exactly right! The machine has a 4 slot card reader (as do my collegues who experienced the exact same problem. Looking at the installer log this is exactly what happened. Attached is the relevant part of /var/log/installer/syslog Dan Oct 3 16:43:24 kernel: sd 6:0:0:0: [sda] Attached SCSI removable disk Oct 3 16:43:24 kernel: sd 6:0:0:1: [sdb] Attached SCSI removable disk Oct 3 16:43:24 kernel: sd 6:0:0:2: [sdc] Attached SCSI removable disk Oct 3 16:43:24 kernel: sd 6:0:0:3: [sdd] Attached SCSI removable disk Oct 3 16:43:24 kernel: ata3.00: configured for UDMA/100 Oct 3 16:43:24 kernel: ata4: SATA link down (SStatus 4 SControl 300) Oct 3 16:43:24 kernel: ata5: SATA link down (SStatus 0 SControl 0) Oct 3 16:43:24 kernel: ata6: SATA link down (SStatus 4 SControl 300) Oct 3 16:43:24 kernel: scsi 0:0:0:0: Direct-Access ATA ST3250310AS 4.AD PQ: 0 ANSI: 5 Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] 488281250 512-byte hardware sectors (25 MB) Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Write Protect is off Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Mode Sense: 00 3a 00 00 Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] 488281250 512-byte hardware sectors (25 MB) Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Write Protect is off Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Mode Sense: 00 3a 00 00 Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 3 16:43:24 kernel: sde: sde1 sde2 sde3 Oct 3 16:43:24 kernel: sd 0:0:0:0: [sde] Attached SCSI disk Oct 3 16:43:24 kernel: scsi 1:0:0:0: Direct-Access ATA ST3250310AS 4.AD PQ: 0 ANSI: 5 Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] 488281250 512-byte hardware sectors (25 MB) Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Write Protect is off Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] 488281250 512-byte hardware sectors (25 MB) Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Write Protect is off Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Mode Sense: 00 3a 00 00 Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 3 16:43:24 kernel: sdf: sdf1 Oct 3 16:43:24 kernel: sd 1:0:0:0: [sdf] Attached SCSI disk signature.asc Description: Digital signature
Bug#501306: update-grub fails with raid1 boot partition
On Thu, Oct 09, 2008 at 09:28:56PM +0100, Dan Poltawski wrote: On Thu, Oct 09, 2008 at 09:27:51PM +0200, Jeroen Dekkers wrote: It might be possible that the names sda to sdd were used for something that wasn't an hard disk during the install (a card reader with 4 different slots might be a good candidate). Then your system would still boot properly with your old device.map because grub detected that sde was the first hard disk, but then you wouldn't be able to run update-grub because your first hard disk is sda now. Could you check this in the installation log or by running the debian installer again to the point where it detects all the disks? You are exactly right! The machine has a 4 slot card reader (as do my collegues who experienced the exact same problem. Looking at the installer log this is exactly what happened. Attached is the relevant part of /var/log/installer/syslog And here is dmesg output of currently running system (they have indeed swapped since the installer): [ 13.029040] scsi 6:0:0:0: Direct-Access TEAC USB HS-CF Card 4.08 PQ: 0 ANSI: 0 [ 13.030753] scsi 6:0:0:1: Direct-Access TEAC USB HS-xD/SM 4.08 PQ: 0 ANSI: 0 [ 13.039924] scsi 6:0:0:2: Direct-Access TEAC USB HS-MS Card 4.08 PQ: 0 ANSI: 0 [ 13.042754] scsi 6:0:0:3: Direct-Access TEAC USB HS-SD Card 4.08 PQ: 0 ANSI: 0 [ 13.048067] sd 6:0:0:0: [sdc] Attached SCSI removable disk [ 13.048131] sd 6:0:0:0: Attached scsi generic sg3 type 0 [ 13.053311] sd 6:0:0:1: [sdd] Attached SCSI removable disk [ 13.053373] sd 6:0:0:1: Attached scsi generic sg4 type 0 [ 13.058303] sd 6:0:0:2: [sde] Attached SCSI removable disk [ 13.058365] sd 6:0:0:2: Attached scsi generic sg5 type 0 [ 13.062752] sd 6:0:0:3: [sdf] Attached SCSI removable disk [ 13.062752] sd 6:0:0:3: Attached scsi generic sg6 type 0 Dan signature.asc Description: Digital signature
Bug#501306: update-grub fails with raid1 boot partition
On Wed, Oct 08, 2008 at 01:35:53AM -0400, Samat K Jain wrote: On Tuesday 07 October 2008 04:53:57 am Dan Poltawski wrote: Just in response to this - my problem has not been caused by an upgrade - it was a clean lenny install onto a new machine a few days ago. Well, something regenerated device.map since installation. I don't think your system would boot with the device.map you've provided---grub would have ever installed properly. I believe, from what you've provided, your device.map should contain: (hd0) /dev/sda (hd1) /dev/sdb Did you try the workaround? Namely running `grub-mkdevicemap --no-floppy` again? Yes I did, this does resolve the problem and also contains the same map as you guessed at. I'm looking through the apt log to see if I can find anything which would regenerate the device.map since install. Dan signature.asc Description: Digital signature
Bug#501306: update-grub fails with raid1 boot partition
Hi, (sorry for second mail - didn't send to bug) On Mon, Oct 06, 2008 at 07:18:08PM +0200, Felix Zielcke wrote: Am Montag, den 06.10.2008, 19:02 +0200 schrieb Felix Zielcke: If you do `grub-install /dev/sda' then it should be in your device.map. Either run grub-mkdevicemap --no-floppy or grub-install with `--recheck --no-floppy'. Urm I forgot somehow that you're talking about update-grub not grub-install. But somewhere /dev/sda has to come from which isn't visible on the report. Is your /dev/md0 over sda or something like that? Yes, md0 is over sda1 and sdb1: [EMAIL PROTECTED]:~$ cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sdb3[1] sda3[0] 241207872 blocks [2/2] [UU] md1 : active (auto-read-only) raid1 sda2[0] sdb2[1] 1951808 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 979840 blocks [2/2] [UU] During some previous upgrade, /boot/grub/device.map was regenerated, and it was missing some of the devices that made up the boot RAID array. Just in response to this - my problem has not been caused by an upgrade - it was a clean lenny install onto a new machine a few days ago. Thanks, Dan signature.asc Description: Digital signature
Bug#501306: update-grub fails with raid1 boot partition
Package: grub
Version: 0.97-47
Severity: critical
Justification: breaks unrelated software
When installing new kernels onto the system, the kernel package post
instalation fails on update-grub (output attached below), this
problem has also affected a number of my collegues, all of us have
a raid1 configuration on our boot partition.
I tried to get to the bottom of the problem by running the following
steps:
Running update-grub manually produces the errored status:
[EMAIL PROTECTED]:~# update-grub
Searching for GRUB installation directory ... found: /boot/grub
[EMAIL PROTECTED]:~# echo $?
1
Upon investigation of the update-grub script, I tracked the problem down to
line 155 of update grub:
GRUB_LEGACY_0_BASED_PARTITIONS=1 grub-probe --device-map=${device_map} -t
drive -d $1 2 /dev/null
I discovered the options that were being used and this is the command which is
being run:
[EMAIL PROTECTED]:~# /usr/sbin/grub-probe --device-map=/boot/grub/device.map -t
drive -d /dev/sda1
error: cannot open `/dev/sdf'
error: cannot open `/dev/sdf'
grub-probe: error: Cannot find a GRUB drive for /dev/sda1. Check your
device.map.
This results in convert() returning error status.
Please let me know if I can be of any more assistance
APT OUTPUT:
Setting up linux-image-2.6.26-1-686 (2.6.26-5) ...
Running depmod.
Running mkinitramfs-kpkg.
initrd.img(/boot/initrd.img-2.6.26-1-686
) points to /boot/initrd.img-2.6.26-1-686
(/boot/initrd.img-2.6.26-1-686) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569.
vmlinuz(/boot/vmlinuz-2.6.26-1-686
) points to /boot/vmlinuz-2.6.26-1-686
(/boot/vmlinuz-2.6.26-1-686) -- doing nothing at
/var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569.
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/grub
/dev/sda1 /boot/grub/device.map
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.26-1-686 (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-2.6-686:
linux-image-2.6-686 depends on linux-image-2.6.26-1-686; however:
Package linux-image-2.6.26-1-686 is not configured yet.
dpkg: error processing linux-image-2.6-686 (--configure):
dependency problems - leaving unconfigured
Setting up libpq5 (8.3.4-1) ...
Errors were encountered while processing:
linux-image-2.6.26-1-686
linux-image-2.6-686
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- Package-specific info:
*** BEGIN /boot/grub/device.map
(hd0) /dev/sde
(hd1) /dev/sdf
*** END /boot/grub/device.map
*** BEGIN /proc/mounts
/dev/mapper/vg0-root / ext3 rw,errors=remount-ro,data=ordered 0 0
/dev/mapper/vg0-root /dev/.static/dev ext3 rw,errors=remount-ro,data=ordered 0 0
/dev/md0 /boot ext3 rw,errors=continue,data=ordered 0 0
/dev/mapper/vg0-home /home ext3 rw,errors=continue,data=ordered 0 0
/dev/mapper/vg0-srv /srv ext3 rw,errors=continue,data=ordered 0 0
/dev/mapper/vg0-usr /usr ext3 rw,errors=continue,data=ordered 0 0
/dev/mapper/vg0-var /var ext3 rw,errors=continue,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
#grub-install(8), grub-floppy(8),
#grub-md5-crypt, /usr/share/doc/grub
#and /usr/share/doc/grub-legacy-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5
# Pretty colours
color cyan/blue white/blue
### PASSWORD LINE REMOVED ###
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
### PASSWORD LINE REMOVED ###
### PASSWORD LINE REMOVED ###
### PASSWORD LINE REMOVED ###
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel/vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options
