ZFS: can't read MOS of pool
Trond Endrestøl
Trond.Endrestol at fagskolen.gjovik.no
Thu Jul 25 20:23:49 UTC 2013
On Thu, 25 Jul 2013 20:45+0200, ?ukasz W?sikowski wrote:
> W dniu 2013-07-25 18:40, Trond Endrestøl pisze:
>
> >> Any hints how to go from here?
> >
> > I'm only subscribed to freebsd-stable@, but as far as I can tell, no
> > one from freebsd-fs@ nor freebsd-stable@ has yet replied. I'm only
> > replying to freebsd-stable at .
> >
> > First, just some quick questions:
> >
> > Have you by chance upgraded the pool format without upgrading the boot
> > blocks? Or was the pool already at 5000?
> >
> > You didn't mention if you have made any attempt at updating the boot
> > blocks after playing with ezjail-admin.
> >
> > Perhaps you should consider updating the boot blocks once more:
> >
> > 1. Boot from the live CD.
> >
> > 2. Import the pool read-only without mounting any fs:
> >
> > zpool import -f -N -o readonly=on klawisz
> >
> > 3. Mount the root fs read-only:
> >
> > mount -r -t zfs klawisz/ROOTFS /tmp/zroot
> >
> > 4. Update the boot blocks from the files stored in the root fs:
> >
> > gpart bootcode -b /tmp/zroot/boot/pmbr -p /tmp/zroot/boot/gptzfsboot -i 1 ada0
> >
> > 5. Unmount the root fs:
> >
> > umount /tmp/zroot
> >
> > 6. Reboot the system, do NOT export the pool.
> >
> > Hopefully, the updated gptzfsboot stored in ada0p1 will be able to
> > read the MOS.
> >
> > That's all I can think of at the moment.
> >
> > Best of luck.
>
> Thank you for your reply. The pool was created with version 5000. I have
> updated the boot blocks before (but with exporting pool after). I don't
> think that ezjail-admin has anything to do with booting.
Never ever leave a pool you intend to boot from in the exported state.
Period. ;-)
At least that was a big no-no when I started using ZFS a couple of
years ago. Maybe this has changed since FreeBSD no longer relies on
the zpool.cache file.
> I did as you suggested and it didn't help, still MOS can't be read. I'm
> pretty sure I can reproduce this problem. I will try to do detailed
> guide and post it here.
Reading through your post once more,
http://pastie.org/private/mtfhkx0wx0vve29xn0plw , I noticed the
following:
1. The bootfs property is set to klawisz/ROOTFS for the klawisz pool.
2. The mountpoint property is set to / for the klawisz filesystem.
3. The mountpoint property is set to legacy for the klawisz/ROOTFS filesystem.
Maybe item 2 is the cause of all this confusion. I see nothing wrong
with items 1 and 3.
Perhaps you should reset the mountpoint property for klawisz, using:
zfs set mountpoint=legacy klawisz
At the same time you may let klawisz/ROOTFS inherit the mountpoint
property from klawisz by running:
zfs inherit mountpoint klawisz/ROOTFS
You should also check the mountpoint properties of all the other
filesystems you intend to mount automatically.
--
+-------------------------------+------------------------------------+
| Vennlig hilsen, | Best regards, |
| Trond Endrestøl, | Trond Endrestøl, |
| IT-ansvarlig, | System administrator, |
| Fagskolen Innlandet, | Gjøvik Technical College, Norway, |
| tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, |
| sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. |
+-------------------------------+------------------------------------+
More information about the freebsd-stable
mailing list