Search results

  1. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    (Can't edit my last reply, nor the first, not long enough here yet, but if someone could mark it as solved? Thanks)
  2. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    Ah, thanks for the explanation. I'm happy it works now, overjoyed ;) Now rebuilding my ports, kernel and I'm up and running again, ready for the next challenge, trying to freebsd-update my jails :) Thanks for the great help all!
  3. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    Indeed, the only GPT warning was during boot, but nothing in dmesg anymore, sounds good. Now to try the 8.2 GENERIC :) (Sorry DutchDaemon, I kept an eye out but missed the formatting of devices)
  4. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    Yes, I did it with the new mirror, but due to some mistakes on my side, gm0 was my new (and only) mirror ;) I accidentally (don't ask how), managed to not be able to boot into my old mirror anymore, so I went in with a livecd and fixit, broke up the mirror, repartitioned ad6 with the above...
  5. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    I'm halfway there :) Just got one last question I'm unsure about (found different sources using different statements) When you say "install bootblocks", would this do? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 mirror/gm0 Or do I need different switches?
  6. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    Yes, I partitioned it before the mirror :/ Is it possible to repartition my current disks *without* losing any data on it? My guess I came up with while thinking about it today, after reading your answer: - I need to boot using fixit mode - Somehow remove the current partitioning scheme...
  7. CumpsD

    Upgrade to 8.2 - GPT became corrupt?

    Yesterday I tried to do a binary upgrade to 8.2-RELEASE (using freebsd-update), coming from 8.1-RELEASE-p2. The upgrade process went fine, up until the point I rebooted using the GENERIC kernel (nextboot -k GENERIC). After rebooting, I was unable to mount my root filesystem. After some...
Back
Top