Bug#336317: initramfs-tools: created initramfs is unable to boot a system with mirrored rootdisks

2005-11-02 Thread Dominik Kubla
On Wednesday 02 November 2005 08:51, maximilian attems wrote:
[...]
 hmm i had suspected a more esoteric setup.
 tested it myself with latest initramfs-tools on raid root.
[...]
 yes can you put the initramfs archive somewhere online where i can take a
 look at it.

 how did you generate it?

 does regenerating the initramfs image help:
 update-initramfs -u -t -k 2.6.14-1-686

 assuming you use the linux-image-2.6-686 from unstable?

The initramfs was created by the kernel postinstall script.
I did recreate the kernel image like you suggested. Same result:
/dev/md0 not found and the USB keyboard does not work in the shell.

I am using the k7 kernel from unstable.

You can find the initramfs image at:

http://www.kubla.de/temp/initramfs-2.6.14-1-k7

Regards,
  Dominik
-- 
Verschmilzt die Wirtschaft Europas zur Gemeinschaft, und das wird
früher geschehen, als wir denken, so verschmilzt auch die Politik.
-- Walter Rathenau (1867-1922)



Bug#336317: initramfs-tools: created initramfs is unable to boot a system with mirrored rootdisks

2005-10-31 Thread Dominik Kubla
On Monday 31 October 2005 11:42, maximilian attems wrote:
 On Sat, 29 Oct 2005, Dominik Kubla wrote:
  The created initramfs drops into a shell because /dev/md0 can not be
  mounted. This is a regression from version 0.30.

 what is your setup?
 please send the output of /proc/mdstat?

# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda3[0] hdc3[1]
  19591168 blocks [2/2] [UU]

md0 : active raid1 hda1[0] hdc1[1]
  15623104 blocks [2/2] [UU]

md1 : active raid1 hda2[0] hdc2[1]
  3903680 blocks [2/2] [UU]

unused devices: none

 have you mdadm installed on that box?
 what does dpkg -l mdadm show?

# dpkg -l mdadm
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
ii  mdadm  1.12.0-1   tool to administer Linux md device arrays (s

Additional infos:

$ cat /etc/fstab
#
# /etc/fstab: static file system information.
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
/dev/md0/   ext3defaults,errors=remount-ro 0   1
/dev/md1noneswapsw  0   0
/dev/md2/home   ext3defaults0   2
/dev/hdc4   /scratchext3defaults0   2
/dev/hdb/media/cdrom0   udf,iso9660 ro,user,noauto  0   0
/dev/fd0/media/floppy0  autorw,user,noauto  0   0
tmpfs   /tmptmpfs   mode=1777,size=2G   0   0

$ df -k
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/md0  15377744   3755052  10841540  26% /
/dev/md2  19283236  14418876   4864360  75% /home
/dev/hdc4 39376392   1769000  35607168   5% /scratch
tmpfs  209715272   2097080   1% /tmp
tmpfs   648296 0648296   0% /dev/shm
tmpfs10240   144 10096   2% /dev

$ sfdisk -l /dev/hda

Disk /dev/hda: 77622 cylinders, 16 heads, 63 sectors/track
Warning: The partition table looks like it was made
  for C/H/S=*/255/63 (instead of 77622/16/63).
For this listing I'll assume that geometry.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start End   #cyls#blocks   Id  System
/dev/hda1   *  0+   19441945-  15623181   fd  Linux raid autodetect
/dev/hda2   19452430 4863903795   fd  Linux raid autodetect
/dev/hda3   243148692439   19591267+  fd  Linux raid autodetect
/dev/hda4  0   -   0  00  Empty

$  sfdisk -l /dev/hdc

Disk /dev/hdc: 158816 cylinders, 16 heads, 63 sectors/track
Units = cylinders of 516096 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start End   #cyls#blocks   Id  System
/dev/hdc1   *  0+  31001   31002-  15624976+  fd  Linux raid autodetect
/dev/hdc2  31002   3875177503906000   fd  Linux raid autodetect
/dev/hdc3  38752   79441   40690   20507760   fd  Linux raid autodetect
/dev/hdc4  79442  158815   79374   40004496   83  Linux


If you need any more info, please let me know ...

Many thanks for your work!
Dominik
-- 
Verschmilzt die Wirtschaft Europas zur Gemeinschaft, und das wird
früher geschehen, als wir denken, so verschmilzt auch die Politik.
-- Walther Rathenau (1867-1922)



Bug#336317: initramfs-tools: created initramfs is unable to boot a system with mirrored rootdisks

2005-10-29 Thread Dominik Kubla
Package: initramfs-tools
Version: 0.37
Severity: critical
Justification: breaks the whole system


The created initramfs drops into a shell because /dev/md0 can not be
mounted. This is a regression from version 0.30.

The shell is unusable because USB keyboards are not fully initialized:
they are no longer working in PS/2-Emulation mode, but not yet working
in USB mode.

The system is left in an unusable state.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (900, 'unstable'), (700, 'testing'), (500, 'experimental'), (500, 
'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-1-k7
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages initramfs-tools depends on:
ii  busybox   1:1.01-3   Tiny utilities for small and embed
ii  cpio  2.6-8  GNU cpio -- a program to manage ar
ii  klibc-utils   1.1.1-2small statically-linked utilities 
ii  mklibs-copy   0.1.18 Shared library reduction script
ii  udev  0.071-1/dev/ and hotplug management daemo

initramfs-tools recommends no packages.

-- no debconf information


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



Bug#333067: linux-image-k7: System unusable after reboot because rivafb is compiled with debugging enabled.

2005-10-10 Thread Dominik Kubla
Package: linux-image-k7
Version: 2.6.12-10
Severity: critical
Justification: breaks the whole system


After updating udev a reboot resulted in a unusable system because
rivafb was being loaded by udev/coldplug. rivafb is not usable,
especially not when being compiled with debugging enabled. Result was a
system that only printed panning related debugging messages.

To revive the system i had to boot into emergency mode (using -b, using
the grub recovery boot was not successful. I doubt a normal user would
have known what to do.) and delete rivafb. Now udev was correctly using
nvidiafb, which worked.

And the bottomline is:

* Don't compile any modules with debugging support enabled. (If you like
  you can provide a kernel-modules-dbg package.) In almost all cases the
  debugging options are only useful to kernel developers anyway.
* Don't compile rivafb: it was never really usable and except for old
  riva cards nvidiafb is the better choice anyway (but that is arguably
  a bug in udev/coldplug).

Regards,
  Dominik

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-k7 depends on:
ii  linux-image-2.6-k72.6.12-10  Linux kernel 2.6 image on AMD K7 m

linux-image-k7 recommends no packages.

-- no debconf information


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