Ok, so maybe the problem was my way of copying my disk layout from the old disk (the one before that) to this one. I still have a pool with the same name that I cannot destroy (it's faulty hence I cannot import and destroy it). Is it possible to copy all data from it to another disk, create the...
The disk is really new, like six weeks and SMART shows no abnormality. I highly doubt it's faulty. I find it much more likely that I messed up something, but I'm not sure how to find out what.
I upgraded from 11.1-RELEASE and I'm able to import the pool as well as read all files from it (on a live system). The disk cannot have become bad from just kernel upgrading can it?
Since my latest change, I can't get to the boot prompt anymore, I believe I'm in some other kind of prompt that...
Hello,
after initiating the 11.2 upgrade on Sunday evening and finishing the kernel part of it,
the following reboot left me with a ZFS error:
ZFS: i/o error - all block copies unavailable
ZFS: can't find pool by guid
The pool layout is simple, just a single disk, so no RAID.
I find it...
I'd really like to know what's causing the segmentation fault. On my system, if I remove wins from the hosts line in /etc/nsswitch.conf, everything works normally. Apparently even when doing ls or vi some kind of host lookup is performed which mysteriously fails with the new kernel or parts of...
Very interesting, for me the removal of /etc/nsswitch.conf works (even if /usr/local/lib/libtspi.so is present) and the system doesn't segfault anymore.
/etc/nsswitch.conf
group: compat
group_compat: nis
hosts: files wins dns
networks: files
passwd: compat
passwd_compat: nis
shells: files...
My system is running again after I extracted base.txz from 10.1 to / (not overwriting /usr, /etc, /var and the likes). Still, vim was segfaulting when closing it. I could trace this back to a faulty libtspi.so (e.g. used by gnutls). As long as it resides in /usr/local/lib it's causing segfaults...
My system seems to be running again (preliminary at least). I booted from USB and replaced /bin, /lib and /libexec. Somehow freebsd-update must have corrupted at least one of these directories.
Another run of freebsd-update screws up again. I have no idea what could be the cause. Currently I'm...
I faced the same problem today when upgrading from 10.0-RELEASE to 10.1-RELEASE. I am using ZFS and a GELI encrypted root. Almost every command segfaults, ls and mount still work, however. Currently I'm desperately trying to recover the system.
Edit: Simple recovery failed, now the system is...
So wait, did you _enable_ this option or disable it in order to get it to work? Because the Bugzilla you linked says that USB does not work if the option is enabled.
Interesting! But unfortunately by BIOS does not have such an option. What does it do actually? For me, as written before, it sometimes helped to disable ACPI or the APIC but this never lasted more than one minor version. It would really be great to get to the bottom of this.
Edit: Ah, I see...
I don't think it's a GELI issue but rather a USB keyboard driver problem. Most likely you will also not get a
keyboard in the mountroot prompt (as in my case). You could try asking the question on the freebsd-usb mailing list again but this seems to be a recurring bug or rather a symptom of an...
(Somewhat delayed reply) Yes I tried that - no keypress whatsoever was accepted. The only solution for my problem was to switch to new hardware and use the amd64 architecture. I think the problem was rooted in the interplay of USB driver, probably faulty hardware/firmware and other intricacies...
Just when I was about to update my ports via pkg I realized that since the last update several dependencies have changed: chromium depends on gcc5? ImageMagick now depends on nvidia-driver? This cannot be correct can it? I don't even have an Nvidia card...
New packages to be INSTALLED...
Follow up: I was unable to solve my problems with the old hardware. In the meanwhile I switched to an Intel NUC keeping my old hard disk which worked like a breeze. The APIC/ACPI/Interrupt problems are gone and the system is even a little faster now.
Re: How to deal with dependency problems when using only pkg
I'm still having this problem with graphics/giblib and graphics/imlib2. giblib is still missing from the official repositories. There seems to be no option to pkg install that allows to ignore dependencies. Although this seems a...
Re: How to deal with dependency problems when using only pkg
It seems to be a repository error. The same problem occurred on a fresh 10.0 when not all packages were yet available. I got around it by compiling the concerned ports by hand.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.