Date: Mon, 27 Nov 2000 12:04:40 +0000 From: "Neil Long" <neil.long@computing-services.oxford.ac.uk> To: freebsd-questions@FreeBSD.ORG Subject: wd0 versus ad0 on warm boot Message-ID: <1001127120440.ZM23007@ratbert.oucs.ox.ac.uk>
next in thread | raw e-mail | index | archive | help
Hello I can't find where I need to make an edit but here is the problem I had an old 2.2.8 box which I upgraded via 3.2, 3.4, 4.1.1_RELEASE to 4.2_RELEASE (only real problem was that the old '/' default size is a teensy bit tight at 4.* but I will rebuild one day...) All is fine on a cold boot - i.e. all disks are using ad0 as per fstab but if I reboot (i.e. warm) then '/' gets mounted on wd0s2a rather than ad0s2a (and top won't run because of it - nlist errors). I re-wrote the disklabel which has wd to ad as one guess # /dev/ad0c: type: ESDI disk: ad0s2 installworld updated the /boot files (and of course all is well on a hard boot). There is another partition with a minimal Linux distro on it and I use the lilo boot manager (which speaks hda, etc). Any ideas where the vestigal wd0 comes from? Can I still boot Linux as the non-default if I use a different boot manager? Rarely use Linux but sometimes I need to, could use a boot floppy I suppose. Thanks Neil -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dr Neil J Long, Computing Services, University of Oxford 13 Banbury Road, Oxford, OX2 6NN, UK Tel:+44 1865 273232 Fax:+44 1865 273275 EMail: Neil.Long@computing-services.oxford.ac.uk PGP: ID 0xE88EF71F OxCERT: oxcert@ox.ac.uk PGP: ID 0x4B11561D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1001127120440.ZM23007>