[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#547895: marked as done (Unable to reload partition table for md0 / md2)

Your message dated Wed, 17 Jul 2013 11:38:31 +0200
with message-id <201307171139.02755.holger@layer-acht.org>
and subject line dealing with old partman related bugs
has caused the Debian Bug report #547895,
regarding Unable to reload partition table for md0 / md2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
547895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547895
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports

Boot method: Manual Boot.


on a linux host (prepare the debian-installer)
$> wget http://ftp.debian.org/dists/lenny/main/installer-armel/current/images/versatile/netboot/initrd.gz 
$> gunzip initrd.gz
$> mkdir deb_init
$> cd deb_init
$> cpio -i < ../initrd
$> tar cf ../deb_init.tar *

on the embedded host:

* boot an initrd
* enable telnetd
* plug SATA HDD (hotplug) and rescan bus
* create /debian in ramfs (of 512MB)
* untar deb_init.tar in /debian
* mount /proc /sys in /debian
* copy a preseed file to /debian
* chroot to /debian
* /lib/debian-installer.d/start-udev
* sh /lib/debian-installer-startup.d/S01mount
* sh /lib/debian-installer-startup.d/S10syslog
* sh /lib/debian-installer-startup.d/S15lowmem
* sh /lib/debian-installer-startup.d/S20templates
* sh /lib/debian-installer-startup.d/S35initrd-preseed
* kill some daemons that are running



more info
==========
# uname -a
Linux TS-WXL-EMDEB 2.6.22.18 #539 Fri Jul 17 13:57:12 JST 2009 armv5tejl unknown
Image version: http://ftp.debian.org/dists/lenny/main/installer-armel/current/images/versatile/netboot/initrd.gz 

Date: 22/09/09

Machine: Buffalo Terastation Duo

Processor: armv5tejl
Memory: 512M

Partitions:

Here is my recipe :

d-i partman-auto/expert_recipe string
   multiraid ::
      512 5000 512 raid $primary{ } method{ raid } .
      10000 6000 10000 raid $primary{ } method{ raid } .
      512 512 300% raid method{ raid } .
      50000 10000 100000000 raid method{ raid } .

d-i partman-auto-raid/recipe string
      1 2 0 ext3 /boot /dev/sda1#/dev/sdb1 .
      1 2 0 ext3 / /dev/sda2#/dev/sdb2 .
      1 2 0 swap - /dev/sda5#/dev/sdb5 .
      1 2 0 ext3 /space /dev/sda6#/dev/sdb6 .


Output of lspci -knn (or lspci -nn): N/A



Base System Installation Checklist:

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [E]
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [ ]
Overall install:        [O]

Comments/Problems:

Problem after partitioning :


[!] Partition disks
The kernel was unable to re-read the partition table on /dev/md0 (Invalid Argument). 


(same for md2)
I can press "Continue" and everything goes smooth and the installation runs well. 

as I have a runing telnet, I can see that during the installation:
# cat /proc/mdstat
reports the array OK (or resysnching .. depending when I cat the file)




regards,

--- End Message ---
--- Begin Message --- 
reassign 693107 partman-auto
reassign 670702 partman-auto
reassign 615074 lvm2
reassign 676172 partman
severity 691046 wishlist
retitle 644430 document the need for a bios boot partition when using GPT
forcemerge 644430 691046 
reassign 691046 release-notes
reassign 683747 partman-lvm
reassign 671879 partman-base
thanks

Hi,

thank you for submitting installation reports, much appreciated.

I read through all the ("partman" related) bugs mentioned here and am closing 
them now as
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they were (very) old.

If I've closed a bug incorrectly please do reply or just file a new one - 
thats often better, as the bug log will be more clear.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: