RE: cannot mount IDE disk under FreeBSD-4.1.1-STABLE
Hi all, I apologize if this is the wrong place to ask such questions. I've tried to ask in freebsd-questions, but no one ever replied. The disklabel output is as follows: root@dns :~# disklabel ad1 # /dev/ad1c: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 29826 sectors/unit: 30064608 rpm: 5400 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] c: 3006460804.2BSD 1024 819216 # (Cyl.0 - 29825) I hope this helps. One more question; how do you change the rpm value for a disk? Thanks in advance. Noor -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Antoine Beaupre Sent: Wednesday, November 08, 2000 1:05 AM To: Noor Dawod Cc: [EMAIL PROTECTED] Subject: Re: cannot mount IDE disk under FreeBSD-4.1.1-STABLE Send disklabel ad1 output. You are trying to mount the wrong partition (c) on your drive. The c partition is symbolic and represents the whole drive. You probably have another partition to mount. BTW, this does not belong to -stable, from what I understand of your problem. Am I right here, people? A. On Wed, 8 Nov 2000, Noor Dawod wrote: Hello all, Our server was upgraded recently. At first, it had a SCSI disk. This was the boot disk. An additional IDE disk was connected as secondary backup disk. Recently, as said, we upgraded the server by moving the SCSI disk from its booting status to be a regular disk, and installed instead an IDE disk that was set bootable. The old IDE disk was connected as secondary on the IDE port to the new IDE disk. The problem is that I am not able to mount the old IDE now. Here are the info about the old disk: *** Working on device /dev/ad1 *** parameters extracted from in-core disklabel are: cylinders=29826 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=29826 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 5 (24 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 255 Observe what happens when I try to mount it: root@dns :~# mount -t ufs /dev/ad1c /disk3 mount: Operation not permitted Also: root@dns :~# mount -t ufs /dev/ad1 /disk3 mount: Operation not permitted Anyone can direct me what to do in order to mount this disk? By the way, the system identifies the disk and I can see it in dmesg. Please help if you can. TIA. Noor. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: wierd printout from dmesg
If y understand, there is a window where you have new userland and old kernel. I have experienced big problems (even panics) with these mixings in the transition 4.1 - 4.2 It seeems that things have changed so much that userland utilities can even panic mismatched kernels. Reboot single user, with the new kernel, mount -a, and make installworld and reboot. Then all problems where fixed in the two upgrades i have done, moreover some bugs i had with 4.1 are fixed now. -- Michel TALON To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.1.1-Release and PR kern/19162 still actual
Hello! I have 4.1.1-RELEASE box. Recently I'v got a few rebooting on my FreeBSD box for a day. After some investigation I discover one my user had reach inode limit and when he tried write some file crash happened. After the user removed some files crashings had stop. I looked for PR, and found kern/19162 exectly for my case. But it was reported for 4.0-S and still open. Please take into consideration it. -- Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: rc.firewall script natd on 4.1.1
"Crist J . Clark" wrote: Details please? The natd(8) process is not actually started from rc.firewall, but from rc.network. In which of these is the supposed breakage? Or do you mean the divert(4) rule in rc.firewall is not being added properly? That's right ! Could you post the actual problem and the versions of the file(s) you are using? -- Crist J. Clark [EMAIL PROTECTED] Bad file: # Setup system for firewall service. # $FreeBSD: src/etc/rc.firewall,v 1.30.2.6 2000/09/21 07:44:53 ru Exp $ And that one works and adds natd divert rule to ipfw correctly # Setup system for firewall service. # $FreeBSD: src/etc/rc.firewall,v 1.30.2.4 2000/05/28 19:17:15 asmodai Exp $ Cuk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stability
Roman Shterenzon wrote: I've a perfectly good PR about vinum (panics) open. There's no even single follow up (kern/22103). I couldn't stand it any longer, so I'm not able to recreate it since I'm using raid1 on those disks now. I waited for almost one month but aparently nothing was done. (I opened one PR before that but it was badly formatted and had to become closed). I understand that people have other things to do, and FreeBSD is volunteer project, but we shall face the truth - the man page for vinum should state that RAID5 is experimental and prone to crashes. It should be emphasized that it shouldn't be used in sensitive environmets. I know other people for whom it rendered their servers unusable. I managed 8( to crash it today as well. I'll probably move to hardware raid solution instead, I'm quite fed up with vinum. Wich good hardware solution is supported under FreeBSD ? I've a crash dump of today, perhaps I'll open another PR. I've had crash before one hour, and I've only doing cvsup ports Yesterday I was changing speed of ipfw pipe and it crashed after a second. I cannot imagine such things. I can't have 20 days of uptime because of so many crashes. Yes, I know a solution for stable FreeBSD. Leave it completly alone and don't do anything. It's no good. Fbsd is 4.1. Cuk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1.1-Stable
On Tue, 07 Nov 2000 23:08:12 -0500 Michael DeMutis [EMAIL PROTECTED] wrote: Yikes, I'm lost. I had always thought that the RELENG_4 tag was always going to carry the 4.x-STABLE name. And that the BETA was really 4.x-CURRENT ? What happened to CURRENT or has it been done away with? There is only one CURRENT and it has 5 for the leading digit. There are three RELENG branches (more or less) alive, RELENG_2, RELENG_3 and RELENG_4. RELENG branches cycle through STABLE - BETA - RELEASE - STABLE ... BETA is the lockdown and test period prior to RELEASE when things are most stable. RELEASE is a point, and STABLE is the rest of the time. -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Stability
* Marko Cuk [EMAIL PROTECTED] [001108 01:52] wrote: Roman Shterenzon wrote: I've a perfectly good PR about vinum (panics) open. There's no even single follow up (kern/22103). I couldn't stand it any longer, so I'm not able to recreate it since I'm using raid1 on those disks now. I waited for almost one month but aparently nothing was done. (I opened one PR before that but it was badly formatted and had to become closed). I understand that people have other things to do, and FreeBSD is volunteer project, but we shall face the truth - the man page for vinum should state that RAID5 is experimental and prone to crashes. It should be emphasized that it shouldn't be used in sensitive environmets. I know other people for whom it rendered their servers unusable. I managed 8( to crash it today as well. I'll probably move to hardware raid solution instead, I'm quite fed up with vinum. Wich good hardware solution is supported under FreeBSD ? AMI MegaRAID and Mylex are a good bet, they are very stable for me. I've a crash dump of today, perhaps I'll open another PR. I've had crash before one hour, and I've only doing cvsup ports Yesterday I was changing speed of ipfw pipe and it crashed after a second. I cannot imagine such things. I can't have 20 days of uptime because of so many crashes. Yes, I know a solution for stable FreeBSD. Leave it completly alone and don't do anything. It's no good. Fbsd is 4.1. This isn't a useful bug report, please see: http://www.freebsd.org/handbook/kerneldebug.html Furthermore, I'm sorry FreeBSD isn't stable for you, but things like vinum and ipfw pipe are quite new to FreeBSD, with good bug reports these features could be made more stable, but right now I wouldn't recommend twiddling too much with vinum in RAID 5 mode (RAID 0/1 is fine). -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
4.2-BETA release candidate #1 ISO installation image available
Please see: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.2-RC1-install.iso For an installatable ISO image with packages and XFree86 3.3.6 bits (MD5 checksum is in CHECKSUM.MD5 in the same directory). The FTP installable version is also uploading to the FTP site and will be available from ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ shortly. Please test this all you can! Thanks. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pkg_version does not work for ports that add -gtk suffix
Greetings, Thanks for the update. My pleasure to work on it, really. Anyway, I looked into the files is /usr/ports/Mk and realised that there are others prefixes too like -esound, -glib, ... then there are more stuff like apache/mod_ssl/php ... It gets way complicatd. Glad to know someone better at it is working on it. Regards, /calvin lines with : are quotes from Bruce A. Mah's email : If memory serves me right, Calvin NG wrote: : :Just send my first PR ever. Anyway, maybe we can slip this :into 4.2?? Or is it too late? : : Description: : :Recently, some of the the ports that define 'USE_GTK' :adds the '-gtk' suffix to the package name/port name. :This breaks the pkg_version utility as it cannot fine :the portname/package in the INDEX file. : : I've closed this PR, because an upcoming commit to bsd.port.mk after the : release will activate some pkg_* changes (proposed by sobomax) that will : deal with this problem, as well as some other similar ones. You can : follow the related discussion in the archives for the -ports list by : looking for messages with the subject "PROPOSAL: Use @comment PLIST : variable to track where installed packages came from". : : Thanks for taking the time to look into this problem though! : : Bruce. : : : To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: docproj port still broken in 4.2-RELEASE
On Tue, Nov 07, 2000 at 12:01:09PM -0800, Jordan Hubbard wrote:
=== Cleaning for tidy-2804
=== Cleaning for w3m-0.1.11.p.17
=== Cleaning for docproj-1.1
make: don't know how to make all. Stop
*** Error code 2
Stop in /usr/src/release.
*** Error code 1
I'm going to have to disable docs for this build if we can't get
this fixed. :-(
Some questions, for anyone that's building a release, and can afford to
spend some time poking around on my behalf;
(1) Are you building this with a specific RELEASETAG? If so, what is it?
The "make: don't know how to make all. Stop" line is consistent with
running make(1) in a directory that doesn't contain a {m,M}akefile.
(2) Could you check if ${CHROOTDIR}/usr/doc actually contains any files?
(3) If it does contain files, can you tell me what revision numbers the
files are.
Cheers,
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: We cannot use 'make -j' option to build the world, period.
Regarding the -j option, I seem to remember someone telling me that option was only for make buildworld/installworld and not the modules or anything else. This information is outdated I believe. This used to be true however, I can attest to having built 4.x worlds with -j 4 many times. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: docproj port still broken in 4.2-RELEASE
On Tue, Nov 07, 2000 at 12:01:09PM -0800, Jordan Hubbard wrote:
=== Cleaning for tidy-2804
=== Cleaning for w3m-0.1.11.p.17
=== Cleaning for docproj-1.1
make: don't know how to make all. Stop
*** Error code 2
Stop in /usr/src/release.
*** Error code 1
I'm going to have to disable docs for this build if we can't get
this fixed. :-(
Working on it. It would be very helpful if you (or someone else) could
forward me a copy of the ${CHROOTDIR}/mk shellscript when this happens,
so I can try and replicate this without doing a full release.
[ Yes, I know that in an ideal world I'd do a release -- however, in an
ideal world I'd not be spending the majority of my time travelling,
with a laptop that fails to suspend to disk/memory reliably. If I
can duplicate this without needing to build a release I can try and get
a fix faster. ]
N
--
Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95.
Telephone line, $24.95 a month. Software, free. USENET transmission,
hundreds if not thousands of dollars. Thinking before posting, priceless.
Somethings in life you can't buy. For everything else, there's MasterCard.
-- Graham Reed, in the Scary Devil Monastery
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
