Installation report (X11/ZFS problems inside)

Questions about the installation of FreeBSD

Installation report (X11/ZFS problems inside)

Postby kraileth » Tue Nov 15, 2016 9:39 am

Hi again! I've finally found the time to convert my laptop to GhostBSD (leaving TrueOS due to various issues). Since I faced some problems with it as well, I've decided to write this installation report. I had played with the pre-alphas a bit in VMs but for my main box I opted for Enoch.

1st installation attempt (failure)

First things first: From a *BSD perspective, my machine sucks. It's an ASUS K95V and the main reason I bought it was because it didn't come with Windows (it had Linux Mint on it). It uses Optimus technology, FreeBSD won't boot on it in EFI mode and it has a broken BIOS that wouldn't boot off a GPT partition in non-EFI mode... Back in the day when I was happy with Linux this was not a problem. However I would definitely not buy something like that again now that I'm aware of what to consider when buying hardware for *BSD. I'm stuck with it for now, though.

Both PC-BSD and TrueOS are able to start up and display the installer in graphical mode. Both detect Optimus. GhostBSD doesn't and I guess that leads to X11 choking and failing to start (I'll post the log below). This is probably the point where a first timer giving BSD a try would cancel the attempt and move on. However I'm already convinced that I want a FreeBSD system. And while I have no problem with just installing vanilla FreeBSD and then building my desktop environment myself, having something that provides a nice desktop out of the box is quite appealing. Also I'd really like something that I can recommend to people using Linux who'd like to give FreeBSD a try. A lot of people prefer to go from things they know (like X11/MATE/bash/...) to things they don't know (tcsh/pkg/rc.conf/...), though. Vanilla FreeBSD forces them to dive deeply into the later to even reach the former. Beside myself being lazy (and you guys are doing a great job with configuring MATE!) this is why I want to make a new home with GhostBSD and thus support the BSD desktop.

So I logged in as root, changed the kbdmap and ran 'Xorg -configure'. Then I copied the resulting file over /etc/X11/xorg.conf and ran 'service slim start'. That made the login manager come up and enabled me to log in and use the installer. I went with ZFS and dedicated the laptop's SSD to it, leaving the other drive alone. The installer copied the files and then failed to set up the bootloader. I got the "Installation Error" message which told me to report the issue to the GhostBSD issue system and include the pc-sysinstall.log file.

BTW: The link provided there is leading nowhere (Redmine 404)! This should be fixed, I guess.

2nd installation attempt (success)

I rebooted and repeated the previous steps. This time I chose custom UFS and FreeBSD's loader instead of GRUB. Everything worked as expected and the system booted fine afterwards. I had to overwrite the xorg.conf again but that's not a big deal.

While this setup is less than ideal (I'd really prefer ZFS), I can live with it for now. And I must say that in general I like my new desktop! I'm having some problems with GhostBSD, but I'll put that into another topic as it is not installation related.

Oh, and I'll of course gladly provide more info or help to test any proposed fixes if somebody want's to look into this (either the graphics or the ZFS installer issue)!

xorg.conf:
Code: Select all
[    15.988]
X.Org X Server 1.17.4
Release Date: 2015-10-28
[    15.988] X Protocol Version 11, Revision 0
[    15.988] Build Operating System: FreeBSD 10.1-RELEASE-p37 amd64
[    15.991] Current Operating System: FreeBSD ghostbsd 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
[    15.992] Build Date: 16 August 2016  04:25:31AM
[    15.992] 
[    15.992] Current version of pixman: 0.34.0
[    15.992]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[    15.992] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    15.992] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 15 05:04:24 2016
[    16.010] (II) Loader magic: 0x801510
[    16.010] (II) Module ABI versions:
[    16.010]    X.Org ANSI C Emulation: 0.4
[    16.010]    X.Org Video Driver: 19.0
[    16.010]    X.Org XInput driver : 21.0
[    16.010]    X.Org Server Extension : 9.0
[    16.010] (!!) More than one possible primary device found
[    16.010] (--) PCI: (0:0:2:0) 8086:0166:1043:10cc rev 9, Mem @ 0xf7400000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/65536
[    16.010] (--) PCI: (0:1:0:0) 10de:0de9:1043:10cc rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/65536
[    16.010] (==) Using default built-in configuration (21 lines)
[    16.010] (==) --- Start of built-in configuration ---
[    16.010]    Section "Device"
[    16.010]       Identifier   "Builtin Default fbdev Device 0"
[    16.010]       Driver   "fbdev"
[    16.010]    EndSection
[    16.010]    Section "Screen"
[    16.010]       Identifier   "Builtin Default fbdev Screen 0"
[    16.010]       Device   "Builtin Default fbdev Device 0"
[    16.010]    EndSection
[    16.010]    Section "Device"
[    16.010]       Identifier   "Builtin Default vesa Device 0"
[    16.010]       Driver   "vesa"
[    16.010]    EndSection
[    16.010]    Section "Screen"
[    16.010]       Identifier   "Builtin Default vesa Screen 0"
[    16.010]       Device   "Builtin Default vesa Device 0"
[    16.010]    EndSection
[    16.010]    Section "ServerLayout"
[    16.010]       Identifier   "Builtin Default Layout"
[    16.010]       Screen   "Builtin Default fbdev Screen 0"
[    16.010]       Screen   "Builtin Default vesa Screen 0"
[    16.010]    EndSection
[    16.010] (==) --- End of built-in configuration ---
[    16.010] (==) ServerLayout "Builtin Default Layout"
[    16.010] (**) |-->Screen "Builtin Default fbdev Screen 0" (0)
[    16.010] (**) |   |-->Monitor "<default monitor>"
[    16.011] (**) |   |-->Device "Builtin Default fbdev Device 0"
[    16.011] (==) No monitor specified for screen "Builtin Default fbdev Screen 0".
   Using a default monitor configuration.
[    16.011] (**) |-->Screen "Builtin Default vesa Screen 0" (1)
[    16.011] (**) |   |-->Monitor "<default monitor>"
[    16.011] (**) |   |-->Device "Builtin Default vesa Device 0"
[    16.011] (==) No monitor specified for screen "Builtin Default vesa Screen 0".
   Using a default monitor configuration.
[    16.011] (==) Automatically adding devices
[    16.011] (==) Automatically enabling devices
[    16.011] (==) Not automatically adding GPU devices
[    16.058] (==) FontPath set to:
   /usr/local/share/fonts/misc/,
   /usr/local/share/fonts/TTF/,
   /usr/local/share/fonts/OTF/,
   /usr/local/share/fonts/Type1/,
   /usr/local/share/fonts/100dpi/,
   /usr/local/share/fonts/75dpi/
[    16.058] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[    16.058] (II) The server relies on devd to provide the list of input devices.
   If no devices become available, reconfigure devd or disable AutoAddDevices.
[    16.058] (II) LoadModule: "glx"
[    16.070] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[    16.126] (II) Module glx: vendor="X.Org Foundation"
[    16.126]    compiled for 1.17.4, module version = 1.0.0
[    16.126]    ABI class: X.Org Server Extension, version 9.0
[    16.126] (==) AIGLX enabled
[    16.126] (II) LoadModule: "fbdev"
[    16.130] (WW) Warning, couldn't open module fbdev
[    16.130] (II) UnloadModule: "fbdev"
[    16.130] (II) Unloading fbdev
[    16.130] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    16.130] (II) LoadModule: "vesa"
[    16.130] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[    16.130] (II) Module vesa: vendor="X.Org Foundation"
[    16.130]    compiled for 1.17.4, module version = 2.3.4
[    16.130]    Module class: X.Org Video Driver
[    16.130]    ABI class: X.Org Video Driver, version 19.0
[    16.130] (II) VESA: driver for VESA chipsets: vesa
[    16.131] (--) Using syscons driver with X support (version 2.0)
[    16.131] (++) using VT number 9

[    16.153] (WW) Falling back to old probe method for vesa
[    16.153] (EE) No devices detected.
[    16.153] (EE)
Fatal server error:
[    16.153] (EE) no screens found(EE)
[    16.153] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[    16.153] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    16.153] (EE)
[    16.165] (EE) Server terminated with error (1). Closing log file.



pc-sysinstall.log:
Code: Select all
kern.geom.debugflags: 0 -> 16
kern.geom.label.disk_ident.enable: 0 -> 0
Deleting all gparts
Running: gpart destroy -F /dev/ada1
ada1 destroyed
Clearing gpt backup table location on disk
Running: dd if=/dev/zero of=/dev/ada1 bs=1m count=1
1+0 records in
1+0 records out
1048576 bytes transferred in 0.004744 secs (221029576 bytes/sec)
Running: dd if=/dev/zero of=/dev/ada1 bs=1m oseek=114469
dd: /dev/ada1: short write on character device
dd: /dev/ada1: end of device
5+0 records in
4+1 records out
4677632 bytes transferred in 0.011300 secs (413955282 bytes/sec)
Running gpart on /dev/ada1
Running: gpart create -s mbr -f active /dev/ada1
ada1 created
Running gpart add on /dev/ada1
Running: gpart add -a 4k -t freebsd -i 1 /dev/ada1
ada1s1 added
Running: gpart set -a active -i 1 /dev/ada1
active set on ada1s1
Running: gpart create -s BSD /dev/ada1s1
ada1s1 created
Running: gpart destroy -F /dev/ada1s1
ada1s1 destroyed
Running: gpart create -s BSD /dev/ada1s1
ada1s1 created
Running: gpart add -a 4k -s 90033M -t freebsd-zfs /dev/ada1s1
ada1s1a added
Running: gpart add -a 4k -s 24437M -t freebsd-swap /dev/ada1s1
ada1s1b added
NEWFS: /dev/ada1s1a - ZFS
Setting up ZFS boot loader support
Running: dd if=/boot/zfsboot of=/dev/ada1s1 count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.011483 secs (44588 bytes/sec)
Running: dd if=/boot/zfsboot of=/dev/ada1s1a skip=1 seek=1024
128+0 records in
128+0 records out
65536 bytes transferred in 0.010826 secs (6053513 bytes/sec)
Creating zpool system1 on /dev/ada1s1a
Running: zpool create -m none -f system1 /dev/ada1s1a
Running: sync
Running: glabel label swap0 /dev/ada1s1b
Running: sync
zfs create  -p system1/ROOT
Running: zfs create  -p system1/ROOT
zfs create  -p system1/ROOT/initial
Running: zfs create  -p system1/ROOT/initial
Running: zfs set mountpoint=/mnt system1/ROOT/initial
Stamping system1/ROOT/initial as bootfs
Running: zpool set bootfs=system1/ROOT/initial system1
Running: zfs set compress=lz4 system1/ROOT/initial
Running: zfs set atime=off system1/ROOT/initial
zfs create  -p system1/usr
Running: zfs create  -p system1/usr
Running: zfs set mountpoint=/mnt/usr system1/usr
Running: zfs set canmount=off system1/usr
Running: zfs set mountpoint=none system1/usr
zfs create  -p system1/var
Running: zfs create  -p system1/var
Running: zfs set mountpoint=/mnt/var system1/var
Running: zfs set canmount=off system1/var
Running: zfs set atime=on system1/var
Running: zfs set mountpoint=none system1/var
FOUND DVD: /dev/da0
pc-sysinstall: Starting Extraction
pc-sysinstall: Extraction Finished
Running chroot command: glib-compile-schemas /usr/local/share/glib-2.0/schemas/
Running chroot command: /usr/bin/cap_mkdb /etc/login.conf
Running chroot command: pw userdel -n ghostbsd
Running chroot command: rm -rf /home/ghostbsd
Running chroot command: cat /.tmpPass | pw useradd -n michael -c "michael" -h 0 -s "/bin/tcsh" -m -d "/home/michael" -g "wheel" -G "operator"
Running: rm /mnt/.tmpPass
Setting hostname: klappi1
Setting root password
Running chroot command: cat /.rootpw | pw usermod root -h 0
Running: rm /mnt/.rootpw
Running chroot script: /usr/local/bin/iso_to_hd
Running chroot command: pkg install -y de-libreoffice
Running: mount -t devfs devfs /mnt/dev
Running: cp /boot/zfs/zpool.cache /mnt/boot/zfs/
Running: ln -s ../zfs /mnt/boot/kernel/zfs
Running: cp /etc/hostid /mnt/etc/hostid
Running: chroot /mnt grub-install  --force /dev/ada1
Installing for i386-pc platform.
grub-install: warning: your core.img is unusually large.  It won't fit in the embedding area.
grub-install: error: filesystem `zfs' doesn't support blocklists.
EXITERROR: Error 1: chroot /mnt grub-install  --force /dev/ada1
Running: swapoff /dev/ada1s1b
swapoff: /dev/ada1s1b: Invalid argument
Unmounting: /mnt
Running: umount -f /mnt
Unmounting DVD/USB media: /cdmnt-install
Running: umount -f /cdmnt-install


dmesg:
Code: Select all
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016
    root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
VT(vga): resolution 640x480
CPU: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz (2294.84-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306a9  Family=0x6  Model=0x3a  Stepping=9
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7fbae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  Structured Extended Features=0x281<FSGSBASE,SMEP,ERMS>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 25769803776 (24576 MB)
avail memory = 24825917440 (23675 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <_ASUS_ Notebook>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
random: <Software, Yarrow> initialized
ioapic0 <Version 2.0> irqs 0-23 on motherboard
Cuse4BSD v0.1.36 @ /dev/cuse
module_register_init: MOD_LOAD (vesa, 0xffffffff80dc6510, 0) error 19
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
acpi0: <_ASUS_ Notebook> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_ec0: <Embedded Controller: GPE 0x17> port 0x62,0x66 on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xe000-0xe07f mem 0xf6000000-0xf6ffffff,0xe0000000-0xefffffff,0xf0000000-0xf1ffffff irq 16 at device 0.0 on pci1
vgapci1: <VGA-compatible display> port 0xf000-0xf03f mem 0xf7400000-0xf77fffff,0xd0000000-0xdfffffff irq 16 at device 2.0 on pci0
agp0: <IvyBridge mobile GT2 IG> on vgapci1
agp0: aperture size is 256M, detected 65532k stolen memory
vgapci1: Boot video device
xhci0: <Intel Panther Point USB 3.0 controller> mem 0xf7900000-0xf790ffff irq 16 at device 20.0 on pci0
xhci0: 32 bytes context size, 64-bit DMA
usbus0: waiting for BIOS to give up control
xhci0: Port routing mask set to 0xffffffff
usbus0 on xhci0
pci0: <simple comms> at device 22.0 (no driver attached)
ehci0: <Intel Panther Point USB 2.0 controller> mem 0xf7918000-0xf79183ff irq 16 at device 26.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci0
hdac0: <Intel Panther Point HDA Controller> mem 0xf7910000-0xf7913fff irq 22 at device 27.0 on pci0
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0xd000-0xd0ff mem 0xf2104000-0xf2104fff,0xf2100000-0xf2103fff irq 16 at device 0.0 on pci2
re0: Using 1 MSI-X message
re0: ASPM disabled
re0: Chip rev. 0x2c800000
re0: MAC rev. 0x00100000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: 10:bf:48:df:e9:65
pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
pci3: <ACPI PCI bus> on pcib3
ath0: <Atheros AR9485> mem 0xf7800000-0xf787ffff irq 17 at device 0.0 on pci3
ar9300_set_stub_functions: setting stub functions
ar9300_set_stub_functions: setting stub functions
ar9300_attach: calling ar9300_hw_attach
ar9300_hw_attach: calling ar9300_eeprom_attach
ar9300_flash_map: unimplemented for now
Restoring Cal data from DRAM
Restoring Cal data from EEPROM
Restoring Cal data from Flash
Restoring Cal data from Flash
Restoring Cal data from OTP
ar9300_hw_attach: ar9300_eeprom_attach returned 0
ath0: RX status length: 48
ath0: RX buffer size: 4096
ath0: TX descriptor length: 128
ath0: TX status length: 36
ath0: TX buffers per descriptor: 4
ar9300_freebsd_setup_x_tx_desc: called, 0x0/0, 0x0/0, 0x0/0
ath0: ath_edma_setup_rxfifo: type=0, FIFO depth = 16 entries
ath0: ath_edma_setup_rxfifo: type=1, FIFO depth = 128 entries
ath0: [HT] enabling HT modes
ath0: [HT] enabling short-GI in 20MHz mode
ath0: [HT] 1 stream STBC receive enabled
ath0: [HT] 1 RX streams; 1 TX streams
ath0: AR9485 mac 576.1 RF5110 phy 991.1
ath0: 2GHz radio: 0x0000; 5GHz radio: 0x0000
ehci1: <Intel Panther Point USB 2.0 controller> mem 0xf7917000-0xf79173ff irq 23 at device 29.0 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci1
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel Panther Point AHCI SATA controller> port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem 0xf7916000-0xf79167ff irq 19 at device 31.2 on pci0
ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahciem0: <AHCI enclosure management bridge> on ahci0
acpi_button0: <Power Button> on acpi0
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model Generic PS/2 mouse, device ID 0
battery0: <ACPI Control Method Battery> on acpi0
acpi_acad0: <AC Adapter> on acpi0
ppc0: cannot reserve I/O port range
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
est4: <Enhanced SpeedStep Frequency Control> on cpu4
est5: <Enhanced SpeedStep Frequency Control> on cpu5
est6: <Enhanced SpeedStep Frequency Control> on cpu6
est7: <Enhanced SpeedStep Frequency Control> on cpu7
random: unblocking device.
usbus0: 5.0Gbps Super Speed USB v3.0
fuse-freebsd: version 0.4.4, FUSE ABI 7.8
Timecounters tick every 1.000 msec
hdacc0: <Realtek ALC269 HDA CODEC> at cad 0 on hdac0
hdaa0: <Realtek ALC269 Audio Function Group> at nid 1 on hdacc0
pcm0: <Realtek ALC269 (Analog 2.0+HP/2.0)> at nid 20,33 and 24 on hdaa0
pcm1: <Realtek ALC269 (Internal Analog Mic)> at nid 18 on hdaa0
hdacc1: <Intel Panther Point HDA CODEC> at cad 3 on hdac0
hdaa1: <Intel Panther Point Audio Function Group> at nid 1 on hdacc1
pcm2: <Intel Panther Point (HDMI/DP 8ch)> at nid 5 on hdaa1
usbus1: 480Mbps High Speed USB v2.0
usbus2: 480Mbps High Speed USB v2.0
ugen0.1: <0x8086> at usbus0
uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
ugen2.1: <Intel> at usbus2
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus2
uhub0: 8 ports with 8 removable, self powered
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <ST1000DM003-9YN162 CC4B> ATA8-ACS SATA 3.x device
ada0: Serial Number Z1D1T4XR
ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 953869MB (1953525168 512 byte sectors)
ada0: quirks=0x1<4K>
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <SanDisk SDSSDX120GG25 R112> ATA8-ACS SATA 3.x device
ada1: Serial Number 121206400226
ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 114473MB (234441648 512 byte sectors)
ada1: Previously was known as ad6
ses0 at ahciem0 bus 0 scbus3 target 0 lun 0
ses0: <AHCI SGPIO Enclosure 1.00 0001> SEMB S-E-S 2.00 device
ses0: SEMB SES Device
cd0 at ahcich2 bus 0 scbus2 target 0 lun 0
cd0: <MATSHITA BD-CMB UJ160 1.00> Removable CD-ROM SCSI device
cd0: Serial Number WN63 002258
cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes)
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #6 Launched!
SMP: AP CPU #4 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #5 Launched!
SMP: AP CPU #7 Launched!
Timecounter "TSC-low" frequency 1147419288 Hz quality 1000
Root mount waiting for: usbus2 usbus1 usbus0
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
ugen0.2: <SuYin> at usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus1
ugen2.2: <vendor 0x8087> at usbus2
uhub4: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on usbus2
Root mount waiting for: usbus2 usbus1
uhub3: 6 ports with 6 removable, self powered
uhub4: 6 ports with 6 removable, self powered
ugen2.3: <Generic> at usbus2
Root mount waiting for: usbus2
ugen2.4: <vendor 0x05e3> at usbus2
uhub5: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/77.64, addr 4> on usbus2
uhub5: 4 ports with 4 removable, self powered
Root mount waiting for: usbus2
ugen2.5: <Logitech> at usbus2
Root mount waiting for: usbus2
ugen2.6: <TrulyErgonomic.com> at usbus2
ukbd0: <TrulyErgonomic.com Truly Ergonomic Computer Keyboard, class 0/0, rev 1.11/1.30, addr 6> on usbus2
kbd2 at ukbd0
Trying to mount root from ufs:/dev/label/rootfs0 [rw,noatime]...
re0: link state changed to DOWN
wlan0: Ethernet address: 74:e5:43:cf:97:15
ums0: <Logitech USB Laser Mouse, class 0/0, rev 2.00/56.01, addr 5> on usbus2
ums0: 8 buttons and [XYZT] coordinates ID=0
uhid0: <TrulyErgonomic.com Truly Ergonomic Computer Keyboard, class 0/0, rev 1.11/1.30, addr 6> on usbus2
re0: link state changed to UP
kraileth
Developer
 
Posts: 202
Joined: Sun Sep 04, 2016 3:30 pm
Has thanked: 28 times
Been thanked: 22 times

Installation report (X11/ZFS problems inside)


Re: Installation report (X11/ZFS problems inside)

Postby ASX » Tue Nov 15, 2016 11:40 am

Hi,

optimus support is not there, and this is going to be difficult for us, because we don't have optimus featured hardware.

FreeBSD won't boot on it in EFI mode and it has a broken BIOS that wouldn't boot off a GPT partition in non-EFI mode.

This could be the source of the issue: actually GhostBSD support ZFS only on GPT. (FreeBSD support ZFS on MBR too)

However you should be able to install GhostBSD in EFI mode. (using GPT and Grub2)
ASX
Developer
 
Posts: 542
Joined: Wed May 06, 2015 3:46 pm
Location: ITALY
Has thanked: 25 times
Been thanked: 36 times

Re: Installation report (X11/ZFS problems inside)

Postby ASX » Tue Nov 15, 2016 11:51 am

BTW: The link provided there is leading nowhere (Redmine 404)! This should be fixed, I guess.


Thanks for reporting: we have migrated GhostBSD website, forum a issue tracker to a new server, and specifically we changed bag tracker software from Mantis to Redmine.

It was supposed to be announced ... but our personal issues has interfered with our intentions, apologies for that.

This was a long awaited change, and we think that it will allow us to improve the project management.

The new issue tracker can be reached at http://issues.ghostbsd.org

All users are kindly requested to re subscribe there ... we had to move the issues manually and we decided to not move the users because many aren't interested anymore.
ASX
Developer
 
Posts: 542
Joined: Wed May 06, 2015 3:46 pm
Location: ITALY
Has thanked: 25 times
Been thanked: 36 times

Re: Installation report (X11/ZFS problems inside)

Postby kraileth » Tue Nov 15, 2016 5:50 pm

ASX wrote:Hi,

optimus support is not there, and this is going to be difficult for us, because we don't have optimus featured hardware.


I'm not sure if this is worth too much effort and time as probably not too many people are affected. Intel graphics seems to work fine and people who absolutely need the power of the nvidia card probably won't install FreeBSD/GhostBSD anyway. However if anybody wants anything tested, I'd volunteer for that (PC-BSD/TrueOS detect Optimus correctly, so some code for FreeBSD must already exist).

FreeBSD won't boot on it in EFI mode and it has a broken BIOS that wouldn't boot off a GPT partition in non-EFI mode.

This could be the source of the issue: actually GhostBSD support ZFS only on GPT. (FreeBSD support ZFS on MBR too)

However you should be able to install GhostBSD in EFI mode. (using GPT and Grub2)


Ah, I see! Thanks for explaining! So as GhostBSD is based on FreeBSD which does support it, it is a limitation with the installer, I guess? Is support for ZFS on MBR planned for the future or is this something that probably won't be supported? In that case I guess I have to resort to some FreeBSD mailing list and find somebody interested in fixing EFI for not so new ASUS laptops or stick to UFS for booting. :(
kraileth
Developer
 
Posts: 202
Joined: Sun Sep 04, 2016 3:30 pm
Has thanked: 28 times
Been thanked: 22 times

Re: Installation report (X11/ZFS problems inside)

Postby ASX » Sat Nov 19, 2016 1:24 pm

kraileth wrote: So as GhostBSD is based on FreeBSD which does support it, it is a limitation with the installer, I guess? Is support for ZFS on MBR planned for the future or is this something that probably won't be supported? In that case I guess I have to resort to some FreeBSD mailing list and find somebody interested in fixing EFI for not so new ASUS laptops or stick to UFS for booting. :(


Yes, there are limitations into the installer:
FreeBSD provide MBR support for ZFS install, but there (i386) FreeBSD create two pools, zroot and bootpol, (the reason is unknown to me), and after that bootpool is not imported upon first boot, so it is bugged upstream anyway.

That said, please remember that we mainly target desktop system (which usually imply single disk system) and there a ZFS install is not suggested, (ZFS require data redundancy for good safety).

MBR support is mainly retained for compatibility with already installed system where dual boot is desired, otherwise GPT already provide an MBR protective setup to allow boot from MBR only machines.
ASX
Developer
 
Posts: 542
Joined: Wed May 06, 2015 3:46 pm
Location: ITALY
Has thanked: 25 times
Been thanked: 36 times

Re: Installation report (X11/ZFS problems inside)

Postby kraileth » Sun Nov 20, 2016 2:05 am

ASX wrote:Yes, there are limitations into the installer:
FreeBSD provide MBR support for ZFS install, but there (i386) FreeBSD create two pools, zroot and bootpol, (the reason is unknown to me), and after that bootpool is not imported upon first boot, so it is bugged upstream anyway.


I'm not sure if that's necessarily a bug. The separate bootpool is created on amd64, too, if you choose MBR, not just on i386, BTW. I haven't looked at bsdinstall lately, but when I was tinkering with installing FreeBSD manually (to dualboot with OpenBSD) in february or so, I dug into these things a little bit. My conclusion was that the separate pool is not always needed but since the Auto (ZFS) option allows for disk encryption with GELI, an unencrypted boot partition/pool might be needed. That's probably why it's there in the first place. For 11.0 a separate pool is no longer needed for GELI encrypted partitions, as far as I know. I don't have the time to look at that now, but I probably could try to figure out if the MBR bootpool is just a leftover or, if it is still needed, what the reason for it is.

That said, please remember that we mainly target desktop system (which usually imply single disk system) and there a ZFS install is not suggested, (ZFS require data redundancy for good safety).


Well, that's one topic where I disagree. Please let me explain why: It's pretty obvious that ZFS has a lot of advantages for more advanced storage needs - be it on a server or a NAS or whatever. But I claim that it's very useful on the desktop, too. Laptops are one thing, but for the common desktop it's not so much a problem to go with a two disk setup and create a mirrored zpool. Actually I'd probably go with a single SSD drive for the system (that doesn't need redundancy) and two bigger drives for a z-mirror. But that's just me. Still even if we assume just one drive, ZFS offers huge benefits over UFS! Here are just three of them (I'm just a ZFS novice myself; the gurus could probably go on for pages here):

1. Unmatched flexibility. Create and destroy datasets as you need them instead of partitioning your drive at install time and be stuck with it until you decide to throw the system away and start over. Even though GPT helped a lot in doing away with that "extended partitions" workaround for the 4 partition limit of MBR, it's still unflexible. Real world example: I once gave my laptop to a friend for a few days because his broke and he couldn't get a replacement quickly. I admit that this was years ago and said laptop was running win2k back then. Today it would be running FreeBSD (or probably rather: GhostBSD). I'd create a new user for him and would like to mount that user's home dir with different permissions (e.g. noexec). Retrofit that into a classical setup that didn't plan for such a case! With ZFS it's a new dataset and life is good.

2. COW. No fsck after unclean shutdown. Sure, fsck is not too bad these days since we have journals. Still it's a nice not to have to fsck. But what about (nearly) instant snapshots? While UFS can do snapshots, too, it's really, really epic to be able to snapshot several gigs in just a second! And not having the snapshot taking any considerable amount of diskspace to begin with as only the delta is stored makes this even better.

3. Safety. ZFS's strong safety comes primarily from using VDEVs that provide redundancy, that's true. But even if you opt for a simple striped VDEV, you're probably going to be fine. In any case your data won't be less secure than if you chose to go with UFS. On the contrary: ZFS uses checksumming and will at least be able to tell you if some data that you asked for is flawed. Other filesystems will happily return garbage and leave it to you to notice before the corruption spreads into your backups and the last good copy is rotated away... If you care for your data, scrubs are an excellent utility with which ZFS has a real benefit over other filesystems. And even if you have a simple VDEV without redundancy, there's still the copies property that you can tune per dataset. You just tell ZFS "hey, this stuff is important!" and it will store n copies of it on the provider for you (and even automatically take care to put them in places far from each other so that it's less likely that both are affected if e.g. you start to dd if=/dev/zero the wrong device).

There are other things like boot environments, send/receive, etc., which are also totally useful on the desktop. PC-BSD definitely is a desktop focused FreeBSD variant and the've been ZFS only for several releases now! Don't get me wrong, please. I'm not against UFS in any way. In fact I like it a lot that GhostBSD supports installing to UFS, too. There are enough cases where ZFS simply doesn't make sense (for me that's especially systems with little RAM). But I would definitely not discourage ZFS usage for the desktop in general.

Two things that might draw me away from using ZFS-on-root with GhostBSD (even if it would work with MBR) are: 1) 10.3 needs GRUB to boot from it. I don't like GRUB much. Fortunately when GhostBSD is updated to 11.0 that's an issue of the past. 2) ZFS is CDDL'ed. Like a lot of *BSD people, I'm a permissive license enthusiast and try to avoid copyleft when it's possible. I'd totally love if a filesystem guy ported over HAMMERfs (http://www.dragonflybsd.org/hammer/) from DragonFly. Until something like that happens (which may just be wishful thinking anyways...) ZFS is just too good to lose.

MBR support is mainly retained for compatibility with already installed system where dual boot is desired, otherwise GPT already provide an MBR protective setup to allow boot from MBR only machines.


As far as I know the protective MBR is installed by default when FreeBSD uses GPT. Unfortunately that doesn't stop my machine to no longer recognize the whole disk (!!) and disregard it for booting. I do not love MBR. Not at all. But so far I'm currently stuck with it. I should get less crappy hardware, I know. But I won't be able to afford that any time soon. :(
kraileth
Developer
 
Posts: 202
Joined: Sun Sep 04, 2016 3:30 pm
Has thanked: 28 times
Been thanked: 22 times

Re: Installation report (X11/ZFS problems inside)

Postby ASX » Sun Nov 20, 2016 8:52 am

The bug, related to FreeBSD MBR based ZFS setup is that the bootpool is not imported at first boot, as required, not that a bootpool exists, aside experiencing the problem myself, it was reported on freebsd forum too, more than one time.

ZFS on single disk:
Please note that I moved to FreeBSD/GhostBSD exactly for one thing: ZFS. Initiailly I was thinking exactly like you, there are many advantages to use ZFS, even on single disk system.

I changed my mind later, after reading carefully several man/docs pages), thinking at what happen when a single bit get corrupted:
the related disk is put "offline" and the pool must rely on the remaining disks; that's fine for a mirrored system, but on single disk it means no zpool at all.

moreover, even when a user will have the capability to import a corrupted pool (something I do not expect from an average desktop user):
from zpool manpage:
"A single case of bit corruption can render some or all of your data unavailable."

The above statement make a lot of sense, although it can be very unlikely and very rare, it is also true.
ASX
Developer
 
Posts: 542
Joined: Wed May 06, 2015 3:46 pm
Location: ITALY
Has thanked: 25 times
Been thanked: 36 times

Re: Installation report (X11/ZFS problems inside)

Postby kraileth » Mon Nov 21, 2016 5:08 pm

ASX wrote:I changed my mind later, after reading carefully several man/docs pages), thinking at what happen when a single bit get corrupted:
the related disk is put "offline" and the pool must rely on the remaining disks; that's fine for a mirrored system, but on single disk it means no zpool at all.


First: I have a hard time believing that. There have been a lot of loud claims that you shouldn't use ZFS without ECC RAM because otherwise a single bit flip could mean your data is toast. However a lot of people from the FreeBSD project that I hold in very high esteem when it comes to ZFS have repeatedly stated that this is somewhat of a myth.

I cannot see how a single corrupted bit (leading to a corrupted byte) could bring down your whole pool. If that byte affects your data and ZFS has no copies of that it will tell you that this file is corrupted when you try to access it. The pool as a whole should still be working. If the bad byte affects metadata that's far more severe. However by default ZFS keeps multiple copies of that metadata in different locations. Especially the precious uberblock is saved in various locations. If you manage to lose all uberblocks at once, the problem that you are experiencing with the disk is simply disastrous and no filesystem will be able to save you in that case. If you lose all superblocks on UFS or EXTx you're done for, too. That's not a specific disadvantage or risk with ZFS.

moreover, even when a user will have the capability to import a corrupted pool (something I do not expect from an average desktop user):
from zpool manpage:
"A single case of bit corruption can render some or all of your data unavailable."

The above statement make a lot of sense, although it can be very unlikely and very rare, it is also true.


That does sound dramatic indeed. But I fail to understand what they mean by this. Unavailability of some data due to bitrot? Sure thing. Checksum mismatch leads to ZFS refusing to give you the bad (or thought bad) data. But what needs to happen to make all data unavailable? You'd have to tune ZFS to not keep copies of important metadata that it keeps by deafult to be able to do this, I think. And if you are really determined to shoot yourself in the foot it's fine that ZFS will not stop you from doing it. I don't think there's any filesystem that will effectively stop anyone who really wants to destroy it from thrashing his or her data.
kraileth
Developer
 
Posts: 202
Joined: Sun Sep 04, 2016 3:30 pm
Has thanked: 28 times
Been thanked: 22 times

Re: Installation report (X11/ZFS problems inside)

Postby ASX » Mon Nov 21, 2016 6:51 pm

I cannot see how a single corrupted bit (leading to a corrupted byte) could bring down your whole pool. If that byte affects your data and ZFS has no copies of that it will tell you that this file is corrupted when you try to access it.


not exactly, the behavior is configurable (see man zpool, param failmode) and range from:
- block all I/O
- continue, but with read only access
- panic

Must be noted that fall under the definition of "catastrophic failure", like happens when a pool has no more redundant data available.
In case of single disk pool that means that a single checksum failure will put the disk offline and the pool in a "catastrophic failure" state.

I have not been able to replicate that behavior in practice, but I would like to hear that I'm wrong, In the meantime I put out the warning.

Also, whether or not you will be able to recover your data later is a different problem.

The ECC RAM is a debatable requirement, certainly ECC RAM is an improvement over NON ECC. system.
ASX
Developer
 
Posts: 542
Joined: Wed May 06, 2015 3:46 pm
Location: ITALY
Has thanked: 25 times
Been thanked: 36 times

Re: Installation report (X11/ZFS problems inside)

Postby tankist02 » Thu Dec 01, 2016 1:17 am

For me ZFS is too much resource hungry and slow for a simple desktop system. Its killer features are more suited for servers, I think.
tankist02
 
Posts: 14
Joined: Wed Sep 04, 2013 8:46 pm
Has thanked: 0 time
Been thanked: 1 time

Next

Return to Installing GhostBSD

Who is online

Users browsing this forum: No registered users and 1 guest