FreeBSD 4.5-RELEASE no /boot/loader error! Need Help!
Patrick Simon
i just updated my unix system to freebsd 4.5 and after booting i got the
following error message:
-----------------------------
No /boot/loader
>> FreeBSD/i386 BOOT
Default: 0:ad(0,a)/kernel
boot:
No /kernel
-----------------------------
What can i do now? /boot/loader does exsist! The previous installed os was
freebsd 4.4 - i took the same slices and disk labels - i actually changed
nothing and performed the installion the same way (same settings) than
usally - but it just doesn't work! I need help urgently ... thank you very
much in advance. (I already noticed that i am not the only one who has to
deal with this problem ...)
My System:
AMD 800 Duron
512MB PC-133
ATA/EIDE 60GB Maxtor HDD
SVGA 8MB Diamond S330
NEC Floppy/NEC CDROM
2 3COM 100/10MB ADAPTERS
My Configuration:
KERNELKONFIGURATION
Dev IRQ Port
Storage:
ATA/ATAPI compatible disk controller ata0
14 0x1f0
ATA/ATAPI compatible disk controller ata1
15 0x170
Floppy disk controller
fdc0 6 0x3f0
Network:
NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters ed0 10 0x280
AT&T Starlan 10 and EN100, 3C507, NI5210 Ethernet ada. Ie0 11 0x300
Comunications:
Parallel Port chipset
ppc0 7
8250/16450/16550 Serial port sio0 4
0x3f8
8250/16450/16550 Serial port sio1 3
0x2f8
Input:
Keyboard
atkbd0 1
PS/2 Mouse
psm0 12
Syscons console driver
sc0
Multimedia:
Miscellaneous:
PC-card controller
pcic0 0x3e0
Math coprocessor ´
npx0 13 0xf0
PARTITION
Disk name: ad0
DISK Geometry: 7476 cyls/255 heads/63 sectors = 120101940 sectors (58642MB)
Offset Size(ST) End Name Ptype Desc
Subtype Flags
0 63 62 - 6
unused 0 -
63 120101877 120101939 ad0s1 3 freebsd 165 C
120101940 1260 120103199 - 6 unused
-
:: installed standard MBR (no boot manager)
LABELS
Disk: ad0 Partition name: ad0s1 Free: 0 blocks (0MB)
Part Mount Size Newfs
Ad0s1e / 60MB UFS Y
Ad0s1a /var 200MB UFS-S Y
Ad0s1b swap 512MB SWAP
Ad0s1f /home 1000MB UFS-S Y
Ad0s1g /netdrive 50000MB UFS-S N
Ad0s1h /usr 6871MB UFS-S Y
Patrick Simon
boot: 0:ad(0,c)/kernel
than it boots up .... but i still don't know how to change this entry
permanently. Please let me know if you know how to do this. Thanks.
"Patrick Simon" <psi...@iicast.net> wrote in message
news:3ce19ffd$1@news-fe-01...
David Vidal Rodríguez
>
> boot: 0:ad(0,c)/kernel
That looks singular to me, because with ad0c the _whole_ disk is meant, AFAIK,
isn't it?
Ciao!
--
------------------------------------------------------------------------
David Vidal R. (vidalrod <at> in DOT tum DOT de)
charon
> That looks singular to me, because with ad0c the _whole_ disk is meant,
> AFAIK, isn't it?
yep - I think the original poster has done something dodgy to his machine
ad0a is the one thats supposed to be '/'
--
"It took me fifteen years to discover that I had no talent for writing,
but I couldn't give up because by that time I was too famous."
-- Robert Benchly
charon
>
> Part Mount Size Newfs
> Ad0s1e / 60MB UFS Y
> Ad0s1a /var 200MB UFS-S Y
> Ad0s1b swap 512MB SWAP
> Ad0s1f /home 1000MB UFS-S Y
> Ad0s1g /netdrive 50000MB UFS-S N
> Ad0s1h /usr 6871MB UFS-S Y
gaah - / should be ad0s1a not s1e
what does your /etc/fstab say?
--
There can be no twisted thought without a twisted molecule.
-- R. W. Gerard
Patrick Simon
/dev/ad0s1e / ufs rw 1 0
is it possible to fix that without repartitioning my hdd? Or can i atleast
modify a config so that i don't have to manually type it each time i restart
my computer? Thanks.
Patrick Simon
"charon" <cha...@dssrg.curtin.edu.au> wrote in message
news:abtfhr$g0h$1...@ftp.curtin.edu.au...
charon
> it says the same ... :(
>
> /dev/ad0s1e / ufs rw 1 0
>
> is it possible to fix that without repartitioning my hdd? Or can i atleast
> modify a config so that i don't have to manually type it each time i
> restart my computer? Thanks.
the only thing I can think of is to edit the disklabel and /etc/fstab to
switch a with e. - BUT - I am not sure you can do this with a machine thats
already running (booting single user etc etc doesnt work - if you use ad0a
in any way then disklabel fails).
I think you will have to boot from other media and try to find some way of
running 'disklabel -r -e ad0' to switch the a and e entries (and also
switch fstab a and e entries)
disklabel -r -e ad0 should give something like
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 524288 0 4.2BSD 1024 8192 22 # (Cyl.0-520*)
b: 1048576 2621440 swap # (Cyl.2600*-3640*)
c: 19541025 0 unused 0 0 # (Cyl.0-19385*)
e: 2097152 524288 4.2BSD 1024 8192 22 # (Cyl.520*-2600*)
f: 2097152 3670016 4.2BSD 1024 8192 22 # (Cyl.3640*-5721*)
g: 6291456 5767168 4.2BSD 1024 8192 22 # (Cyl.5721*-11962*)
h: 7482401 12058624 4.2BSD 2048 16384 89 # (Cyl.11962*-19385*)
which you then alter to switch a: with e:
there is also another catch. disklabel will try to use vi so you may
have to partially mount some of the ad0 filesystems or else set
EDITOR=/bin/ed and use that (its primitive - e.g. 23s/a/e/ will change a to
e on line 23, w by itself means write, q means quit)
it may actually be quicker to redo the install
ps: if you can get the machine to boot single user from the ad0c device
that may be sufficient provided you can see what would normally be in ad0a.
--
Patageometry, n.:
The study of those mathematical properties that are invariant
under brain transplants.
Patrick Simon
freebsd :) But i decided to redo the installation since it's faster to
backup my data and to redo it again. But atleast i know the possiblities for
fixing the partion table ...
Patrick Simon
"charon" <cha...@dssrg.curtin.edu.au> wrote in message
news:abtqq0$mea$1...@ftp.curtin.edu.au...
David Vidal Rodríguez
> the only thing I can think of is to edit the disklabel and /etc/fstab to
> switch a with e. - BUT - I am not sure you can do this with a machine thats
> already running (booting single user etc etc doesnt work - if you use ad0a
> in any way then disklabel fails).
Looks like we have a partition-salad :-| . Try to boot from the recovery
CD (the second one of the Walnut Creek CD set), or from a floppy, and
try mounting each of the drives to see which is what. I *think* that
renaming the disklabel is possible, but it's a very dangerous practice.
If you can access your disklabel, make sure you write down the size of
each partition and the the block where it starts. Then try to create a
new label with the correct letters asigned to each partition - it's not
necessary that partition a starts up from the beginning...
Regards,
David.
charon
> Okay thanks again - it seems to me that you have a good knownledge of
> freebsd :) But i decided to redo the installation since it's faster to
I'm kindof responsible for helping out with a sysadmin course. Its kindof
like air traffic controlling when none of the pilots speak a common
language. And yes - sometimes a reinstall is the easiest way :-)
--
People need good lies. There are too many bad ones.
-- Bokonon, "Cat's Cradle" by Kurt Vonnegut, Jr.