Re: system hangs on; Probing devices, please wait (this can take a while)...
On Wed, Jul 21, 2010 at 8:45 AM, Rich rl...@pacbell.net wrote: From: Dave d...@g8kbv.demon.co.uk To: Bruce Cran br...@cran.org.uk Cc: freebsd-questions@freebsd.org Sent: Wed, July 21, 2010 3:56:50 AM Subject: Re: system hangs on; Probing devices, please wait (this can take a while)... On 20 Jul 2010 at 23:46, Bruce Cran wrote: On Tue, 20 Jul 2010 14:59:04 -0700 (PDT) Rich rl...@pacbell.net wrote: Any ideas anyone ? I'm stuck. Cannot install FreeBSD on my computer. Every other OS besides FreeBSD boots up and installs. What else can I check? It looks like it's stopping/spinning at the section where it parses the slices/partitions. I don't know why it would be getting stuck there, though. Maybe because there might be old RAID metadata from being in one of those stupid fakeraids. I had this problem last year and somehow (can't remember) wiped the drives and got it working. The system worked for about a year then crashed. I thought it a good time to move to 9.0 but now having the same problem again. I didn't put them back in the fakeraid. From what I understand FreeBSD can't be installed on those fakeraids. Maybe it has something to do with that. -- Bruce Cran Hi, I'm not a developer (of OS's at least) but from that DEBUG: list, it almost looks like it thinks it can see just about every hardware device it knows about, existing or not, and is trying to use them all. I know someone mentioned memory tests, but I didn't see what results they came up with, or how much memory you have. I do know however from my own frustrating experience in the past, that often some software will run just fine on bad memory, if the problems don't screw up the code or it's workspace. Where as other software will crash badly, making you think the program is bad. The same is sadly true of hard disk errors too! Did you run a recent memtest86 (self boot CD) and let it do several Full passes (can take many many hours per pass if you have lots of ram! And or a not so fast CPU) ? Just idle musings. Dave B. No I didn't run a mem test since every other OS works perfectly fine. There's something in the FreeBSD code that is hanging. When it hangs it says Probing devices (this may take a while). What does a while mean? A few seconds? few hours? few days? That's a really dumb message IMHO. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org It's not a memory problem. I've never seen this before. I'll see if I can take a look at the code tonight (I'm at work right now) and figure out why you might be getting this. Clearly doing a minimal install (as some have suggested) isn't going to work because you don't even get to the menu. I know *what* the code is doing - and this is actually something we're getting rid of soon. This was written before devfs was implemented, so it is going through looking for every possible device. I'm just not sure what order it does it in off the top of my head, so I don't know what comes after the scan for SCSI disks, as it's clearly getting through that part just fine. Hmmm. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 11:09 PM, Bruce Cran br...@cran.org.uk wrote: On Mon, 19 Jul 2010 16:17:06 -0700 Chuck Swiger cswi...@mac.com wrote: There's not quite enough information here to identify your motherboard, but you should make sure there aren't any BIOS upgrades available for it, as those might help resolve this level of issue. Check your BIOS config for the disks carefully, and try adjusting the options you have. In particular, try choosing LBA mode rather than auto or CHS, and try to toggle through ACPI (or SATA mode) vs. IDE (or PATA compatibility) vs. enhanced (often meaning some form of BIOS RAID is enabled) and see whether any of them work. If that doesn't do the trick, you could wander through your BIOS menus, and disable all of the non-essential stuff like parallel serial ports, second NIC, or anything else which is not needed, and see whether that does any good...but that's getting into stuff which is less likely to make a difference. The code that's being run does the following: 1. Finds all network interfaces. 2. Finds all CDROM, floppy, disk and network devices that might be needed for installation. 3. Finds all partitions on the disks to register. I'd guess it's hanging on a syscall somewhere, but there really isn't much debugging output in usr.sbin/sysinstall/devices.c to know where, unless the kernel has printed some errors to the debug console. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org This is why I suspected #3 - maybe querying the disk and hanging because of bad disk? Hard to say without debug logs. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: system hangs on; Probing devices, please wait (this can take a while)...
On Mon, Jul 19, 2010 at 1:16 PM, Rich rl...@pacbell.net wrote: I'm trying to boot on the 9.0 Current or 8.0 Release CD to install and it just hangs on; Probing devices, please wait (this can take a while)... I've waited almost an hour. how long is it supposed to take? It would be nice if there were a status bar or spinning wheel or something to let you know if it's doing anything or hung. What can I do to get this to install. AMD Phenom 9500 Quad-Core 2.20 GHz 2G RAM Drive: Seagate ST31000333AS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org This is probably just grasping at straws, but any chance your hard drive is failing? -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysinstall fails when adding distributions
This has been fixed. Get a newer RC. -- randi On Fri, Jul 2, 2010 at 6:49 AM, Kristaps Kūlis kristaps.ku...@gmail.com wrote: Hi, On FreeBSD 8.1-RELEASE (i386) on IBM T43, sysinstall fails when trying to add src distribution to already installed system (when starting to download them from FTP). No network activity is observed. coredump: http://www.ltn.lv/~kristapskulis/sysinstall.core dmesg: http://www.ltn.lv/~kristapskulis/dmesg What I`m doing wrong and how to fix it ? Kristaps Kūlis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: File system
On Sun, May 9, 2010 at 2:51 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote: 2) You could try using a 'journaling' filesystem, *BUT* you'd have to build/ implement it yourself. Journaling filesystems are deliberately _not_ provided with FreeBSD, due to security issues/implications with them. _You_ will have to decide if the security risks in *your* envrionment are worth the (limited) benefits. Really? Where do you get your information? Seriously, loling so hard right now. There's been a lot of work within FreeBSD to add journaling to UFS2. I guess we just don't care about security anymore. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Addition to BSDstats
Marc G. Fournier wrote: On Wed, 5 May 2010, Chris Whitehouse wrote: I seem to have probs with mine too. I was under the impression that bsdstats was installed by default (in the base system?) There has been talk about adding it as an option to sysinstall, but, unfortunately, I don't have enough knowledge of sysinstall to add it, and nobody else has step'd forward that does ... the idea wasn't to auto-install/enable, but to make it more visible while you are installing ... Anyone out there able to do this ... ? I have not heard any talk about this up until this email. I wouldn't want to add an option to sysinstall for this unless bsdstats was part of base. If it were, this would be trivial, but I don't really want to pop up any optional package menus other than what already exists. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Addition to BSDstats
mikel king wrote: On May 5, 2010, at 10:55 PM, Randi Harper wrote: Marc G. Fournier wrote: On Wed, 5 May 2010, Chris Whitehouse wrote: I seem to have probs with mine too. I was under the impression that bsdstats was installed by default (in the base system?) There has been talk about adding it as an option to sysinstall, but, unfortunately, I don't have enough knowledge of sysinstall to add it, and nobody else has step'd forward that does ... the idea wasn't to auto-install/enable, but to make it more visible while you are installing ... Anyone out there able to do this ... ? I have not heard any talk about this up until this email. I wouldn't want to add an option to sysinstall for this unless bsdstats was part of base. If it were, this would be trivial, but I don't really want to pop up any optional package menus other than what already exists. -- randi This idea was mentioned a few years as a way to improve advocacy statistics. Something short and sweet, with a one or two line explanation encouraging people to install the BSDStats system. If it were a yes/no option similar to the Would you like to install Linux Compatibility then it would be a no brainer. Honestly this seems relatively unobtrusive and quite logical. You're right, it is just for advocacy statistics. bsdstats is not an integral part of system operation. We prompt for Linux Compatibility because it could be needed for technical reasons. While advocacy is certainly important, the installer needs to be simplified, not complicated even more with unnecessary options and menus. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysinstall and mfs Great News and another Question
Please create a PR for any problems you find here or additions to install.cfg that you would like to see, and I'll take a look at it. -- randi On Mon, Feb 8, 2010 at 7:41 PM, Martin McCormick mar...@dc.cis.okstate.edu wrote: I really hate to give up on anything and I finally found out my problem with getting sysinstall to use the hard drive rather than garbaging up mfs every time. The problem is not something you can set in the partition editor or disklabel editor. It is found in the very first menu which oddly is numbered 2 and is the options editor. The option that makes it all work is one that lets you specify where you want the distribution to go on the drive. It is always set for you when using the CDROM unless you were formatting another disk so it is kind of easy to miss. I missed it for a week and a half. Now the question. There are a bunch of functions that can be set in sysinstall such as the bsdlabel editor, partition editor and dists to name a few. It would be nice to be able to set that mount point in install.cfg because I am trying to make a script that coworkers can run to configure a system quickly without having to waste a week of their own trying to figure it all out. It turns out that one can format the disk, mount /dev/ad0s1a on /mnt and then one must set the root option to /mnt and things work so much better! Occasionally, /var fills up and I haven't figured out why but it appears that ftp gets ahead of the ability to store the files. Whatever it happening, it is now more right than wrong. Again, thanks for all your help. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Thu, Dec 10, 2009 at 2:20 AM, Ian Smith smi...@nimnet.asn.au wrote: On Sat, 5 Dec 2009, Randi Harper wrote: On Sat, Dec 5, 2009 at 4:01 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 286, Issue 12, Message 7 On Fri, 27 Nov 2009 06:51:50 -0800 Randi Harper ra...@freebsd.org wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: [..] I made the memstick.img by dd as per the release page on my Thinkpad T23. It only sports USB 1.0 ports, and while I was confident of the dd (which took ~25m at ~600kB/s), I didn't really expect a 2002 laptop to boot from the image, but on seeing the USB stick show up in its BIOS and promoting it in the disk boot order, it did! Never underestimate IBM .. [..] So .. booted into sysinstall, fdisk and label ad0s4, leave boot0 as was, committed that much after two earlier attempts failed due to the below, quit to reboot, checked the labelling, redid the mount points, all ok. Picked pretty much all distributions from custom install, then of course had to select media. Picked USB - and got about what Derek did, no USB disk found. Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! After knowing that, the install went pretty smoothly, modulo not getting fc-10 to install by FTP, but that's another issue.. And just now, prompted by this thread I tried selecting Fixit, to again get what Derek did. And again, Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Maybe sysinstall could try a device rescan itself in that circumstance? This is a known issue. It would be possible to write in a hack to fix this problem that would be fairly quick to implement, but sysinstall already has one too many bandaids in place. I'd rather take a little bit of extra time and fix the underlying problem, especially since there is this workaround (forcing a device rescan) that seems to work for users in the meanwhile. At best it's an 'unknown known' :) Except for this present thread, my 'googling for ages' found nothing in FreeBSD lists about it. I was so close to giving up until I could go somewhere to burn a DVD, by then. I appreciate your disinclination to extend that message in sysinstall, it's been about to die for so long it's no longer funny, still it would have saved me half a day, and I'm sure I won't be the last person to run into this. I guess I should file a PR with a patch .. If you want to supply a patch that changes the error message in not finding a valid USB device, go for it. I'll push it through. One of the ideas I've been kicking around is consolidating some of the menu options and having sysinstall look for valid media on all removable devices (USB/CDROM/floppy), with the option to manually set it still available in the Options menu. I'm curious to see what other people think of this first, though. It does dumb down the install, but it still gives advanced users the option of specifying media. If you want to chuckle, take a look at sysinstall's devices.c and how it defines a valid USB device (hint: think DD). :) sysinstall was written back in the good 'ol days of pre-devfs and hasn't been updated much since. When it first runs, it does a device scan - that is, there's this really ugly data structure of all possible devices and a description/limit for each. So, just for example (and I'm not checking the code, so this value is probably wrong), say there's an entry for 'fxp' that is a type network with a limit of 16 devices - it's going to poke the system looking for fxp0, fxp1, ..., fxp15. It's doing this for every single network card, all possible disk devices, everything. Back in the day when computers were slower, this process could take a while, so it only happened once unless the user selected it again. But now, a rescan on my T23 was quite fast, and it's only a P3 1133MHz. I wish we could just disregard all the limitations of older hardware (this would make life so much easier!), but the fact remains that there are people that still install freebsd on ridiculously old computers. The smallest group tends to be the most vocal, or so I've found. Needless to say, this is extremely inefficient (sysinstall code has to be changed any time a new driver is added, too!) and there's a lot of better ways to do this. It's very easy to pull a list of network cards, disks, etc, but the work in moving away from that ugly data structure is no small job. Right now, much of my time is being taken up in trying to get gpt support into sysinstall, but getting rid of that data structure is high in my
Re: can't get a full fbsd 7.2 amd64 install
I could be mistaken, but that sounds like an awfully big /var and /usr. Are you sure this is a vanilla install that no one has touched? -- randi On Sat, Dec 12, 2009 at 8:11 PM, Len Conrad lcon...@go2france.com wrote: At 11:50 AM 12/10/2009, you wrote: fbsd 7.2 amd64 kernel developer install Here's a successful install du du -d1 -h / 2.0K /.snap 2.0K /dev 1.8G /usr 1.6G /var 1.7M /etc 2.0K /cdrom 2.0K /dist 1.1M /bin 206M /boot 6.7M /lib 396K /libexec 2.0K /media 2.0K /mnt 2.0K /proc 4.0M /rescue 42K /root 4.3M /sbin 24K /tmp 3.6G / here's what we're getting on another machine, way too little: du -h -d1 / 2.0K /.snap 2.0K /dev 1.1G /usr 238K /var 1.7M /etc 2.0K /cdrom 2.0K /dist 1.1M /bin 411M /boot 6.7M /lib 396K /libexec 2.0K /media 2.0K /mnt 2.0K /proc 4.0M /rescue 10K /root 4.3M /sbin 12K /tmp 1.5G / and /usr is also missing 800 MB just after install. using 7.2 amd64 disc01, as forever. I ran sysinstall, post install config, and checked stuff, but still didn't get, eg, anything in /usr/bin/ comments? Could my client have chosen the wrong .iso? the amd64 .iso is verified as disc01 and we have the same partial install failure, with no install errors, on two machines, Dell 1850, with amd64 and i386. any ideas? Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Sat, Dec 5, 2009 at 4:01 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 286, Issue 12, Message 7 On Fri, 27 Nov 2009 06:51:50 -0800 Randi Harper ra...@freebsd.org wrote: On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: Hi, Just wondering if anyone else out there has successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up. It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. When I switch to the debug tty, I see da0, and all my device parameters. I've even created a second USB stick, and stuck it in and tried. No joy. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? Thanks! - Derek That's really weird. I can't say that I've seen this problem. It sounds like you're trying to load the livefs - can you bring up a normal fixit shell prompt and see what entries you have in /dev for da0*? There should be a da0a. Due to sysinstall weirdness, adding this USB support was somewhat of a hack, as it doesn't look for da0 - it looks for da0a. :P Hi Randi, I had the same problem, rather more substantially, installing 8.0 from the memstick.img. This thread and to you seems to be where I should report what I remember of the process, only later finding all this. I made the memstick.img by dd as per the release page on my Thinkpad T23. It only sports USB 1.0 ports, and while I was confident of the dd (which took ~25m at ~600kB/s), I didn't really expect a 2002 laptop to boot from the image, but on seeing the USB stick show up in its BIOS and promoting it in the disk boot order, it did! Never underestimate IBM .. I was being very careful, as I wanted to install 8.0 on ad0s4, hopefully not damaging my 7.0-R on ad0s2, still having memories of a 3.3-R install in similar circumstances that went horribly wrong, 8? years ago :) So .. booted into sysinstall, fdisk and label ad0s4, leave boot0 as was, committed that much after two earlier attempts failed due to the below, quit to reboot, checked the labelling, redid the mount points, all ok. Picked pretty much all distributions from custom install, then of course had to select media. Picked USB - and got about what Derek did, no USB disk found. Very long story short: googled for ages and found a forum thread about this very problem, in which someone suggested Options / Rescan Devices then trying again. The OP there said it didn't work for him, but it sure did for me! After knowing that, the install went pretty smoothly, modulo not getting fc-10 to install by FTP, but that's another issue.. And just now, prompted by this thread I tried selecting Fixit, to again get what Derek did. And again, Options / Rescan Devices fixed it for me. Maybe it will for Derek and/or maybe provide another clue? Maybe sysinstall could try a device rescan itself in that circumstance? This is a known issue. It would be possible to write in a hack to fix this problem that would be fairly quick to implement, but sysinstall already has one too many bandaids in place. I'd rather take a little bit of extra time and fix the underlying problem, especially since there is this workaround (forcing a device rescan) that seems to work for users in the meanwhile. sysinstall was written back in the good 'ol days of pre-devfs and hasn't been updated much since. When it first runs, it does a device scan - that is, there's this really ugly data structure of all possible devices and a description/limit for each. So, just for example (and I'm not checking the code, so this value is probably wrong), say there's an entry for 'fxp' that is a type network with a limit of 16 devices - it's going to poke the system looking for fxp0, fxp1, ..., fxp15. It's doing this for every single network card, all possible disk devices, everything. Back in the day when computers were slower, this process could take a while, so it only happened once unless the user selected it again. Needless to say, this is extremely inefficient (sysinstall code has to be changed any time a new driver is added, too!) and there's a lot of better ways to do this. It's very easy to pull a list of network cards, disks, etc, but the work in moving away from that ugly data structure is no small job. Right now, much of my time is being taken up in trying to get gpt support into sysinstall, but getting rid of that data structure is high in my priority list, especially since there's a workaround. Old/cheap USB flash sticks seem to be the main offender, as they are slow to be recognized/probed, and sysinstall has already finished it's device scan by then. While I'm at it .. selecting 'Holographic Shell', while in that state at least, brings up a shell that (perhaps due to stick not being mounted?) has no ls command, making navigation
Re: 8.0-RELEASE and dangerously dedicated disks
On Wed, Dec 2, 2009 at 7:23 AM, Jerry McAllister jerr...@msu.edu wrote: Some of the responses have said that UFS handling of 'Dangerously dedicated' has not gone away, just sysinstall handling of it. That may be true and if that is true, then you can probably still access dangerously dedicated drives. But, I would think it is a good opportunity to convert them while the uncertainty reigns. Once again, it has nothing at all to do with UFS. Clearly you didn't search the mailing list archives like I said you should. I removed the support from sysinstall because it was *broken* due to changes with geom. It is not a sysinstall thing, it's a oh look, sysinstall lets you do something that doesn't work anymore thing. You'd think if the person that made these changes to sysinstall was commenting on the issue, that should clear up any uncertainty. But you can go ahead believing whatever makes you happy. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE and dangerously dedicated disks
I'm going to just reply to all of these at once. On Tue, Dec 1, 2009 at 1:03 PM, Jerry McAllister jerr...@msu.edu wrote: On Tue, Dec 01, 2009 at 07:59:42AM -0500, Maxim Khitrov wrote: On Sat, Nov 28, 2009 at 12:28 PM, Peggy Wilkins enli...@gmail.com wrote: Due to history I won't go into, all my production (currently 7.2-RELEASE) systems are installed onto dangerously dedicated disks. What exactly do I need to do to upgrade them to 8.0? (I'm not asking for an upgrade procedure, I'm familiar with that, but rather, how this change impacts the upgrade.) I think that the suggestion that the disks need to be reformatted is extreme and I hope something less extreme will suffice. Just to point out the obvious, you shouldn't use dangerous and production in the same sentence. :) Also, just to be clear, does this statement refer to boot disks, data disks, or both? It doesn't make sense to me that dangerously dedicated could have an impact on UFS filesystems specifically. A partition table is just a partition table, regardless of what filesystems might be written on disks, yes? Am I misunderstanding something here? I don't know why it would have an affect, but they say it does. Did you see all the mailing list chatter about new installations failing due to sysinstall not being able to newfs device names that didn't exist? This is related. Also, a partition table isn't just a partition table. It's a little more complex than that. It has *nothing* to do with the filesystems inside. It has everything to do with the way that FreeBSD looks at the drive to figure out what's on it. See man pages for geom/gpart. There are others that have given a better explanation than I can provide (marcus, juli). Search the archives. Trust me, I didn't remove DD support from sysinstall just to make life more complicated for everyone. I did this because as it stands right now, it doesn't work. I take this to mean that any disk that is created without slice and partition within slice needs to be redone. Probably it can all be done in sysinstall, but you can do it with fdisk/bsdlabel/newfs. Or sade, although sade hasn't yet been updated to reflect the lack of DD support. Just don't use that option. It does not matter if it is a boot disk or just a data disk. It is whether or not it has a (one or more, up to 4) slice defined and within the slice[s] partitions defined which are turned in to filesystems. You can tell by the dev names in /etc/fstab. If they have the full device name /dev/da0s1a, ... da0s1h, they are NOT dangerously dedicated and you should not have to worry. If the machine is dual booted with some MS thing as the other OS, then it is very unlikely that they are dangerously dedicated. But, if they are like /dev/da0 or /dev/da0s1 (but with no 'a, b..h') then they are dangerously dedicated and you need to convert them. What? No. 's1' refers to slice 1 (or partition 1, as you're referring to it). bsdlabel is used inside this slice to create a partition for each mount point (a,b,c, etc). See http://www.freebsd.org/doc/en/articles/formatting-media/x76.html. This documentation needs to be updated, but at least it'll give you a good explanation of how it used to work. With DD mode, you're creating a label against the drive itself, not a slice within. First you would have to back up the contents of the disk, partition by partition (mountable filesystem by mountable filesystem) however you have it. Since it is 'dangerously dedicated' it is likely you have a single filesystem per disk that needs backing up. Check out that backup to make sure it is readable. There is no going back. The backup can be done to tape or USB external disk or network or any other media that will not be affected, has room and can be written and read from the FreeBSD system. I think you're confusing running newfs against an unlabeled slice with DD mode. See above. DD mode means no slices, just a label for partitions. Not 'a single filesystem'. Snipping how-to on setting up a drive as it's unnecessary. She asked for a less extreme measure. The poster clearly has some idea as to what is going on and probably doesn't need her hand held in setting up a new drive. Thanks for helping to clear up my confusion... plw Peggy, Were you able to find an answer for this? I also have a number of servers and firewalls that use dangerously dedicated disks (boot and data). I don't see why UFS would care if it's mounted from ad1a vs. ad1s1a. It's not a filesystem thing. See above. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE and dangerously dedicated disks
Did you see all the mailing list chatter about new installations failing due to sysinstall not being able to newfs device names that didn't exist? This is related. Also, a partition table isn't just a partition table. It's a little more complex than that. It has *nothing* to do with the filesystems inside. It has everything to do with the way that FreeBSD looks at the drive to figure out what's on it. See man pages for geom/gpart. There are others that have given a better explanation than I can provide (marcus, juli). Search the archives. Trust me, I didn't remove DD support from sysinstall just to make life more complicated for everyone. I did this because as it stands right now, it doesn't work. Sigh, correction. marcel, not marcus. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE-i386-memstick fixit - No USB devices found!
On Fri, Nov 27, 2009 at 5:00 AM, Derek (freebsd lists) 48225...@razorfever.net wrote: Hi, Just wondering if anyone else out there has successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up. It boots fine, and sysinstall comes up, but I continually get No USB devices found! when I go to the fixit/USB option. When I switch to the debug tty, I see da0, and all my device parameters. I've even created a second USB stick, and stuck it in and tried. No joy. Anyways, has anyone successfully gotten the 8.0-RELEASE-i386-memstick fixit prompt up? Thanks! - Derek That's really weird. I can't say that I've seen this problem. It sounds like you're trying to load the livefs - can you bring up a normal fixit shell prompt and see what entries you have in /dev for da0*? There should be a da0a. Due to sysinstall weirdness, adding this USB support was somewhat of a hack, as it doesn't look for da0 - it looks for da0a. :P -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: no sshd on new server...
On Wed, Nov 18, 2009 at 3:12 PM, Gary Kline kl...@thought.org wrote: no joy on 8.0rcx. i got stuck in an infinite loop and decided to go back to my 7.2 DVD. there i know i can get out to the net ; i always installed zsh. there are TWO kinds of gateways. one gateway is my local 10.47.0.1; the other is my wide area 209.* that runs thru my pfsense firewall. i =am= getting more familiar with this rats nets of details. i t hink we are severely oversue for a better way of doing a barebone install on virgin hardware. =sigh= This makes so little sense that I'm actually kind of amazed. 1.) infinite loop? explain? 2.) what does zsh have to do with getting out to the internet? 3.) wtf is a barebone install on virgin hardware? What have you been doing to your hardware that you have specific definitions of virgin and not virgin hardware? sysinstall has had some changes since 7.x, but no changes that would have affected network service configuration (yet). You ran through the install and didn't bother reading all of the dialogs before hitting enter, so you don't have ssh installed. Good job. Don't blame FreeBSD for your ineptitude. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: no sshd on new server...
Correction - s/installed/enabled/. sigh. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Installer: missing GEOM/gpart capabilities slicing disk?
On Mon, Nov 9, 2009 at 7:40 AM, Daniel O'Connor docon...@gsoft.com.auwrote: [ -current CC dropped ] On Mon, 9 Nov 2009, O. Hartmann wrote: I try to install a fresh new FreeBSD 8.0-RC2 (from snapshot-DVD) on a barndnew harddrive. As far as I recall partitioning a disk is now done via gpart and the limitation of having only 8 (-2) partitions from a through h except b and c is now obsoleted. When dropping into the installation process, I realised that the 8 partition boundary is still present. Is there a howto (I searched the wiki and lists without success)? I read a lot about how to install FreeBSD on op of a complete ZFS infrastructure, but key issue seems to be a hands-on partitioning of the target haddrive via the fixit procedure. sysinstall does not [yet] do GPT partitions, I believe someone is working on patches but I have no idea what state they are in. Progressing nicely, but still quite a ways off from being ready. ;) -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Help understanding basic FreeBSD concepts (ports, updates, jails)
On Fri, Nov 6, 2009 at 9:31 AM, Roger rno...@gmail.com wrote: My second concerned is the ports. In the file ports-supfile there is one option, *default release=cvs tag=.. I believe this specifies which cvs tag to use when pulling files from the ports. At one point I had *default release=cvs tag=RELEASE_7_2_0. When I pulled the ports using the RELEASE_7_2_0 tag and tried to build portsupgrade the installation failed because the ruby version that was going to be installed I believe had a security problem. (I love the fact that I was stopped from installing software that is KNOWN to be vulnerable). I figured that maybe I needed to get the latest version. So I went ahead and changed the cvs tag to . (which I believe means the head version). Don't bother with any of that. Just use portsnap. It's also part of base, and was written by the same person that wrote freebsd-update. It's lovely and much faster, although some people may argue with me on that. I updated the ports and then tried the installation again, this time the installation went further but failed again due to the fact that my libtool (I can't remember the exact name) was older than what the installation required. So that threw me off. I believe that libtool is part of the base system and not the ports, correct? So that made me think that maybe because of using the latest version of the ports I can build certain ports if my base is not concurrent (in terms of what the ports requires and what my system offers) with the port system. So my question is this, if my FreeBSD release is 7.2-RELEASE-p4 which tag should I set for the ports system? Should I put the tag RELEASE_7_2_0 and then wait for a security fix of the particular port (ruby) and then proceed to install? What is the recommended approach if your aim is to have your system up to date and stable? For your system, use freebsd-update. For your ports tree, use portsnap. For installed ports, use portupgrade or portmanager. I'm more fond of portmanager, but it seems portupgrade has many more users. Both portupgrade and portmanager are available in the ports tree, not base. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Failure to do netinstall
On Fri, Oct 30, 2009 at 8:34 AM, John Nielsen li...@jnielsen.net wrote: On Friday 30 October 2009 03:12:29 Vadim Maksimenko wrote: I have faced an unpleasant fact that your netinstall ability of 7.2 RELEASE and 8.0-RC2 are dead. My network card is being identified and initialized properly (an old 3com980), it gets DHCP setup (IP, gateway, DNS info is ok), but... That's all that is done properly. When I try to select any flavor of network install, it crashes with a message like Cannot connect bla bla bla: the connect is in wrong state. I just did a network installation of 8.0-RC2 yesterday (albeit from an 8.0-RC1 bootonly CD) so I'm fairly certain it's not totally broken. Since you apparently got a valid DHCP lease on your NIC it's probably not the card or the driver that's broken either What should I do now if I want to install FreeBSD via network and have no option of changing the hardware? We need to figure out what _is_ wrong. Can you provide more details of the exact steps you took during the setup? Do you have the exact error message? Guessing wildly, it's entirely possible that sysinstall got confused at some point. Did you have to repeat the network configuration or FTP server selection? Did you try repeating the installation after a reboot? JN You might also try enabling debugging messages and seeing what's on the next tty over when it fails. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd 6.4 can't load kernel after upgrade
On Fri, Oct 30, 2009 at 8:20 PM, oscar Seo oscar...@gmail.com wrote: I'm a beginner in freebsd. my machine consists of freebsd-6.4 + i386 bootstrap loader,+ windowmaker after upgrade freebsd-6.4 using sysinstall then reboot the system, I got an error message as follows +++ Loading /boot/defaults/loader.conf Unable to load a kernel! / can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. OK _ +++ so I decided to reinstall freebsd-6.4 but I can't boot and re-install freebsd using CD-rom. what shall I do boot my system using installed freebsd or live-CD ? Thanks... For future reference, while upgrading via sysinstall is possible, it's best to use something like freebsd-update, which is included in base. I can't recall off the top of my head if upgrading via sysinstall moves the kernel to kernel.old or not. Good luck with that. You may be best off using livefs and trying to repair with that. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why is sendmail is part of the system and not a package?
MAKE THE PAIN STOP. Seriously, read back in the friggin' mailing list archives. None of y'all are going to say anything that hasn't been said before. Or don't, and just prove how valuable your time isn't by wasting it arguing about something that everyone else is just rolling their eyes at and ignoring, as they've seen it all before. This bikeshed is old and tired. I don't want to paint it. I want to drown it in lighter fluid and set it on fire. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysinstall colours
On Fri, Oct 16, 2009 at 6:00 PM, Michiel Overtoom mot...@xs4all.nl wrote: On Friday 16 October 2009, Randi Harper wrote: Personally if I spent a lot of time on such a project, I'd be sure to have the is this going to make it into freebsd base? conversation first. I think there's no doubt about it that 'sysinstall' will feature in the next FreeBSD too. It will! Keep up the good work! It's worth it. Thank you for the kind words. :) The sysinstall manual page makes two apocalyptical remarks about itself: 1. This product is currently at the end of its life cycle and will eventually be replaced. 2. This utility is a prototype which lasted several years past its expiration date and is greatly in need of death. These doomsayings are wrong. To date no serious contenders have surfaced and up until that time sysinstall does its job, underappreciated perhaps, but it does it reasonably well, and adequately. Now that it is back in the focus, we can look to a bright, evolutionary future for sysinstall. As much as I want to agree with you, I can't quite do so. There are (to the best of my understanding) solid reasons why no other installer has made it into base. This doesn't necessarily mean that sysinstall is the final answer, though. Eventually, in my opinion, sysinstall needs to be replaced. It tries to do more than it should. For example, one of the things I'd like to see removed is the upgrade option - although I'm expecting quite a bit of backlash on that, so we'll see if that happens. I also don't think it should manage configuring rc.conf beyond network interfaces/hostname. The network services configuration is a mess. I don't think enabling the NFS server via sysinstall even works at this point. That aside, the code for sysinstall isn't really that bad, although it's been more of a history lesson than I initially expected. It was clearly written with the restrictions of older technology in mind. Bringing it completely up to date with current technology (devfs, gpt, zfs, whatever) is going to be such an extensive rewrite that it's true, one might as well write a new installer altogether. Then again, maybe I just like playing devil's advocate. :) -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysinstall colours
On Tue, Oct 13, 2009 at 2:23 PM, Alexander Best alexbes...@math.uni-muenster.de wrote: just did a quick research and google soc sponsored the finstaller in 2007 and the bsdinstaller in 2005. personally if i spent a lot of time on such a project i'd be expecting it to get integrated into the base system. if not i'd get rather upset and would probably switch to linux or opensolaris. just my 2 cents. alex Personally if I spent a lot of time on such a project, I'd be sure to have the is this going to make it into freebsd base? conversation first. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: / almost out of space just after installation
On Thu, Oct 8, 2009 at 1:02 AM, per...@pluto.rain.com wrote: At least as far back as SunOs 3.5* the installer was able to auto- size the partitions based on the selected distribution sets. Of course, this means that the installer must know the size of each distribution set -- on each of /, /usr, and /var -- and that the selection of what to install has to happen before the partitioning is actually done. I would think that the sizing of the distribution sets could easily be automated as part of the release process, and that the needed reordering of the installation process would not be all that difficult for someone familiar with sysinstall and accustomed to coding in the language involved. 1.) Look at the PR database and search for sysinstall. See all those open reports, some from 8 years ago? sysinstall needs some babying. There are bugs that need to be addressed, and I'm making those a much higher priority than feature requests, although this isn't to say that you can't submit a feature request anyways. 2.) The problem isn't that the current default partition sizing doesn't work with a newly installed system. It does. The problem is what happens afterwords: compiling a new kernel or two, installing third party software (while it's true that most files from installed ports are installed to /usr/local, that doesn't mean that they are all configured to only write data to /usr/local at run time, obviously), etc. syslogd is installed by default, but there's no way for me to know if you plan on logging to a remote host, or even using this host as a syslog server for multiple hosts, or what your log retention is going to be, nor do I know if this is going to be a database or mail server, so I can't guess the size of /var. Knowing the size of the data to be installed is easily enough done, but it's not going to solve this problem at all. 3.) Although your comparison to SunOS isn't really all that relevant, your complaint about default partition size is. This is something that I'm considering changing, although I expect some backlash/bikeshed. I've not yet run into problems with / unless I had more than 2 kernels around, but I have seen a default-sized /tmp fill up due to some third party software. I was thinking that a more acceptable default layout (leaving swap at it's current default size) would be: / = 1GB /var = 2GB /tmp = 2GB One thing to remember is that these are just suggested defaults. Most experienced users are going to use a custom layout when setting up a new server, so the goal here is to have partition sizes that work for everyone else. Although FreeBSD does work on older hardware, I'd guess that most of the hardware it is being installed on now is less than 10 years old. The defaults we currently have in place are outdated. They are targeted more for older systems, perhaps because sysinstall hasn't been touched in quite a while. I'm looking for community input on this, so feel free to pipe up with your $.02. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: / almost out of space just after installation
On Fri, Oct 9, 2009 at 12:06 AM, Jon Radel j...@radel.com wrote: I believe it's been years since I didn't bump up the sizes on an install, otherwise I just end up with all this space where it's least likely to save me from a filled disk in the future. While I am actually running some hardware that is over 10 years old with FreeBSD, quite happily, every single hard drive involved has been replaced due to failure or as a preventative measure. Oh, I'm not saying people aren't running FreeBSD on older hardware, I'm just guessing that *new* installs mostly happen on hardware that is less than 10 years old. :) -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting ZFS and GPT
On Thu, Sep 17, 2009 at 4:51 AM, Anselm Strauss amsiba...@gmail.com wrote: Hi, I've read and tried out that FreeBSD is able to boot from ZFS directly, also with GPT partitions, through zfsboot and gptzfsboot. When I tried the last time 8-CURRENT it was however not built into the release CD. Will this be included in the final release image? Is there any plan to include GPT and ZFS setup in sysinstall during an initial installation? I am working on this, but it is a lot of work. Don't expect it anytime soon, as it involves ripping out libdisk and replacing it with libgeom. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting ZFS and GPT
To big a rewrite needed i think. Tell me about it. :P I've heard of plans to potentially release a graphical installer based on pc-bsd, which will do all the bells an whistles. Not sure what stage its at though. There's quite a few installer options that are around. bsdinstaller, then there's ivan's finstall. I've never used either of them. AFAIK, there aren't any graphical installers in the works that are 'based on pc-bsd'. I also seriously doubt these will make it to the official iso's. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting ZFS and GPT
On Wed, Sep 23, 2009 at 1:01 AM, ill...@gmail.com ill...@gmail.com wrote: I hope our developers see fit to make sysinstall zfs aware, but I hope we are not pushed (I know how to kick and my screams are deafening) into using it any time soon: ufs is wonderful for us ordinary computer users. Getting libgeom support is what is currently being worked on. ZFS is probably quite a ways down the road unless someone else steps up to help out. That said, sysinstall is the beast that no one else wants to touch, so don't expect this anytime soon. I'm hoping to have this done (or at least mostly done) by 9. FWIW, I'll kick and scream before sysinstall defaults to zfs. I'm currently planning on making zfs/gpt/etc only available from expert mode. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem installing FreeBSD 7.1 RELEASE.
On Thu, Sep 10, 2009 at 4:09 PM, Rom Albuquerque a_rom...@hotmail.comwrote: Hi. I'm having trouble installing 7.1 release. The details of my system : Motherboard : EliteGroup (A740GM-M) RAM : 3G DDR2 800Mhz CPU : AMD Athlon 64 x2 Dual Core processor Disk :WD 500GB SATA DVD : Samsung DVD/Writer Super Write Master Primary OS : Windows XP sp3 I'll list the problems and the attempts I've tried to get around them. Problem #1 The CD/DVD drive can not be mounted by sysinstall. === I have a SAMSUNG DVD writer drive attached to my ATAPI IDE interface. I have a WD 500GB SATA Drive attached to my SATA interface. The system boots off the CD, runs sysintall. I'm able to allocate storage for the FREEBSD partition and then create the individual slices for the default file systems. (/, swap, /var, /tmp, /usr) When choosing the instalation media as CD/DVD, an error message saying that the CD/DVD drive was not found pops up. I've tried every option on the boot program, they all fail to load the CD/DVD drive and can't proceed with the instalation. I've tried changing the DVD drive to a nother CD/RW drive attached to the same ATAPI controller, the problem persist as before, no change. This leads me to my next attempt to install the system from a disk PARTITION. Problem #2 Unable to mount the disk partiton at the time of install. = Ok, I've created a new extended partition with Partition Magic to hold the contents of the install CD. This new partition sits third on the list as follows : a) NTFS partition with my XP installation b) FreeBSD partiton where the system will be installed. c) The new FAT partiton where the contents of the FREEBSD cd is copied into the directory named E:\FREEBSD. I've copied the entire CD to this new partition. Back to sysinstall, when choosing the new instalation media Install from DOS partition I get an error message saying Unable to mount /dev/ad8s3 to /dist, and the problem of not finding the DOS partition where the contents of the FREEBSD cd were copied to continues, keeping me from progressing with the install. The next attempt was trying to install from a filesystem. When selecting this option, a dialog from sysinstall pops up asking to list the complete path name of where the FREEBSD files were copied to this disk partition. I enter /dev/ad8s3:/FREEBSD and an error message saying that it can not find the disk partition comes up keeping me from progressing with the install. I've looked at the FreeBSD handbook online, but could not find further details about installing the system from a disk partition. Any pointers as to what proper measures to take to try to get past this problem. ? Can someone suggest some other way to get the system installed. ? Oh, I've also tried PC-BSD, but that stops right away with an error message of Error loading image since it can not find the CD/DVD drive again. I'll appreciated if you can provide further details of how to proceed, point me to the direction where I can get more details. Your response is greatly appreciated. --Rom a_rom...@hotmail.com _ Windows Live: Keep your friends up to date with what you do online. http://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009___ freebsd-questions@freebsd.orghttp://windowslive.com/Campaign/SocialNetworking?ocid=PID23285::T:WLMTAGL:ON:WL:en-US:SI_SB_online:082009___%0afreebsd-questi...@freebsd.orgmailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org When the installation CD is booting, can you see if your CDROM drive is being detected as acd0? Another option might be to try installing from USB. Go into the options menu, enable debugging, and try the install again - either from the CDROM drive or the DOS partition. Switch to the next terminal over, and you should see some more verbose output as to what's going wrong. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Are all USB Flash Memory sticks bootable?
On Thu, Jul 23, 2009 at 6:27 AM, Sergio de Almeida Lenzi lenzi.ser...@gmail.com wrote: Em Qui, 2009-07-23 às 12:52 +0800, Fbsd1 escreveu: Hello I found here that some bios does have problem with booting from partitions they do not know So first I initialize the USB stick with == dd count=100 if=/dev/zero of=/dev/da0 fdisk -BI da0 sade == than edit the partitions... ls /dev/da* should show da0s1 da0s2 than disklabel -wB da0s1 disklabel -wB da0s2 newfs -L Freebsd7 da0s1a newfs -L Freebsd8 da0s2a boot0cfg -vB da0 mount the partitions, copy the files boot from the usb... it will show you the F1 F2 chooser for me, this worked Sergio Just to clarify, are you trying to boot from a USB stick that you've installed FreeBSD onto, or is this a USB stick that you've dd'ed the memstick.img to? You should NOT use disklabel on a usb stick that you're dd'ing the memstick.img to. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Install from a USB Pen (semi OT)
On Wed, Jul 22, 2009 at 8:29 AM, Mikel King mikel.k...@olivent.com wrote: Just curious, but is there an easy way to get all of this onto the pen in the first place? I missed the origin of the thread. dd if=image file of=usb drive bs=10240 conv=sync -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Install from a USB Pen
On Fri, Jul 17, 2009 at 8:41 PM, Fbsd1 fb...@a1poweruser.com wrote: Took 3 times longer to download the 8.0-BETA1-i386-memstick.img that to download the 8.0-BETA1-i386-disc1.iso. I suggest you look into another method of creating the memstick.img so it downloads faster. dd does no compression of the data. -rw-r--r--1 110 1002 346845184 Jul 16 02:04 8.0-BETA2-i386-disc1.iso -rw-r--r--1 110 1002 917391360 Jul 16 02:00 8.0-BETA2-i386-memstick.img Note the filesize. This may be the reason it took 3 times longer. Just a guess. Using a 8gb memstick as the target to install 8.0 on took 2 times longer than disc1 cd installing to same 8gb memstick. Might have something to do with the amount of data being written. Again, just a guess. Are you sure it wasn't 3 times longer? Selected the [STANDARD/KERNEL DEVELOPER] distribution, It completed successfully, but the new 8.0 8gb memstick was not recognized as bootable. I don't know why that's the case as I am unable to reproduce this problem, but if the memstick.img is 1GB, why are you using an 8GB memstick instead of the 2GB? Here is a script i have used in the past to convert the disc1.iso to bootable memstick. Maybe its better to add this script to the place where 8.0-BETA1-i386-disc1.iso is located in place of the memstick.img. That way the 3 times larger memstick.img is not needed any more. No. If you took a look at the contents of the memstick, you'd realize it's not just a copy of disc1. It also includes livefs. This is probably why the memstick.img is so much bigger. :D -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Install from a USB Pen
On 7/14/09, Fbsd1 fb...@a1poweruser.com wrote: What are the instructions for using this 8.0 memstick.img? What raw size memstick is needed? Is the 8.0 memstick.img the same content as the cd1 disk? Sigh. Reply-to-all fail. Resending. It's all in the email about the 8.0 BETA(s). Use dd, a memstick that is of equal to or greater size than the memstick.img, and no, it's different from disc1. It currently lacks packages, but it does include livefs. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Install from a USB Pen
On Wed, Jul 15, 2009 at 6:50 PM, Fbsd1 fb...@a1poweruser.com wrote: Randi Harper wrote: On 7/14/09, Fbsd1 fb...@a1poweruser.com wrote: What are the instructions for using this 8.0 memstick.img? What raw size memstick is needed? Is the 8.0 memstick.img the same content as the cd1 disk? Sigh. Reply-to-all fail. Resending. It's all in the email about the 8.0 BETA(s). Use dd, a memstick that is of equal to or greater size than the memstick.img, and no, it's different from disc1. It currently lacks packages, but it does include livefs. -- randi The email about 8.0 BETA(s) was not posted to the questions list that is why I did not see it. This is what I tried Plugging in the stick auto generated these messages # /root umass0: vendor 0x0930 USB Flash Memory, class 0/0, rev 2.00/2.00, addr 2 on uhub1 da0 at umass-sim0 bus 0 target 0 lun 0 da0: USB Flash Memory 6.50 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 1905MB (3903487 512 byte sectors: 255H 63S/T 242C) GEOM_LABEL: Label for provider da0s1 is msdosfs/ço¤żňÚktń I have to hit enter key to get prompt of=da0 or of=da0s1 resulted in same thing, no img on stick # /usr dd if=8.0-BETA1-i386-memstick.img of=da0 bs=10240 conv=sync 57412+0 records in 57412+0 records out 587898880 bytes transferred in 192.035793 secs (3061403 bytes/sec) Can not mount with (mount /dev/da0s1 /mnt) But (mount_msdosfs /dev/da0s1 /mnt) does work but stick still contains the original data. Has not been overwritten by the 8.0-BETA1-i386-memstick.img What is the problem here? You're writing to a file called da0 inside /usr instead of /dev/da0. -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: partition black magic but no data lost phew!
On Mon, Jul 13, 2009 at 3:56 PM, Chris Whitehouse cwhi...@onetel.comwrote: Hi, This is from memory (brain not ram) and I can't recreate the steps for reasons which will be obvious, so may not be entirely accurate. I have a sata hard disk which is divided into 2 slices. Slice 1 (ad4s1) is about half the disk and had the remains of a standard install with swap, / , /var, /tmp, /usr. Slice 2 (ad4s2) is the remainder and has a single partition for data, ad4s2d. It was all created with sysinstall and doesn't have anything special like dangerously dedicated. The operating system on this machine is on a second hard disk which is what I booted from. I moved all the data from ad4s1f onto ad4s2d so that I could delete partitions from slice 1 and make a single large partition. I then unmounted all ad4* partitions. I may even have rebooted. sysinstall - Configure - Label allowed me to delete ad4s1a but when I tried to delete the other ad4s1* partitions sysinstall told me I had to set kern.geom.debugflags=16 before I could make changes on a running system . I set kern.geom.debugflags but changes I made in sysinstall did not take effect, the partitions persisted, both as /dev/ad4s1* and as entries in sysinstall At some stage sysinstall core dumped and somewhere else ad4s2d got deleted. I managed to recreate it and didn't lose any data. Next I booted from a pen drive and successfully deleted the partitions from slice 1, being very careful not to delete the partition on slice 2, however when I exited from sysinstall ad4s2d was gone. Again I managed to recreate it and didn't lose any data. The bit that puzzles me is that ad4s2d disappeared twice and the second time I am sure I didn't do any explicit steps to delete it. Did I hit a bug in sysinstall or did I do something wrong? I didn't lose any data in the end but I could easily have done (I know - back up - I'm going to go and buy a nice big external hard disk very soon ;) FreeBSD muji 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Nov 24 20:22:16 EST 2008 r...@pcbsdx32-7:/usr/obj/pcbsd-build/cvs/7.0.2-src/sys/PCBSD i386 Everything is sorted now so I am really asking this out of curiousity. Thanks Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org When you booted from the pen drive, was sysinstall running as init? ie: is this the memstick.img from the ftp site or a homebrew disc1.iso-usb image, or did you have freebsd installed to the pen drive? If so, what version? -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Install from a USB Pen
On Mon, Jul 13, 2009 at 7:17 PM, Fbsd1 fb...@a1poweruser.com wrote: Mark Wallbank wrote: OK I know this has probably been done to death by know and I keep hitting the same problems with the methods I have tried to find on google and I know I could just sacrifice a laptop and do a build to create the image or do a net (pxe) install from another NIX serverbut it does seem to be a bit over the top. Does any body know of an easy way to create a bootable USB install media for 7.2 using either linux or vista (or using an option from the install dvd). I have tried some of the tricks from openBSD and linux to no avail. Any help appreciated... Cheers Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org If your asking how to put the cd1 install contents onto a usb stick and use the sysinstall program to perform the install on the target box then check the archive. It has a post with a script to convert the cd1 install disk to usb stick. But the show stopper is the sysinstall program does not have option for usb stick as install source. There was a bug report submitted 2 years ago pointing out this oversight, but as of 7.2 it has not been corrected. If you think the sysinstall program should have install source option for usb stick them file your own bug report. The more people who file bug reports the more attention this problem will get from the developers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ... or you could just download an official image instead of going to all of that trouble. Check the FTP site, there's a memstick.img if you're down for using with 8 instead of 7. There are currently three PRs about this, and I recently took ownership of them. Filing duplicate bug reports doesn't get attention, it's just annoying and it makes trying to improve sysinstall that much more difficult because I'll have to spend more time closing these duplicates and less time fixing problems. There has been an email that stated there is USB install support in sysinstall as of 8.0 BETA1, and USB livefs support as of 8.0 BETA2. The PRs for USB support in sysinstall will be updated and closed soon. Don't open new ones. You're welcome! :D -- randi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Gmail vs FreeBSD
On 4/16/06, Andrew Pantyukhin [EMAIL PROTECTED] wrote: So what's up with gmail and freebsd sites? I haven't seen a single message delivered to my inbox since April 13. Not from mailing lists, not from gnats scripts - nothing. For what it's worth, I'm on several mailing lists and have noticed no problems at all. Although I'm not using the gmail service, I'm one of the beta testers for domain mail hosting, so my MX is pointed at google's servers.. Randi Harper -- FreeBSD Tsarina http://freebsdgirl.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB2.0 External IDE connections
On Friday 22 April 2005 10:48 am, scott renna wrote: Has anyone had any luck in using external USB2.0 enclosures on FreeBSD 5.3? I've picked up 2 of them with different chipsets and have 2 USB2.0 to IDE converter cables. My kernel has support for ehci so that's not an issue, but every time i plug one of these devices it, it's detected as da0 and a umass device, and I'm told data transfer is limited to 1Mb/s. attempting to mount da0 doesn't work. You have to use the disklabel tool and newfs it, of course. :) It's the same as using any USB drive. You might get faster speeds if you plugged it into a usb 2.0 port on your computer - I'm not sure what the limits are. USB HD enclosures are meant to be convenient, not fast. Next time, choose firewire. ;) Randi Harper URL: http://freebsdgirl.com Email: [EMAIL PROTECTED] AIM: Randi BSD pgp4QcmTwKxxr.pgp Description: PGP signature
Re: System very slow to boot
On Thursday 21 April 2005 02:54 pm, matadeen dokania wrote: system is very slow to boot, pl. sugest, what to do A dmesg would be nice, or perhaps just a bit more of an explanation than that. Where is it slow? Randi Harper URL: http://freebsdgirl.com Email: [EMAIL PROTECTED] AIM: Randi BSD pgpjY38ZzAO45.pgp Description: PGP signature
Re: USB2.0 External IDE connections
On Friday 22 April 2005 10:55 am, Brian McCann wrote: I tried, but I ended up returning the enclosures. I had a problem where anytime I would output lots of data to the drive (say 2 PCs copying a 4gb file to it), the drive would dissapear and hang the system. Happened on both Windows and FreeBSD though. IIRC, it was the newer Prolific chipset. Don't top post! I had the same problem, btw. I have a USB HD enclosure, I forget what chipset. Any time I transfered large amounts of data, it would lock my entire system. Fun stuff. I switched to firewire. The performance is heaps better, and I haven't had any problems with it (yet). Randi Harper URL: http://freebsdgirl.com Email: [EMAIL PROTECTED] AIM: Randi BSD pgpr7EUzhqWKU.pgp Description: PGP signature
Re: USB2.0 External IDE connections
Kernel options MSDOSFS_LARGE is experimental and advised to only be r/o. I tend to use 180/200 GB FAT32 drives in these enclosures, and that doesn't work unless you have kernel compiled this way, so I'm stuck needing to use MSDOSFS's that are 128 GB. If you've had trouble, you might look at your kernel config...? So use UFS2. ;) Randi Harper URL: http://freebsdgirl.com Email: [EMAIL PROTECTED] AIM: Randi BSD pgpNYCdIydW62.pgp Description: PGP signature
Re: sysinstall don't want to install packages
On Wednesday 20 April 2005 09:32 am, Stevan Tiefert wrote: Hello list, I've patched my FreeBSD to 5.3-RELEASE-p9. Afterwards I tried to install with sysinstall via ftp some packages, but sysinstall was saying that the 5.3-RELEASE-p9 isn't at the ftp-server and I should set in the options any in the release-field... My question is: Is this message OK or how should I install release-packages after a cvsup-Update of my release? Why use sysinstall? Just use pkg_add -r to fetch remote packages, or build them from ports, which generally gives you a more recent version number. It isn't rare for the precompiled packages to be slightly behind. Randi Harper URL:http://freebsdgirl.com Email: [EMAIL PROTECTED] AIM:Randi BSD pgptwiD97zek6.pgp Description: PGP signature
Re: Sound not working
On Wednesday 20 April 2005 01:30 pm, Emil Khatib wrote: Didn't work! I saw that ,as you said, volume controls in kmix were turned down to 0. I changed them but it had no effect. I even tried playing saound in Gnome, but it didnt work either. :( Try using the console program, mixer? ex: `mixer vol 70` Randi Harper URL: http://freebsdgirl.com Email: [EMAIL PROTECTED] AIM: Randi BSD pgpfWN4Hm2q7I.pgp Description: PGP signature
Re: Which app to watch movies?
Here is the error: = Attempting to fetch from ftp://ftp.mplayerhq.hu/MPlayer/Skin/. fetch: ftp://ftp.mplayerhq.hu/MPlayer/Skin/Blue-1.4.tar.bz2: size mismatch: expected 221761, actual 221733 = Attempting to fetch from ftp://ftp.lug.udel.edu/MPlayer/Skin/. fetch: ftp://ftp.lug.udel.edu/MPlayer/Skin/Blue-1.4.tar.bz2: size mismatch: expected 221761, actual 221733 = Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mplayer/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mplayer/Blue-1.4.tar.bz2: size mismatch: expected 221761, actual 221736 = Couldn't fetch it - please try to retrieve this = port manually into /usr/ports/distfiles/mplayer and try again. *** Error code 1 Cvsup'ed your ports tree recently? :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: One of your employees are very rude.
I'm sorry but.. hahahahahahahahahahahaha. It's IRC. You expected something different? Love, Randi Harper [EMAIL PROTECTED] http://freebsdgirl.com On Jan 30, 2004, at 11:06 PM, lorink wrote: To whom it may concern, I just want to let the bsd team know this has been a great OS and it is meeting my needs over that of other operating systems including windows which I was a software tester of W2k back in the late 90s. While your documentation is excellent and sometimes such subjects on google searches also provide answers I recently have stumbled across a irc chanell on efnet called #freebsdhelp. Been a good chanell so far but lately there is one op nick name hideaway who has been a little on the rude side and has kicked some people or my self and not permited them to return to the chanell because of his fits. I have a log of the events that led up to my being banned from the chanell and let me know if this is a employee that represent freebsd.org Sincerly, James K --clip-- Leak- you don't like sad? hideaway he's too happy harryv hideaway, that was not cool what did he ever do? harryv so what? hideaway he asked too many questions ??? Lori17 [EMAIL PROTECTED] has joined #FreeBSDHelp raistlin` lol harryv let me remind you this is freebsdhelp hideaway OH WoW hideaway THANKS! ??? mode/#FreeBSDHelp [+b [EMAIL PROTECTED] by hideaway You have been kicked off #FreeBSDHelp by hideaway (go join your fucking loser friend) ??? [#freebsdhelp] Banned from channel freebsdhelp: No such nick/channel ??---?--??-??---?--??-?--- -- - | hideaway ([EMAIL PROTECTED]) (unknown) ? ircname : Pete Fritchman [EMAIL PROTECTED] -- Does he work for Freebsd? ? server : irc.mindspring.com (EarthLink, Inc.) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Post-installation configuration problems with FreeBSD 4.4
On Dec 12, 2003, at 11:27 AM, Walt Haynes wrote: I've installed FreeBSD 4.4 from the CD-ROM included in my FreeBSD Unleashed book (I installed 4.4 instead of 5.0 because it's supposedly more stable; 5.0 is a pre-release snapshot.). When I try to do the X Server configuration stuff, the server won't start and, consequently, X-Windows won't start. My video card is CinePak Codec by Radius, Inc. and my monitor is a 15 ASTVision 4i (Intel (r) 82810 graphics controller with 4MB memory, screen refresh rate of 60 hertz, resolution is 800x600, and 24 bit color quality. For the card option, CinePak doesn't show up in the list of potentials. Can you tell me what I might be doing wrong in my attempt to configure X server ? By the way, I have FreeBSD installed in a primary partition on a system on which I also run Windows XP Professional with Boot US boot manager. I'd appreciate any information that you can provide. Thank you. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You're just a teensy bit outdated. FreeBSD 5.x is -RELEASE, just not -STABLE. and the latest version of FreeBSD 4.x is 4.9. This might be your problem. Check freebsd.org. Randi Harper [EMAIL PROTECTED] http://freebsdgirl.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
