From owner-freebsd-hackers Fri Jun 7 11:41:59 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 25EA837B427 for ; Fri, 7 Jun 2002 11:41:09 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g57If4p05726; Fri, 7 Jun 2002 11:41:04 -0700 (PDT) Date: Fri, 7 Jun 2002 11:41:04 -0700 (PDT) From: Doug White To: =?iso-8859-7?b?tuPj5evv8iDP6erv7e/s/PDv9evv8g==?= Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cannot access disk In-Reply-To: <200206070145.21754.aoiko@cc.ece.ntua.gr> Message-ID: <20020607114011.V5585-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 7 Jun 2002, [iso-8859-7] Άγγελος Οικονομόπουλος wrote: > On Thursday 06 June 2002 22:36, Doug White wrote: > > On Thu, 6 Jun 2002, Aggelos Economopoulos wrote: > > > After adding a 40G ide disk(ad3) on my system, I 'ld like to devote > > > some extra space to FreeBSD (there is already a linux installation on > > > the 40G disk). However, after booting my -stable installation on the > > > first disk(ad0), I get the error message "excessive recursion in search > > > for slices" by the kernel on any attempt to access ad3 (mount a > > > partition, fdisk -s /dev/ad3, or even a read() on ad3). > > > > Try zeroing off the beginning of the disk with dd; maybe there's a > > corrupt partition table there. > > No, the partition table is _not_ corrupt. As I mentioned before, I have a > working linux installation on said disk. Moreover, I can parse the > partition table chain under the linux kernel (using userspace tools) but > under freebsd I get the same error as the freebsd kernel partition handling > code. I even read the mbr pt + extended pts with a hex editor, they are > just fine. I' ve spent about two weeks on the subject before ruling out all > posibilities that this is a partition handling problem. Well if tools blow up on multiple platforms, I'm inclined to point to a corrupt partition table. Linux may have a workaround but it doesn't get around the root brokenness. Fix your partition table and your systems will be happy. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message