Bug#457785: tomcat6.

2008-02-13 Thread Mauro Sanna
when can we have tomcat6 in sid at least?




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-03-07 Thread Mauro Sanna

maximilian attems wrote:

ok one other thing to check is please upgrade to busybox from
etch does that fix your trouble??


A strange thing!!
Today I've installed an etch, using sarge installer as usual, with lvm 
support in a new pc, an IBM netvista.

It works!!!
Now I think the problem is the hardware because in one pc the system 
boots and in another don't.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-14 Thread Mauro Sanna
Il giorno mar, 13/02/2007 alle 18.01 +0100, maximilian attems ha
scritto:
 ok one other thing to check is please upgrade to busybox from
 etch does that fix your trouble??
 
I have already busybox from etch

dpkg -l busybox

ii  busybox1.1.3-3



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-13 Thread Mauro Sanna
Il giorno ven, 09/02/2007 alle 11.57 +0100, maximilian attems ha
scritto:
 On Fri, Feb 09, 2007 at 11:35:04AM +0100, Mauro Sanna wrote:
  Il giorno ven, 09/02/2007 alle 10.39 +0100, maximilian attems ha
  scritto:
  
  I have had this problem after a complete upgrade to etch and I have the
  same problem using backported initramfs-tools with backported kernel
  2.6.18 or 2.6.17 in sarge. 
 
 regenerate your initramfs with new lvm2.
  

I've done, I've upgraded to etch, reboot and the system says waiting
for root filesystem

   could you add vgscan to your initramfs and check what it is
   saying inside of the rescue shell.
   you'd have to add a following line to the bottom of one hook in
/usr/share/initramfs-tools/hooks/ :
   copy_exec /lib/lvm-200/vgchange /sbin
 uups
 copy_exec /lib/lvm-200/vgscan /sbin
  
  The hooks I have under /usr/share/initramfs-tools/hooks are:
  kernelextras  thermal  udev
  
  In which of these ones I have to add vgscan?
 
 any doesn't matter, you need to regenerate too here once you added the
 line
  
I've add copy_exec /lib/lvm-200/vgscan /sbin at the bottom of
kernelextras then I run update-initramfs -k 2.6.18-3-686 -u.
Reboot and it hangs as usual saying tha can't find volume vg00 and
waiting for root filesystem.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-13 Thread Mauro Sanna
Il giorno mar, 13/02/2007 alle 12.01 +0100, maximilian attems ha
scritto:
 On Tue, Feb 13, 2007 at 11:27:39AM +0100, Mauro Sanna wrote:
  
  I've done, I've upgraded to etch, reboot and the system says waiting
  for root filesystem
 
 hmm strange it works here for many boxes.

Have you root filesystem in a logical volume?

 what's your lvm2 version now?
 dpkg -l lvm2

ii  lvm2   2.02.06-3


  
  I've add copy_exec /lib/lvm-200/vgscan /sbin at the bottom of
  kernelextras then I run update-initramfs -k 2.6.18-3-686 -u.
  Reboot and it hangs as usual saying tha can't find volume vg00 and
  waiting for root filesystem.
 
 sure i'd asked for it output, but pvscan is usually more informative
 please add that one and post what happens when you land in rescue
 console and execute pvscan?
 

If I add copy_exec /lib/lvm-200/vgscan /sbin at the bottom of
kernelextras and I run update-initramfs -k 2.6.18-3-686 -u it don't open
a rescue console, it hangs.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-13 Thread Mauro Sanna

 where what is the last message?
 did you boot with rootdelay?

before the prompt says:

waiting.done check root=bootarg cat /proc/cmdline
or missing modules, devices: cat /proc/modules ls /dev

alert! /dev/mapper/vg00-root does not exist. dropping to a shell



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-09 Thread Mauro Sanna
Il giorno ven, 09/02/2007 alle 01.55 +0100, maximilian attems ha
scritto:
 On Thu, 01 Feb 2007, Mauro Sanna wrote:
 
  Then I upgrade to etch.
  I install the new kernel 2.6.18 and initramfs-tools.
  I create the new initrd then, at the end of upgrade, reboot the
  system.
  It hangs saying that cannot find my volume group and is waiting
  for root filesystem...
  In my preceding upgrades, months ago, I didn't had this problem.
  I have this problem with newer upgrades to etch.
 
 how did you create the initrd?
 please send output of the installed linux-image
 
 dpkg -l linux-image*
 

un  linux-imagenon definita (descrizione non disponibile)
un  linux-image-2. non definita (descrizione non disponibile)
ii  linux-image-2. 2.6.18+5   Linux kernel 2.6 image on
PPro/Celeron/PII/P
pn  linux-image-2. non definita (descrizione non disponibile)
pn  linux-image-2. non definita (descrizione non disponibile)
ii  linux-image-2. 2.6.18-8~bpo.1 Linux 2.6.18 image on
PPro/Celeron/PII/PIII/

dpkg -l kernel-image*


ii  kernel-image-2 2.6.8-16sarge6 Linux kernel image for version 2.6.8
on 386.


I am using sarge and I have installded backport of linux image 2.6.18.
When I boot with kernel 2.6.8 it's all ok.
When I boot with kernel 2.6.18 it says that it can't find volume group
vg00 and waiting for root filesystem.
The creation of initrd with kernel 2.6.18 is automatic, I'have tried
also update-initarmfs, reboot but the system hangs with the above
messages.
If you try to install etch using one boot partition and lvm for the
remaining disk space you'll see that it don't boot.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-09 Thread Mauro Sanna
Il giorno ven, 09/02/2007 alle 10.39 +0100, maximilian attems ha
scritto:
 reassign 409243 lvm2
 stop
 
 On Fri, 09 Feb 2007, Mauro Sanna wrote:
 
  ii  linux-image-2. 2.6.18+5   Linux kernel 2.6 image on
  PPro/Celeron/PII/P
  
  I am using sarge and I have installded backport of linux image 2.6.18.
  When I boot with kernel 2.6.8 it's all ok.
  When I boot with kernel 2.6.18 it says that it can't find volume group
  vg00 and waiting for root filesystem.
  The creation of initrd with kernel 2.6.18 is automatic, I'have tried
  also update-initarmfs, reboot but the system hangs with the above
  messages.
  If you try to install etch using one boot partition and lvm for the
  remaining disk space you'll see that it don't boot.
 
 no it does not it's because your lvm2 is still from sarge
 and it be interesting to track the failure down, currently
 i have no other info beside the failure.
 

I have had this problem after a complete upgrade to etch and I have the
same problem using backported initramfs-tools with backported kernel
2.6.18 or 2.6.17 in sarge. 

 could you add vgscan to your initramfs and check what it is
 saying inside of the rescue shell.
 you'd have to add a following line to the bottom of one hook in
  /usr/share/initramfs-tools/hooks/ :
 copy_exec /lib/lvm-200/vgchange /sbin

The hooks I have under /usr/share/initramfs-tools/hooks are:
kernelextras  thermal  udev

In which of these ones I have to add vgscan?



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-07 Thread Mauro Sanna
Il giorno mer, 07/02/2007 alle 01.39 +0100, maximilian attems ha
scritto:
 hmm i'd also be interested in:
 ls -l /sbin/modprobe
 dpkg -l module-init-tools
 

. /conf/initramfs.conf
no results.

. /scripts/functions
no results.

./scripts/local-top/lvm
unable to find volume group vg00.

vgchange -ay vg00
unable to find volume group vg00.

vgchange -ay
no volumes group found.

dpkg -l lvm2 libdevmapper1.02
ii  lvm2   2.01.04-5  The Linux Logical Volume Manager

I don't have libdevmapper1.02 but libdevmapper1.01 installed.

dpkg -l module-init-tools
ii  module-init-to 3.3-pre3-1 tools for managing Linux kernel
modules

ls -l /sbin/modprobe
-rwxr-xr-x  1 root root 26656 2006-12-08 11:26 /sbin/modprobe





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-06 Thread Mauro Sanna
Il giorno lun, 05/02/2007 alle 13.48 +0100, maximilian attems ha
scritto:
 On Mon, Feb 05, 2007 at 01:19:38PM +0100, Mauro Sanna wrote:
  
  Ok, I've booted with rootdelay=1
  
  ls /dev/hd* 
  
  dev/hda, dev/hda1, dev/hda2, dev/hdd
 
 hmm ok so i need to know where your lvm is on,
 please attach the output of vgdisplay
 i guess it's on /dev/hda2, so your device node
 should be there?

that's vgdisplay:

 --- Volume group ---
  VG Name   vg00
  System ID
  Formatlvm2
  Metadata Areas1
  Metadata Sequence No  6
  VG Access read/write
  VG Status resizable
  MAX LV0
  Cur LV5
  Open LV   5
  Max PV0
  Cur PV1
  Act PV1
  VG Size   19,02 GB
  PE Size   4,00 MB
  Total PE  4869
  Alloc PE / Size   697 / 2,72 GB
  Free  PE / Size   4172 / 16,30 GB
  VG UUID   9q0ZGf-pY0e-dPle-fPAL-mmGT-qjJt-Ap4Mhv


 can you try please to boot with break=mount
 wait a bit of a time in the rescue shell
 and then exit it, does that work?

No, it doesn't work, when I exit from rescue shell it says waiting for
root filesystem
Thank you.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-06 Thread Mauro Sanna
Il giorno mar, 06/02/2007 alle 12.43 +0100, maximilian attems ha
scritto:
 On Tue, Feb 06, 2007 at 12:37:09PM +0100, Mauro Sanna wrote:
  
  that's vgdisplay:
 
 upps sorry meant pvdisplay

--- Physical volume ---
  PV Name   /dev/hda2
  VG Name   vg00
  PV Size   19,02 GB / not usable 0
  Allocatable   yes
  PE Size (KByte)   4096
  Total PE  4869
  Free PE   4172
  Allocated PE  697
  PV UUID   dMf13F-oWvB-1Q9Q-BOVt-bKyP-Zimw-3pJSfx


  
   can you try please to boot with break=mount
   wait a bit of a time in the rescue shell
   and then exit it, does that work?
  
  No, it doesn't work, when I exit from rescue shell it says waiting for
  root filesystem
  Thank you.
 
 hmmm ok so it's not a race in your case,
 what happens if you run in the rescue shell
 . /conf/initramfs.conf
 . /scripts/functions
 ./scripts/local-top/lvm

./conf/initramfs.conf and ./scripts/function says permission denied.
./scripts/local-top/lvm says
unable to find volume group 00.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-06 Thread Mauro Sanna
 ./scripts/local-top/lvm
 

Sorry it is :unable to find volume group vg00
Thanks.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-02-05 Thread Mauro Sanna
Il giorno ven, 02/02/2007 alle 10.59 +0100, maximilian attems ha
scritto:
 On Thu, Feb 01, 2007 at 08:27:58AM +0100, Mauro Sanna wrote:
  
  -- Package-specific info:
  -- /proc/cmdline
  root=/dev/mapper/vg00-root ro
 
 ok looks good.
  
  I've installed sarge with lvm and kernel 2.6.8 with initrd.
  At the end of installation I reboot the system and all works
  well.
  Then I upgrade to etch.
  I install the new kernel 2.6.18 and initramfs-tools.
  I create the new initrd then, at the end of upgrade, reboot the
  system.
  It hangs saying that cannot find my volume group and is waiting
  for root filesystem...
  In my preceding upgrades, months ago, I didn't had this problem.
  I have this problem with newer upgrades to etch.
 
 please boot with bootarg rootdelay=1
 and check in the rescue shell which devices exists
 ls /dev/hd*
 ls /dev/sd*
  
 also attach your /etc/fstab to your response.

Ok, I've booted with rootdelay=1

ls /dev/hd* 

dev/hda, dev/hda1, dev/hda2, dev/hdd

ls /dev/sd* no such file o directory.

etc/fstab:

proc/proc   procdefaults0   0
/dev/mapper/vg00-root  /ext3defaults,errors=remount-ro 0   1
/dev/hda1   /boot   ext3defaults0   2
/dev/mapper/vg00-usr   /usr   ext3defaults0   2
/dev/mapper/vg00-tmp   /tmp   ext3defaults0   2
/dev/mapper/vg00-var   /var   ext3defaults0   2
/dev/mapper/vg00-swap none  swapsw  0   0
/dev/hdd/media/cdrom0   udf,iso9660 user,noauto 0   0
/dev/fd0/media/floppy0  autorw,user,noauto  0   0


That's all.
Thank you.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409171: problems with initramfs-tools.

2007-01-31 Thread Mauro Sanna
Package: initramfs-tools
Version: 0.85e


I've installed sarge with lvm and kernel 2.6.8 with initrd.
At the end of installation I reboot the system and all works
well.
Then I upgrade to etch.
I install the new kernel 2.6.18 and initramfs-tools.
I create the new initrd then, at the end of upgrade, reboot the
system.
It hangs saying that cannot find my volume group and is waiting
for root filesystem...
In my preceding upgrades, months ago, I didn't had this problem.
I have this problem with newer upgrades to etch.
It's a initramfs-tools bug?
Thank you.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409243: fails to boot.

2007-01-31 Thread Mauro Sanna
Package: initramfs-tools
Version: 0.85e
Severity: critical
Justification: breaks the whole system

*** Please type your report below this line ***


-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/vg00-root ro

-- /proc/filesystems
ext2
cramfs
ext3

-- lsmod
Module  Size  Used by
ipv6  230148  10
af_packet  20872  2
evdev   9088  0
floppy 54992  0
pcspkr  3816  0
8139cp 19072  0
ohci1394   32004  0
ieee1394  100408  1 ohci1394
snd_via82xx26660  0
snd_ac97_codec 59268  1 snd_via82xx
snd_pcm85384  1 snd_via82xx
snd_timer  23300  1 snd_pcm
snd_page_alloc 11144  2 snd_via82xx,snd_pcm
gameport4736  1 snd_via82xx
snd_mpu401_uart 7296  1 snd_via82xx
snd_rawmidi23204  1 snd_mpu401_uart
snd_seq_device  7944  1 snd_rawmidi
snd50660  7
snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
pci_hotplug30640  0
via_agp 8832  1
uhci_hcd   29328  0
usbcore   104292  3 uhci_hcd
via82cxxx_audio26248  0
uart40111460  1 via82cxxx_audio
sound  75308  2 via82cxxx_audio,uart401
soundcore   9824  3 snd,via82cxxx_audio,sound
ac97_codec 16908  1 via82cxxx_audio
8139too23936  0
mii 4864  2 8139cp,8139too
parport_pc 33348  0
parport37320  1 parport_pc
agpgart31784  1 via_agp
capability  4872  0
commoncap   7168  1 capability
psmouse17800  0
ide_cd 38176  0
cdrom  35740  1 ide_cd
rtc12088  0
ext3  109800  5
jbd54552  1 ext3
dm_mod 51068  6
ide_generic 1664  0
via82cxxx  12956  1
pdc202xx_old   15388  1
ide_disk   16768  3
ide_core  125028  5
ide_cd,ide_generic,via82cxxx,pdc202xx_old,ide_disk
unix   26036  10
font8576  0
vesafb  6688  0
cfbcopyarea 3840  1 vesafb
cfbimgblt   3200  1 vesafb
cfbfillrect 3712  1 vesafb

-- kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook   = /sbin/update-grub

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-386
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages initramfs-tools depends on:
ii  busybox-cvs-static  20040623-1   Standalone rescue shell
with tons
ii  cpio2.5-1.3  GNU cpio -- a program to
manage ar
ii  klibc-utils 1.4.30-1 small statically-linked
utilities
ii  module-init-tools   3.3-pre3-1   tools for managing Linux
kernel mo
ii  udev0.103-1  /dev/ and hotplug
management daemo

-- no debconf information



I've installed sarge with lvm and kernel 2.6.8 with initrd.
At the end of installation I reboot the system and all works
well.
Then I upgrade to etch.
I install the new kernel 2.6.18 and initramfs-tools.
I create the new initrd then, at the end of upgrade, reboot the
system.
It hangs saying that cannot find my volume group and is waiting
for root filesystem...
In my preceding upgrades, months ago, I didn't had this problem.
I have this problem with newer upgrades to etch.





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]