*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
c is a marker for the total capacity. It won't be used directly except for operations which affect/ wipe the whole disk. So trimming e, /home/, is probably the best option. Shrinking will mean backing up that partition and then erasing it. Depending on the geometry you might be able to grow /usr/ or add /usr/local/ but if you have the possiblity, I'd reinstall and make a separate /usr/local/ in the process.
Distribution: Arch Linux && OpenBSD 7.4 && Pop!_OS && Kali && Qubes-Os
Posts: 824
Original Poster
Rep:
i made some kind of mistake and got "loading err m" warning when booting.
i gave up and now have just xubuntu bridge, ill try later to dual boot bsd and buntu.
ERR M
Bad magic. The ELF “magic number” \7fELF in boot(8)'s header was not found. This indicates that the first block of boot(8) was not read correctly. This could be due to disk corruption, failing to run installboot(8), giving an invalid boot(8) program as the boot argument to installboot(8), or incorrect geometry translation.
Moving / resizing partitions is a possible cause. Re-running installboot(8) usually solves this kind of thing.
It's a problem caused by a change in the physical location of the file /boot, the second stage bootloader. Caused either by moving/deleting the file or by moving/resizing the root partition resulting in a changed location. The error message is issued by the first stage bootloader, stating that it did not find the second stage where expected.
As noted, installboot(8) will fix the problem. The installboot program is available to the admin while using the RAMDISK kernel, so booting installation media and requesting the (S)hell provides access to the program. The 2 stages -- biosboot and boot, respectively -- are already installed in /usr/mdec, or may be manually extracted from the baseXY fileset. I find mounting /usr easier.
Here's an example of the steps I take from the RAMDISK shell when I make this error. Every time I make it. In this example, the disk I damaged is "sd0" and I discover /usr is partition "e" when I read the fstab(5) output:
Code:
# mount /dev/sd0a /mnt
# cat /mnt/etc/fstab
.
.
.
# mount /dev/sd0e /mnt/usr
# cd /mnt/usr/mdec
# installboot -v -r /mnt sd0 biosboot boot
# reboot
I will most of the time select [a] to auto-generate partition sizes when I install OpenBSD. On occasion I will select [c] and customize the partition sizes and manually enter the partition names and the size of each partition.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.