From owner-freebsd-ia64 Thu Jan 30 17:24:45 2003 Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 050FA37B401; Thu, 30 Jan 2003 17:24:43 -0800 (PST) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A025043E4A; Thu, 30 Jan 2003 17:24:41 -0800 (PST) (envelope-from marcel@xcllnt.net) Received: from athlon.pn.xcllnt.net (athlon.pn.xcllnt.net [192.168.4.3]) by ns1.xcllnt.net (8.12.6/8.12.6) with ESMTP id h0V1OfMW078672; Thu, 30 Jan 2003 17:24:41 -0800 (PST) (envelope-from marcel@piii.pn.xcllnt.net) Received: from athlon.pn.xcllnt.net (localhost [127.0.0.1]) by athlon.pn.xcllnt.net (8.12.6/8.12.6) with ESMTP id h0V1OfcV000992; Thu, 30 Jan 2003 17:24:41 -0800 (PST) (envelope-from marcel@athlon.pn.xcllnt.net) Received: (from marcel@localhost) by athlon.pn.xcllnt.net (8.12.6/8.12.6/Submit) id h0V1OfTv000991; Thu, 30 Jan 2003 17:24:41 -0800 (PST) Date: Thu, 30 Jan 2003 17:24:41 -0800 From: Marcel Moolenaar To: phk@FreeBSD.org Cc: ia64@FreeBSD.org Subject: Unable to mount GPT based msdos filsystem (ie EFI) Message-ID: <20030131012441.GA925@athlon.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.3i Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Poul, You may be in the middle of something, but at this time we're not able to mount the EFI filesystem on a GPT disk. I think it started with making NO_GEOM obsolete and the removal of some code that we apparently depend upon. itanium% sudo mount /efi msdosfs: /dev/da0p1: Invalid argument \begin{kdump output} 469 ktrace RET ktrace 0 469 ktrace CALL execve(0x9fffffffffeff430,0x9fffffffffeff958,0x9fffffffffeff978) 469 ktrace NAMI "/sbin/mount_msdosfs" 469 mount_msdosfs RET execve 0 469 mount_msdosfs CALL open(0x40000000000c3678,0,0xe00000000050d260) 469 mount_msdosfs NAMI "." 469 mount_msdosfs RET open 3 469 mount_msdosfs CALL chdir(0x40000000000becb8) 469 mount_msdosfs NAMI "/" 469 mount_msdosfs RET chdir 0 469 mount_msdosfs CALL lstat(0x9fffffffffeff541,0x9fffffffffefec10) 469 mount_msdosfs NAMI "efi" 469 mount_msdosfs RET lstat 0 469 mount_msdosfs CALL chdir(0x9fffffffffeff541) 469 mount_msdosfs NAMI "efi" 469 mount_msdosfs RET chdir 0 469 mount_msdosfs CALL __getcwd(0x9fffffffffeff540,0x400) 469 mount_msdosfs RET __getcwd 0 469 mount_msdosfs CALL fchdir(0x3) 469 mount_msdosfs RET fchdir 0 469 mount_msdosfs CALL close(0x3) 469 mount_msdosfs RET close 0 469 mount_msdosfs CALL stat(0x9fffffffffeff540,0x9fffffffffeff090) 469 mount_msdosfs NAMI "/efi" 469 mount_msdosfs RET stat 0 469 mount_msdosfs CALL stat(0x9fffffffffeff540,0x9fffffffffeff4c0) 469 mount_msdosfs NAMI "/efi" 469 mount_msdosfs RET stat 0 469 mount_msdosfs CALL mount(0x40000000000be9e8,0x9fffffffffeff540,0,0x9fffffffffeff110) 469 mount_msdosfs NAMI "/efi" 469 mount_msdosfs NAMI "/dev/da0p1" 469 mount_msdosfs RET mount -1 errno 22 Invalid argument 469 mount_msdosfs CALL write(0x2,0x9fffffffffefe830,0xf) 469 mount_msdosfs GIO fd 2 wrote 15 bytes "mount_msdosfs: " 469 mount_msdosfs RET write 15/0xf 469 mount_msdosfs CALL write(0x2,0x9fffffffffefe860,0xa) 469 mount_msdosfs GIO fd 2 wrote 10 bytes "/dev/da0p1" 469 mount_msdosfs RET write 10/0xa 469 mount_msdosfs CALL write(0x2,0x40000000000c2ea0,0x2) 469 mount_msdosfs GIO fd 2 wrote 2 bytes ": " 469 mount_msdosfs RET write 2 469 mount_msdosfs CALL write(0x2,0x9fffffffffefe830,0x11) 469 mount_msdosfs GIO fd 2 wrote 17 bytes "Invalid argument " 469 mount_msdosfs RET write 17/0x11 \end{kdump output} I did a chkdsk yesterday with an EFI based tool, so the file system is not corrupted (AFAICT), but fsck_msdosfs gives: itanium% sudo fsck_msdosfs /dev/da0p1 ** /dev/da0p1 Invalid sector size: 127 itanium% Anyway: let me know how this may or may not relate to what you're doing. I'll start digging deeper in the mean time... BTW: If you want to test this yourself on i386, you should be able to build a kernel with GPT support. The gpt(8) utility compiles on i386 as well, so all you need is a spare disk and you can play with it. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message