similar to: Reinstalling boot blocks on a ZFS-only system

Displaying 20 results from an estimated 1000 matches similar to: "Reinstalling boot blocks on a ZFS-only system"

2013 Jul 22
2
ZFS: can't read MOS of pool
Hi, I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm getting: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool klawisz gptzfsboot: failed to mount default pool klawisz Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM, 400 GB of local storage with SCSI Controller type: Default (lsi). I'm not sure what I did to
2012 Mar 24
3
FreeBSD 9.0 - GPT boot problems?
Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many
2013 Dec 09
1
10.0-BETA4 (upgraded from 9.2-RELEASE) zpool upgrade -> boot failure
Hi, Is there anything known about ZFS under 10.0-BETA4 when FreeBSD was upgraded from 9.2-RELEASE? I have two servers, with very different hardware (on is with soft raid and the other have not) and after a zpool upgrade, no way to get the server booting. Do I miss something when upgrading? I cannot get the error message for the moment. I reinstalled the raid server under Linux and the other
2013 Mar 25
2
gptzfsboot: error 4 lba 30
Hi. On one of my fresh installed servers I am seeing the following output during boot: gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 30 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot: error 4 lba 31 gptzfsboot:
2012 Aug 04
2
FreeBSD 9.0 - GPT boot problems?
> On Fri, Aug 3, 2012 at 3:09 PM, Torfinn Ingolfsen > <torfinn.ingolfsen@getmail.no> wrote: > > Just a short update on this machine (Acer Aspire X1470) and the GPT / UEFI situation. > > Today I set up another partition, EFI system partition. The partyitions now looks like this: > > root@kg-vm2# gpart show ada0 > > => 34 250069613 ada0 GPT (119G)
2012 Apr 30
1
FreeBSD 9 "gptboot: invalid backup GPT header" error (boots fine though)
I've been deploying FreeBSD 9 without issue on a number of near-identical servers for a client, but have run into an interesting annoyance when I hit the two DB servers. These DB servers have an LSI 3ware 9750-8i (running a 6 disk RAID 10 in a single 3TB virtual volume) which puts them apart from the other two servers in this cluster (which don't show either issue I am about to
2013 Jan 24
2
RFC: Suggesting ZFS "best practices" in FreeBSD
>> #1. Map the physical drive slots to how they show up in FBSD so if a >> disk is removed and the machine is rebooted all the disks after that >> removed one do not have an 'off by one error'. i.e. if you have >> ada0-ada14 and remove ada8 then reboot - normally FBSD skips that >> missing ada8 drive and the next drive (that used to be ada9) is now
2013 Feb 21
1
IPMI serial console
Hi all, A recent thread inspired me to try getting a proper serial console working on a Supermicro X9SCL motherboard with IPMI. However I find that while I see loader messages and the getty I enabled after boot I don't get any kernel messages which does somewhat limit the utility.. The BMC creates COM3 (/dev/cuau2) which works with getty. I modified /boot/loader.conf like so..
2011 Dec 15
31
Can I create a mirror for a root rpool?
On Solaris 10 If I install using ZFS root on only one drive is there a way to add another drive as a mirror later? Sorry if this was discussed already. I searched the archives and couldn''t find the answer. Thank you.
2013 Jun 19
3
shutdown -r / shutdown -h / reboot all hang and don't cleanly dismount
Hello -STABLE@, So I've seen this situation seemingly randomly on a number of both physical 9.1 boxes as well as VMs for I would say 6-9 months at least. I finally have a physical box here that reproduces it consistently that I can reboot easily (ie; not a production/client server). No matter what I do: reboot shutdown -p shutdown -r This specific server will stop at "All buffers
2012 Sep 18
8
Collecting entropy from device_attach() times.
Hi. I experimented a bit with collecting entropy from the time it takes for device_attach() to run (in CPU cycles). It seems that those times have enough variation that we can use it for entropy harvesting. It happens even before root is mounted, so pretty early. On the machine I'm testing it, which has minimal kernel plus NIC driver I see 75 device_attach() calls. I'm being very careful
2013 Jul 01
1
ZFS Panic after freebsd-update
Hello, I have not had much time to research this problem yet, so please let me know what further information I might be able to provide. This weekend I attempted to upgrade a computer from 8.2-RELEASE-p3 to 8.4 using freebsd-update. After I rebooted to test the new kernel, I got a panic. I had to take a picture of the screen. Here's a condensed version: panic: page fault cpuid = 1 KDB:
2004 Sep 20
5
Cluster size not supported
Hello all, I just installed wine from CVS on fakewindows configuration, but I can't seem to get anything to work well. I tried installing the DCOM98, but I get "Cluster size not supported." The same error occurs when I execute just about anything. Has anyone encountered this or know what it is referring to? Thanks in advance, Leo
2012 Mar 28
2
problem: bsdlabel
hail, I partitioned the disk this way: fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=12161 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size
2013 Jul 17
1
bce and "Warning: bootcode thinks driver is absent."
Recently under amd64 and 9.1-STABLE I am seeing issues with the bce driver. Message is "Warning: bootcode thinks driver is absent". After this message, the box appears to be wedged. After rebooting, it got the same message during fsck. So we installed 9.2 pre-release using a snapshot iso from 7/13/13. Shortly after boot we got the same message. We are now in the process of
2008 Oct 23
1
After an update stable doesn't boot
Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold
2010 Nov 11
3
Booting fails with `Can not read the pool label'' error
I''m still trying to find a fix/workaround for the problem described in Unable to mount root pool dataset http://opensolaris.org/jive/thread.jspa?messageID=492460 Since the Blade 1500''s rpool is mirrored, I''ve decided to detach the second half of the mirror, relabel the disk, create an alternative rpool (rpool2) there, copy the current BE (snv_134) using beadm
2013 Jun 04
3
Serial terminal issues
I can't seem to get my serial terminal to work with my new system. I had a serial terminal connected to my old system that worked great and copied /boot.config, /boot/loader.conf and /etc/ttys settings over from it. The new system has a Gigabyte GA970A-UD3 board with just a serial header on the board. I bought a serial connector backplate in an electronics store and connected it to the
2008 Nov 19
7
Upgrading from a single disk.
Suppose I have a single ZFS pool on a single disk; I want to upgrade the system to use two different, larger disks and I want to mirror. Can I do something like: - I start with disk #0 - add mirror on disk #1 (resilver) - replace first disk (#0) with disk #2 (resilver) Casper
2006 Jan 16
1
fdisk on mounted disks ?
the other day i was trying to create a new freebsd slice on the same disk i booted from (on a freshly updated RELENG_6) and both fdisk and sysinstall failed with some error (i think they could not write on the disk, or something similar). boot -s did not seem to help, either. I remember vaguely some time ago a bit of discussion on this topic, but cannot recall the outcome nor any keyword to