From owner-freebsd-current@FreeBSD.ORG Wed Jun 24 20:19:46 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2E351065670 for ; Wed, 24 Jun 2009 20:19:46 +0000 (UTC) (envelope-from admin@mercurysquad.com) Received: from mail-pz0-f174.google.com (mail-pz0-f174.google.com [209.85.222.174]) by mx1.freebsd.org (Postfix) with ESMTP id 8517B8FC1A for ; Wed, 24 Jun 2009 20:19:46 +0000 (UTC) (envelope-from admin@mercurysquad.com) Received: by pzk4 with SMTP id 4so81887pzk.3 for ; Wed, 24 Jun 2009 13:19:46 -0700 (PDT) MIME-Version: 1.0 Sender: admin@mercurysquad.com Received: by 10.143.5.21 with SMTP id h21mr505313wfi.240.1245872923806; Wed, 24 Jun 2009 12:48:43 -0700 (PDT) Date: Thu, 25 Jun 2009 01:18:43 +0530 X-Google-Sender-Auth: 873ada806f038572 Message-ID: <66b068eb0906241248l7ef72f8dw5a245291a37731c1@mail.gmail.com> From: Prashant Vaibhav To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: External USB disk doesn't remount after suspend/resume X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2009 20:19:46 -0000 Hi, I've come across a problem running -CURRENT snapshot from June 12 (and searching the mailing list for messages after this hasn't yielded anything substantial). I'm running SMP kernel on UP machine, booting from an external usb hdd. The system suspends and resumes fine, except for one problem. Initially on boot the external drive is brought up as "umass0" and attached to "scbus1", however after resuming, the drive is brought up as umass1 and gets attached to scbus2. Obviously this confuses the system as my root is mounted from umass0. Thus everything works (ie. I was able to check dmesg for these messages) that doesn't need access to the filesystem, but since the root filesystem has disappeared from under us, nothing else works, not even a 'shutdown now' or 'halt' or trying to remount root via 'mount' command. I was unable to capture a dmesg log because of this. Is this a known issue, and is there a workaround? It should be noted that I have to set "kern.cam.scsi_delay=10000" in loader.conf before the kernel can mount root from the external usb drive. Best, Prashant