Debian Bug report logs - #445148
S390: Build w/ /boot partition succeeds, but re-boot fails in fsck

version graph

Package: debian-installer; Maintainer for debian-installer is Debian Install System Team <>; Source for debian-installer is src:debian-installer.

Reported by: RPN01 <>

Date: Wed, 3 Oct 2007 15:45:01 UTC

Severity: important

Tags: confirmed

Found in version debian-installer/20070308

Done: Christian Perrier <>

Bug is archived. No further changes may be made.

Full log

Message #58 received at (full text, mbox):

Received: (at 445148) by; 8 Oct 2007 15:13:10 +0000
From Mon Oct 08 15:13:10 2007
X-Spam-Checker-Version: SpamAssassin 3.1.4-bugs.debian.org_2005_01_02 
	(2006-07-26) on
X-Spam-Status: No, score=-1.9 required=4.0 tests=BAYES_00,FORGED_RCVD_HELO,
	FOURLA autolearn=no version=3.1.4-bugs.debian.org_2005_01_02
Return-path: <>
Received: from ([])
	by with esmtp (Exim 4.50)
	id 1IeuIA-0008Nf-Jd
	for; Mon, 08 Oct 2007 15:13:10 +0000
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 8 Oct 2007 17:12:38 +0200
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 8 Oct 2007 17:12:38 +0200
From: Frans Pop <>
Subject: Re: fsck during system boot fails with separate /boot partition
Date: Mon, 8 Oct 2007 17:12:37 +0200
User-Agent: KMail/1.9.7
References: <>
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <>
X-OriginalArrivalTime: 08 Oct 2007 15:12:38.0362 (UTC) FILETIME=[A9E0F3A0:01C809BD]
On Monday 08 October 2007, Peter 1 Oberparleiter wrote:
> This might indicate a timing problem - the init script tries to mount a
> DASD that has not yet been fully initialized by the kernel (the return
> code -EBUSY that triggers the "already mounted" message may indicate
> different problems). Try to add a sleep 5 into the init script just
> before the mount command that fails to check if this is the case.

I've found the root of the problem. It's a configuration problem after all.

We currently do not add the 'dasd=' parameter to the kernel boot arguments. 
Instead, we let udev assign device names.

Because of the 'root=' parameter (in which we use a by-path device name), 
the first dasd that is detected in my test is 0123, which ends up as dasda 
and thus 0122 ends up as dasdb, effectively swapping the two dasds. And as 
we still use the classic device names in /etc/fstab, the result is chaos.

The confusion came from the fact that mount still lists / mounted as
/dev/dasd_b_1, even if it is actually mounted as /dev/dasd_a_1.
So, fsck is completely correct in reporting /dev/dasda1 as already mounted.
It also means that when /boot is mounted later, it's not actually the boot 
partition that is mounted, but it is the root partition that is mounted 
(for a second time) on /boot.

Adding the dasd= boot parameter did not help - it seems to be ignored in our 
initrds; changing /etc/fstab to use /dev/disk/by-path devices consistently 
does result in a correct boot.
I'll consult with other Debian people how we want to resolve this.

Thanks very much for your replies, which did help in straightening this out 
for me.

Frans Pop

Send a report that this bug log contains spam.

Debian bug tracking system administrator <>. Last modified: Wed Apr 16 07:53:36 2014; Machine Name:

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.