Re: FreeBSD6.0 and VMWare 5.0.. No go
On Thu, 1 Sep 2005 09:15:08 -0400, you wrote: This morning I tried to install FreeBSD6.0 under VMWare 5. I got the following message when it was extracting the base into \ directory: Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) cpuid=0 KDB: enter: panic [thread pid 3 tid 100034 ] stopped at kdb_enter+0x2b: nop db Is this a known issue? I am now able to install in VMWARE 5 with 6.0-BETA4. Thanks, Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum or gvinum
Hi all, I am still struggling to set up a one way mirror on two 72GB disks on 5.4 intel platform, however, there seems to be a lot of confusion about what to use in the first place. this is vinum v gvinum. I have managed to get to the point where I can fsck all volumes, however when rebooting the box would not come back giving me this: vinum: loaded vinum: no drives found Mounting root from ufs:/dev/gvinum/root setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Tried to configure the same with gvinum replicating the vinum.conf, however, still nothing. You know, when you are creating the vinum volume in bsdlabel and offsetting it with 16 blocks giving it vinum format, do you change this for gvinum as well??? my config would not have it, I can save it? I also tried the geom_vinum_load=YES in the /boot/loader.conf, however, should I have vinum.autostart=YES there as well for the gvinum?? On another occasion I have edited /etc/rc.d/vinum changing the start_cmd to gvinum start - nothing happened??? Also in the vinum.conf file that I laboriously create each time I try, is the drive Master device /dev/da0s1h with the h which is the slice which I create in the bsdlabel or is it the device name /dev/da0s1a for the root volume?? Non of it worked for me. Help me out from here please. This is supposed to be a production server and I have spent two days on it already. Tomas -- tp PRIVACY CONFIDENTIALITY This e-mail is private and confidential. If you have, or suspect you have received this message in error please notify the sender as soon as possible and remove from your system. You may not copy, distribute or take any action in reliance on it. Thank you for your co-operation. Please note that whilst best efforts are made, neither the company nor the sender accepts any responsibility for viruses and it is your responsibility to scan the email and attachments (if any). This e-mail has been automatically scanned for viruses by MessageLabs. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum or gvinum
Hi, First: do _NOT_ use vinum on 5.4, use gvinum. On Thu, Sep 08, 2005 at 12:43:01PM +0100, Tomas Palfi wrote: I am still struggling to set up a one way mirror on two 72GB disks on 5.4 intel platform, however, there seems to be a lot of confusion about what to use in the first place. this is vinum v gvinum. gvinum. Just to be safe you could move the vinum command and kernel modules out of the way. Tried to configure the same with gvinum replicating the vinum.conf, however, still nothing. Did you start from scratch by wiping the former configuration without loading gvinum? Use # dd if=/dev/zero of=/dev/da0 bs=1m count=128 to be sure. Do this WITHOUT loading any of the vinum modules. You know, when you are creating the vinum volume in bsdlabel and offsetting it with 16 blocks giving it vinum format, do you change this for gvinum as well??? my config would not have it, I can save it? I don't understand this. Here is my gvinum.conf for my mirrored system at home: %%% drive pain device /dev/ad4s1e drive panic device /dev/ad6s1e volume root plex org concat sd length 192m drive pain plex org concat sd length 192m drive panic volume swap plex org concat sd length 2080m drive pain plex org concat sd length 2080m drive panic volume usr plex org concat sd length 6g drive pain plex org concat sd length 6g drive panic volume var plex org concat sd length 256m drive pain plex org concat sd length 256m drive panic volume local plex org concat sd length 0 drive pain plex org concat sd length 0 drive panic %%% Be aware that gvinum's configuration syntax only allows the short forms for many keywords. /dev/ad4s1 and /dev/ad6s1 have this label: %%% [EMAIL PROTECTED] ~ sudo bsdlabel ad4s1 # /dev/ad4s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 393216 2814.2BSD0 0 0 c: 1562490090unused0 0 # raw part, don't edit e: 156248993 16 vinum %%% I also tried the geom_vinum_load=YES in the /boot/loader.conf, however, should I have vinum.autostart=YES there as well for the gvinum?? No, vinum.autostart is for legacy vinum. On another occasion I have edited /etc/rc.d/vinum changing the start_cmd to gvinum start - nothing happened??? Don't do that, it's not necessary to edit anything in /etc/rc.d. Also in the vinum.conf file that I laboriously create each time I try, is the drive Master device /dev/da0s1h with the h which is the slice which I create in the bsdlabel or is it the device name /dev/da0s1a for the root volume?? Non of it worked for me. Use only vinum BSD partitions for gvinum drive declarations. Help me out from here please. This is supposed to be a production server and I have spent two days on it already. Keep at it until it makes sense, that's what I did. There are a lot of concepts to get until it clicks. HTH, --Stijn -- My server has more fans than Britney. -- Steve Warwick, from a posting at [EMAIL PROTECTED] pgpCEkUHfKnuT.pgp Description: PGP signature
Re: SiI 3114 woes
On 08/09/2005, at 13:37, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
The drive apparently aborts the write, however this cant be the first
operation to it, so something else might have happend before this.
On my (granted UP AMD64) it works like a charm, so does it on x86 so
the driver is not completely broken at least :)
Get me the output from dmesg so I can see whats under the hood, might
help explain things.
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum or gvinum
On Thu, Sep 08, 2005 at 01:59:27PM +0200, Stijn Hoop wrote: Did you start from scratch by wiping the former configuration without loading gvinum? Use # dd if=/dev/zero of=/dev/da0 bs=1m count=128 to be sure. Do this WITHOUT loading any of the vinum modules. :( Forgot to add a big fat warning: == this hoses your system if you do this on your system disk of course ==! --Stijn -- Nostalgia ain't what it used to be. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum or gvinum
On Thu, Sep 08, 2005 at 01:20:47PM +0100, Tomas Palfi wrote: I thought I could check previous gvinum config with the gvinum list command in its own shell. When I run this command for either gvinum or vinum, they both reported no volumes. You should be able to use the list command to view the configuration. It's just that I'd start with a clean slate so to speak. Also I noticed that you have IDE hard drives, whereas I have SCSI, would that matter? Not that I know. To gvinum, they're just drives. By the way, you can also consider geom_mirror, for which an excellent article is available here: http://people.freebsd.org/~rse/mirror/ Both gvinum and gmirror approaches are able to boot from a mirrored system disk. It depends on other factors which one you choose. Thank you No problem. --Stijn -- Fairy tales do not tell children that dragons exist. Children already know dragons exist. Fairy tales tell children the dragons can be killed. -- G.K. Chesterton pgprpwYivdc8s.pgp Description: PGP signature
Re: file -i (mime type) has bug ?
and yet another (non-xenophobic) problem: file xml/si.xml xml/si.xml: XML document text file -i xml/si.xml xml/si.xml: it is not a copy/paste error, last line above matches pattern /: *$/ -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file -i (mime type) has bug ?
In the last episode (Sep 08), Andriy Gapon said: Additional information: file mod_ibm_admin.so mod_ibm_admin.so: executable (RISC System/6000 V3.1) or obj module not stripped file -i mod_ibm_admin.so mod_ibm_admin.so: video/unknown I wonder what might be causing this xenophobia. -i uses the magic.mime file instead of the standard magic file, and there are no entries for RISC executables in there. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file -i (mime type) has bug ?
on 08.09.2005 19:29 Dan Nelson said the following: -i uses the magic.mime file instead of the standard magic file, and there are no entries for RISC executables in there. Oh I see, completely different database. BTW who is in charge of this file - freebsd or some 3rd party (GNU?) from which we take file as contrib ? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file -i (mime type) has bug ?
In the last episode (Sep 08), Andriy Gapon said: on 08.09.2005 19:29 Dan Nelson said the following: -i uses the magic.mime file instead of the standard magic file, and there are no entries for RISC executables in there. Oh I see, completely different database. BTW who is in charge of this file - freebsd or some 3rd party (GNU?) from which we take file as contrib ? /usr/src/contrib/file/FREEBSD-upgrade says the original source is at ftp://ftp.astron.com/pub/file/ . We are at 4.10; the latest version is 4.15. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file -i (mime type) has bug ?
Dan Nelson wrote: In the last episode (Sep 08), Andriy Gapon said: on 08.09.2005 19:29 Dan Nelson said the following: -i uses the magic.mime file instead of the standard magic file, and there are no entries for RISC executables in there. Oh I see, completely different database. BTW who is in charge of this file - freebsd or some 3rd party (GNU?) from which we take file as contrib ? /usr/src/contrib/file/FREEBSD-upgrade says the original source is at ftp://ftp.astron.com/pub/file/ . We are at 4.10; the latest version is 4.15. Is there someone responsible for tracking this and importing newer versions? John -- John T. FarmerOwner CTOGoldSword Systems [EMAIL PROTECTED] 865-691-6498 Knoxville TN Consulting, Design, Development of Networks Software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file -i (mime type) has bug ?
In the last episode (Sep 08), J. T. Farmer said: Dan Nelson wrote: In the last episode (Sep 08), Andriy Gapon said: on 08.09.2005 19:29 Dan Nelson said the following: -i uses the magic.mime file instead of the standard magic file, and there are no entries for RISC executables in there. Oh I see, completely different database. BTW who is in charge of this file - freebsd or some 3rd party (GNU?) from which we take file as contrib ? /usr/src/contrib/file/FREEBSD-upgrade says the original source is at ftp://ftp.astron.com/pub/file/ . We are at 4.10; the latest version is 4.15. Is there someone responsible for tracking this and importing newer versions? According to CVS, David O'Brien has done all the previous imports. No-one is strictly responsible for tracking 3rd-party updates though. Imports are usually done on an as-needed basis. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI 3114 woes
Yes, but only in a configuration =3GB. But I thought those problems were
ironed out? I've been looking to switch that machine back to
FreeBSD/amd64 but haven't had a chance yet. Would love to know if there
are issues ahead.
-Jon
On Thu, 8 Sep 2005, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
at the debugging console
and
panic:bundirty: buffer 0x9a7faff0 still on queue 1
cpuid = 0
KDB: enter: panic
[ thread pid 3 tid 100021 ]
Stopped at kdb_enter+0x2f: nop
db trace
Tracing pid 3 tid 100021 td 0xff007ba14be0
kdb_enter() at kdb_enter+0x2f
panic() at panic+0x249
bundirty() at bundirty+0x128
brelse() at brelse+0x831
bufdone() at bufdone+0x225
ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7
bufdone() at bufdone+0x2ad
g_vfs_done() at g_gvfs_done+0x63
g_io_schedule_up() at g_io_schedule_up+0xd4
g_up_procbody() at g_up_procbody+0x7a
fork_exit() at fork_exit+0xbb
fork_trampoline() at fork_tramploine+0xe
--- trap 0, rip = 0, rsp = 0xb2160d00, rbp = 0 ---
db
Some months ago, I did successfully install FreeBSD 5.4/amd64 on it,
using PATA IDE drives, and no problems whatsoever, so I think this has
something to do w/ the SiI 3114 driver.
Any help is much appreciated.
I do apologize for cross-posting but this concerns -stable and -amd64.
Thanks!
cheers
mars
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI 3114 woes
Jon Dama wrote:
Yes, but only in a configuration =3GB. But I thought those problems were
ironed out? I've been looking to switch that machine back to
FreeBSD/amd64 but haven't had a chance yet. Would love to know if there
are issues ahead.
-Jon
On Thu, 8 Sep 2005, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
at the debugging console
and
panic:bundirty: buffer 0x9a7faff0 still on queue 1
cpuid = 0
KDB: enter: panic
[ thread pid 3 tid 100021 ]
Stopped at kdb_enter+0x2f: nop
db trace
Tracing pid 3 tid 100021 td 0xff007ba14be0
kdb_enter() at kdb_enter+0x2f
panic() at panic+0x249
bundirty() at bundirty+0x128
brelse() at brelse+0x831
bufdone() at bufdone+0x225
ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7
bufdone() at bufdone+0x2ad
g_vfs_done() at g_gvfs_done+0x63
g_io_schedule_up() at g_io_schedule_up+0xd4
g_up_procbody() at g_up_procbody+0x7a
fork_exit() at fork_exit+0xbb
fork_trampoline() at fork_tramploine+0xe
--- trap 0, rip = 0, rsp = 0xb2160d00, rbp = 0 ---
db
Some months ago, I did successfully install FreeBSD 5.4/amd64 on it,
using PATA IDE drives, and no problems whatsoever, so I think this has
something to do w/ the SiI 3114 driver.
Any help is much appreciated.
I do apologize for cross-posting but this concerns -stable and -amd64.
It looks like the same issue that we have been complaining
about irt the ATA driver in 5.4/stable.. Several people have also found
it to be a problem under 6.0. In my case, it happens with a plain old
PATA drive (via 8235 controller). It runs fine under PIO4 mode, any
DMA modes result in the same errors you got.
I was working on updating and installing the ataMkIII patches since
that's the only version that is being supported :^ But they are
supposed to merge the beta code that is in 6.0 into 5.stable and
it sound like the same errors are occurring.
I'm seriously considering installing Gentoo and wash my hands of it.
John FreeBSD since '94, ver 2.0.x
--
John T. FarmerOwner CTOGoldSword Systems
[EMAIL PROTECTED] 865-691-6498 Knoxville TN
Consulting, Design, Development of Networks Software
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: file -i (mime type) has bug ?
on 08.09.2005 20:09 Dan Nelson said the following: /usr/src/contrib/file/FREEBSD-upgrade says the original source is at ftp://ftp.astron.com/pub/file/ . We are at 4.10; the latest version is 4.15. I've checked out 4.15 and SPARC executable mime type problem is fixed there, two other problems are not. I've sent an email to Christos Zoulas, the maintainer of the file, about them. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP! [Re: FreeBSD 6.0-BETA4 Available]
All, It looks like I accidentally put amd64 packages onto the i386 ISO images. I'm generating new ISOs and will upload then as soon as possible. This likely explians the problems with installing X11 from the ISO. Sorry for the confusion. Scott Scott Long wrote: Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.0-BETA4. ISO images are available for i386, amd64, pc98, alpha, powerpc, and ia64 architectures. sparc64 is still in the process of being built and will be uploaded as soon as it is ready. We encourage people to help with testing so any final bugs can be identified and worked out. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 (though that will change for the Release Candidates later). Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.0R/todo.html Since this is the first release of a new branch we only have a rough idea for some of the dates. The current rough schedule is available but most dates are still listed as TBD - To Be Determined: http://www.freebsd.org/releases/6.0R/schedule.html Known Issues Other than the items listed in the todo list there are no known issues with this BETA. Availability The BETA3 ISOs are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html Thanks, Scott ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum or gvinum
On 8.9.2005, at 21.26, Stijn Hoop wrote: By the way, you can also consider geom_mirror, for which an excellent article is available here: http://people.freebsd.org/~rse/mirror/ Both gvinum and gmirror approaches are able to boot from a mirrored system disk. It depends on other factors which one you choose. I have to vouch for gmirror system. I have three production machines here running and booting from gmirror on since 5.3-REL and they're all doing fine. Even after I upgraded 5.3 - 5.4 and during the first boot I saw the updating metadata -message. Made me sweat for a few seconds. -- br, Sty ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
