Bug 195855 - freebsd-update damages file system after 10.0 -> 10.1 install
Summary: freebsd-update damages file system after 10.0 -> 10.1 install
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 10.0-RELEASE
Hardware: i386 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2014-12-10 16:21 UTC by Barry Friedman
Modified: 2016-12-20 22:10 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Barry Friedman 2014-12-10 16:21:09 UTC
See: http://lists.freebsd.org/pipermail/freebsd-questions/2014-December/262896.html

System failed to boot after install phase.  

File system on amrd0 was changed from GPT to MBR and was not recognized as valid.

Worked around by manually commenting out entry in fstab.

Have not attempted to recover the bad file system (help on this would be

Logs of the update are available.

gpart  show -lp
=>        63  1171783617  amrd0  MBR  (559G)
          63  1171783617         - free -  (559G)

=>       34  286515133    amrd1  GPT  (137G)
         34        128  amrd1p1  (null)  (64K)
        162  276823936  amrd1p2  (null)  (132G)
  276824098    8388608  amrd1p3  (null)  (4.0G)
  285212706    1302461           - free -  (636M)

dmesg output:
amr0: delete logical drives supported by controller
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 572160MB (1171783680 sectors) RAID 5 (optimal)
amrd1: <LSILogic MegaRAID logical drive> on amr0
amrd1: 139900MB (286515200 sectors) RAID 1 (optimal)

CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2791.05-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf29  Family = 0xf  Model = 0x2  Stepping = 9