Date: Tue, 3 May 2016 10:42:51 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> To: Graham Menhennitt <graham@menhennitt.com.au> Cc: freebsd-current@freebsd.org Subject: Re: boot fails "Can't stat /dev/da0a: No such file or directory" Message-ID: <20160503084251.GB5892@brick> In-Reply-To: <57266A7E.1070500@menhennitt.com.au> References: <57247294.4050607@menhennitt.com.au> <57266A7E.1070500@menhennitt.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 0502T0643, Graham Menhennitt wrote: > On 30/04/2016 06:53 PM, Graham Menhennitt wrote: > > Hi all, > > > > I have a USB disk that I use for backup. Up till now, it's mounted > > without any problems at boot time. After updating to -current as of > > yesterday, it doesn't mount and causes the boot to fail. > > > > My /etc/fstab looks like: > > > > # Device Mountpoint FStype Options Dump Pass# > > > > /dev/ada0s1a / ufs rw 1 1 > > /dev/ada0s1b none swap sw 0 0 > > /dev/da0a /backup ufs rw,late 1 1 > > > > > > I tried adding the "late" to fix the problem, but it doesn't help. > > > > The error message is: > > > > /dev/ada0s1a: clean... > > Can't stat /dev/da0a: No such file or directory > > Unknown error; help! > > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > > > > > > (hand transcribed - maybe typos) > > > > Can anybody help, please. > > > > Thanks, > > Graham > Sorry, I forgot to mention... > > I commented out that line from fstab which allows the boot to complete. > I can then manually mount it without any problems. It looks like the > device doesn't get created early enough. Have you run mergemaster after upgrade? In particular, do you have the current version of /etc/rc.d/mountcritlocal?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160503084251.GB5892>