Folks,
I've been trying to set up a new virtual (XEN) FreeBSD box (at a Gandi datacenter). Unfortunately, Gandi for the time being doesn’t offer anything else than 11.2. Alright. I go for that, then use freebsd-update to overhaul the system to 12.0. Unfortunately, as soon as the new kernel is written and the box rebooted, the root disk becomes unwritable because of SU+J errors:
Etc. Oodles of those lines. Writing on / is impossible (file system full errors). I tried fsck, first by changing / into ro mode, then back in rw. No dice. Tried to create another FreeBSD server, attach that root disk as a data disk and fsck it. No luck either. FSCK fixes a certain number of problems, but apparently that doesn’t solve the SU+J inconsistency.
I booted single user. Tried to FSCK from there. Still no biscuit:
Also, I've used TUNEFS to turn off every sort of journaling (-J, -j, -n) but the errors are still there, and FSCK doesn’t complain anymore.
I’m a bit at wits' end here, so if anyone knows a way out, I'd be forever beholden to them.
Thanks a lot of any help out of this predicament!
V.
I've been trying to set up a new virtual (XEN) FreeBSD box (at a Gandi datacenter). Unfortunately, Gandi for the time being doesn’t offer anything else than 11.2. Alright. I go for that, then use freebsd-update to overhaul the system to 12.0. Unfortunately, as soon as the new kernel is written and the box rebooted, the root disk becomes unwritable because of SU+J errors:
Code:
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 1, cgp: 0xc57d4dcd != bp: 0xebc30f19
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 2, cgp: 0x161e51ff != bp: 0xdff280c3
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 3, cgp: 0x303c6f0c != bp: 0xb6c61ff5
Etc. Oodles of those lines. Writing on / is impossible (file system full errors). I tried fsck, first by changing / into ro mode, then back in rw. No dice. Tried to create another FreeBSD server, attach that root disk as a data disk and fsck it. No luck either. FSCK fixes a certain number of problems, but apparently that doesn’t solve the SU+J inconsistency.
I booted single user. Tried to FSCK from there. Still no biscuit:
Code:
# fsck /
** /dev/gpt/gandiroot
USE JOURNAL? [yn] y
** SU+J Recovering /dev/gpt/gandiroot
** Reading 16777216 byte journal from inode 4.
RECOVER? [yn] y
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
WRITE CHANGES? [yn] y
** 3 journal records in 1536 bytes for 6.25% utilization
** Freed 3 inodes (0 dirs) 0 blocks, and 0 frags.
***** FILE SYSTEM MARKED CLEAN *****
# exit
Setting hostuuid: 9a1d5b35-e917-446e-851f-29b04a426102.
Setting hostid: 0x0b66b4e5.
Fast boot: skipping disk checks.
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 2, cgp: 0x161e51ff != bp: 0xdff280c3
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 3, cgp: 0x303c6f0c != bp: 0xe1a8319e
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 5, cgp: 0x0 != bp: 0x639c9405
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 9, cgp: 0x0 != bp: 0xe41dfdb5
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 17, cgp: 0x0 != bp: 0x66f5b199
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 1, cgp: 0xc57d4dcd != bp: 0xc38b47c3
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 4, cgp: 0x0 != bp: 0x21fb7f73
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 5, cgp: 0x0 != bp: 0x639c9405
UFS /dev/gpt/gandiroot (/) cylinder checksum failed: cg 6, cgp: 0x0 != bp: 0x37c2e95e
Also, I've used TUNEFS to turn off every sort of journaling (-J, -j, -n) but the errors are still there, and FSCK doesn’t complain anymore.
I’m a bit at wits' end here, so if anyone knows a way out, I'd be forever beholden to them.
Thanks a lot of any help out of this predicament!
V.