Search results

This has been resolved — See followup post — https://forums.freebsd.org/threads/unable-to-boot-from-disk.68673/#post-410016 It wasn't related to the upgrade from p4 to p5 — it was related to the fact that I created another zfs pool, which triggered another bug (or feature?).

With the help of Toomas, problem was traced to the BIOS bug which caused system freeze while attempting to probe partitionless disks, which fixed with the following patch (currently in review).

I believe I tried this already in the past, but re-tested today again — nope, same result: it gets stuck.

I copied zfsloader from 11.2 — and saved it as /boot/zfsloader.old — attempted to boot and still got stuck. I sent you an email.

Output of the beadm was: # beadm list BE Active Mountpoint Space Created default NR / 2.5G 2018-11-01 08:30 So I have single boot environment and it active and will be used on next reboot. Ok, so I did this: # gpart bootcode -p /boot/gptzfsboot -i 1 ada0 partcode written...

No. I get access to the loader menu when I boot from CD. I just upgraded it to 12.0 — would upgrade install new boot loaders, or do I need manually upgrade it? One of the posts I found somewhere suggested to do this — tried and failed. Is there way to remove it?

Boot order set correctly, checked and confirmed. I have zfs_load, but not vfs.root.mountfrom — but my understanding, that loader is not loaded at that time — my problem happening because the loader wasn't loaded. Am I wrong? When booting from CD, I see list of BIOS drives, then few lines about...

Boot drives are not connected to the LSI controller. They using motherboard's one. Update: tried it anyway — didn't help.

I've posted earlier about my issues with booting my systems. When system boots up, it shows list of bios drives, and then spinner starts for about two-three seconds, after which it will get stuck. Waited 30 or so minutes without luck, didn't move. When booting from ISO (via IPMI — it's...

This was related to the loader -- https://www.freebsd.org/security/advisories/FreeBSD-EN-18:15.loader.asc But I can't figure out how this change affected boot process.

Hi, This morning I've upgraded two servers with latest security updates which this time were 11.2-RELEASE-p5. Upgrades went exactly same way: # freebsd-update fetch # freebsd-update install # reboot After reboot, systems got stuck in following screen: I recently made change to the...

Hello, I've got two servers which were recently upgraded from 9.2 to FreeBSD 10.1 (One was upgrade, second one was clean install due to hardware failure). Before upgrade, I was getting daily emails between 3 and 4am daily, but after upgrade, these emails started to arrive much later (8-9-10am)...

[SOLVED] FreeBSD 9.1; bridge0 and default gateway issue Looks like issue was due to quick exhaust of mbufs. As FreeNAS's wiki points out, this is common on multiport em and igb cards and mostly had nothing to do with bridge (correct me if I'm wrong). So after I added following lines into...

sorry. igb0 correct name, em0 - typo.

I've got a FreeBSD 9.1-RELEASE-p1 system with three nics, I'm using: igb0, sfxge1 and sfxge2. igb0 used for internet access and is default gateway. Other two nics, I need to use to create bridge0. When system is booted, I execute following commands and get bridge up and running without any...

thanks. i'll try that tomorrow, as I still didn't find solution to this problem...

Hi, I have couple users who need to have access to svn server (subversion+apache) located in different location. Those users come to us via vpn with very limited access. I've setup squid 3.1.4_1 server on my freebsd 7.3 box. Some files commit properly. Some files won't commit with errors...

stupid me. for some reason, I did makeworld, but never managed to install it - that' the reason why I was getting those strange error messages. Thanks for help.

@phoenix: You're right - I'm using single disk on 3ware 9650SE controller. # zpool create tank mirror da4 da5 cannot create 'tank': invalid argument for this pool operation and here is what makes me wonder, after I ran the command: # zpool status internal error: out of memory # zpool...

I tried any other name - same error message. No, drives are not used by the system.