*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using openbsd-3.5-release and it was working great until the last day when i got this message right before it went single user mode: "Bad superblock:values in superblock disagree with those in first alternate" and "/dev/rwd1g:unexpected consistensy;run fsck_ffs manually".
I have ran fsck_ffs but it doesn't solve the problem.
I really need to work on bsd and don't know where to begin on solving this problem (goggling didn't help), so I ask for your help now.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
You should be able to run
# fsck -b <alternative superblock>
where <alternative superblock> is the number of where the next alternative is stored. This is exactly why multiple copies of the superblock are written to a file system when it's created with newfs.
I already did that but it didn't solve the problem.
I have removed /dev/wd1g from fstab temporarily to be able to boot in the system, but I would llike to solve this as fast as i can. As I don't understand much yet about this I am open to any solution that doesn-t blow the rest of the system. As for that partition, could I do something to solve the issue?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.