Displaying 7 results from an estimated 7 matches for "commonly_reported_issu".
Did you mean:
commonly_reported_issue
2008 Nov 19
2
gmirror and gstripe
hail,
I have an old AthlonXP 1700+ running 7-STABLE:
FreeBSD xxx 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Nov 13 23:54:59
BRT 2008 root@xxx:/usr/obj/usr/src/sys/xxx i386
where I have two 750GB Seagate SATA Disks. They are divided as two slices,
around the first 120GB are gathered in gmirror, and what left is in
gstripe. so that's whats going on. if the machine locks, and fsck comes to
2008 May 18
2
possible zfs bug? lost all pools
after trying to mount my zfs pools in single user mode I got the following
message for each:
May 18 09:09:36 gw kernel: ZFS: WARNING: pool 'cache1' could not be loaded as
it was last accessed by another system (host: gw.bb1.matik.com.br hostid:
0xbefb4a0f). See: http://www.sun.com/msg/ZFS-8000-EY
any zpool cmd returned nothing else as not existing zfs, seems the zfs info on
disks
2013 Feb 07
0
ethtool-like utility for FreeBSD
...;EEPROM", which documents a different
bug pertaining the Intel 82573 where some EEPROMs were shipped with a
power-saving bit enabled. Read it, do not skim it, because it explains
the EEPROM dump endian difference WRT Linux ethtool vs. FreeBSD's driver:
https://wiki.freebsd.org/BugBusting/Commonly_reported_issues
There is no way on FreeBSD to change EEPROM contents. You will need to
use Linux ethtool for this, or -- strongly recommended -- ask Intel for
their DOS-based utility that fixes the "packet of death" setting in the
EEPROM and follow their instructions. You can also ask your NIC (or
m...
2008 Oct 08
4
Problem with dump stalling
Hi
If I have the wrong list please feel free to redirect me.
I'm running 7.0-RELEASE-p4 and trying to backup to an external USB
drive.
I'm using the following command
dump -a0Lf /backup/diskimages/root /dev/mfid0s1a
Where df:
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/mfid0s1a 507630 208436 258584 45% /
/dev/da1s1d 709513458
2008 Nov 12
5
System deadlock when using mksnap_ffs
I've been playing around with snapshots lately but I've got a problem on
one of my servers running 7-STABLE amd64:
FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64
I run the mksnap_ffs command to take the snapshot and some time later
the system completely freezes up:
paladin# cd /u2/.snap/
paladin#
2008 Jun 25
3
Problem with /boot/loader
Hello,
I have a problem with loader. I recently upgraded from 6_rel to 7_rel.
Now when I install world there is a problem booting.
Here is what I do:
cd /usr/src
make buildworld
make buildkernel KERNCONF=BLACK
make installkernel KERNCONF=BLACK
At this point I can reboot and all is good. After boot I install the new world:
cd /usr/src
mergemaster -p
reboot into single user mode
cd /usr/src
make
2008 Sep 21
3
UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190
Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY.
Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix
whatever to the questions posed as fsck runs. What does this all mean?
Thanks,
-Clint
--
This message has been scanned for viruses and
dangerous content by MailScanner,