Re: Corrupted OS
/etc/fstab says ufs. Is there a better way to check if its ufs2? Drew2 Garrett Cooper [EMAIL PROTECTED] wrote: On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote: How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew Well, I was curious because I thought it could be something to deal with the 2GB file limit. You still haven't answered my question about the filesystem though: are you using UFS2 or something else? Thanks, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Sat, Mar 17, 2007 at 01:39:17AM +0100, Wojciech Puchar wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. upgrade to what? of course it's is possible to do this with any version. Probably he means he is at the currently highest RELEASE level. Maybe he doesn't want to go to CURRENT. Anyway, that won't change file size restraints. 6.2 is already there. jerry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Drew Jenkins wrote: /etc/fstab says ufs. Is there a better way to check if its ufs2? Drew2 Garrett Cooper [EMAIL PROTECTED] wrote: On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote: How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew Well, I was curious because I thought it could be something to deal with the 2GB file limit. You still haven't answered my question about the filesystem though: are you using UFS2 or something else? Thanks, -Garrett The easiest way to figure out if you're running UFS2 is to go to the disk label feature within sysinstall, and define a mount point for the slice. Make sure _not_ to make any changes though as you'll be thrusting yourself in the middle of a system upgrade (CTRL-C is your friend). If it's ufs1, it should definitely be converted to ufs2. There were some serious limitations in ufs1, in particular dealing with file size (2GB limit I believe) and features. Someone else on the list might be able to advise you or point you in the right direction if you want more details.. Also, you should be running softupdates. If not you're playing a risky game of russian roulette with your data, where if corrupted things can disappear between reboots if you didn't power down the machine properly (power down via ATX dead man power switch, power loss, etc). If all else fails and you're not running ufs1 on the disk, try upgrade your bios or firmware controller that the disk is operating on, and get back to us with more details. Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
I go to run /usr/sbin/sysinstall. It brings up a little GUI and asks me to select. I selected post-installation configuration, and it sent me back to a prompt! So I tried again, selecting the recommended configuration to start over again, and it again sent me back to a prompt! Besides, this is kinda dangerous. Got another, perhaps more complex but *safer* way to determine if it's ufs1 or 2? 2Also, what are softupdates and why do I need them? TIA, Drew Garrett Cooper [EMAIL PROTECTED] wrote: Drew Jenkins wrote: /etc/fstab says ufs. Is there a better way to check if its ufs2? Drew2 Garrett Cooper wrote: On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote: How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew Well, I was curious because I thought it could be something to deal with the 2GB file limit. You still haven't answered my question about the filesystem though: are you using UFS2 or something else? Thanks, -Garrett The easiest way to figure out if you're running UFS2 is to go to the disk label feature within sysinstall, and define a mount point for the slice. Make sure _not_ to make any changes though as you'll be thrusting yourself in the middle of a system upgrade (CTRL-C is your friend). If it's ufs1, it should definitely be converted to ufs2. There were some serious limitations in ufs1, in particular dealing with file size (2GB limit I believe) and features. Someone else on the list might be able to advise you or point you in the right direction if you want more details.. Also, you should be running softupdates. If not you're playing a risky game of russian roulette with your data, where if corrupted things can disappear between reboots if you didn't power down the machine properly (power down via ATX dead man power switch, power loss, etc). If all else fails and you're not running ufs1 on the disk, try upgrade your bios or firmware controller that the disk is operating on, and get back to us with more details. Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Saturday 17 March 2007 4:14 pm, Drew Jenkins wrote: I go to run /usr/sbin/sysinstall. It brings up a little GUI and asks me to select. I selected post-installation configuration, and it sent me back to a prompt! So I tried again, selecting the recommended configuration to start over again, and it again sent me back to a prompt! Besides, this is kinda dangerous. Got another, perhaps more complex but *safer* way to determine if it's ufs1 or 2? 2Also, what are softupdates and why do I need them? Soft updates Soft updates change the way the file system performs I/O. They enable metadata to be written less frequently. This can give rise to dramatic performance improvements under certain circumstances, such as file deletion. Specify soft updates with the -U option when creating the file system. (pg 191 The complete FreeBSD) TIA, Drew Garrett Cooper [EMAIL PROTECTED] wrote: Drew Jenkins wrote: /etc/fstab says ufs. Is there a better way to check if its ufs2? Drew2 Garrett Cooper wrote: On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote: How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew Well, I was curious because I thought it could be something to deal with the 2GB file limit. You still haven't answered my question about the filesystem though: are you using UFS2 or something else? Thanks, -Garrett The easiest way to figure out if you're running UFS2 is to go to the disk label feature within sysinstall, and define a mount point for the slice. Make sure _not_ to make any changes though as you'll be thrusting yourself in the middle of a system upgrade (CTRL-C is your friend). If it's ufs1, it should definitely be converted to ufs2. There were some serious limitations in ufs1, in particular dealing with file size (2GB limit I believe) and features. Someone else on the list might be able to advise you or point you in the right direction if you want more details.. Also, you should be running softupdates. If not you're playing a risky game of russian roulette with your data, where if corrupted things can disappear between reboots if you didn't power down the machine properly (power down via ATX dead man power switch, power loss, etc). If all else fails and you're not running ufs1 on the disk, try upgrade your bios or firmware controller that the disk is operating on, and get back to us with more details. Cheers, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Drew Jenkins wrote:
I go to run /usr/sbin/sysinstall. It brings up a little GUI and asks
me to select. I selected post-installation configuration, and it sent
me back to a prompt! So I tried again, selecting the recommended
configuration to start over again, and it again sent me back to a
prompt! Besides, this is kinda dangerous. Got another, perhaps more
complex but *safer* way to determine if it's ufs1 or 2?
2Also, what are softupdates and why do I need them?
TIA,
Drew
Garrett Cooper [EMAIL PROTECTED] wrote: Drew Jenkins wrote:
/etc/fstab says ufs. Is there a better way to check if its ufs2?
Drew2
Garrett Cooper wrote: On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote:
How large is large? Why filesystem are you using with what
options?The MySQL database was just under a gigabyte, and the Zope
Data.fs file/database was somewhere under 2 gigabytes. Options? No
options. I had symlinks from where these dbases were supposed to
live on the SCSI drives to the 500 GB drive. Then suddenly, poof!
They were gone.
Drew
Well, I was curious because I thought it could be something to deal
with the 2GB file limit. You still haven't answered my question about
the filesystem though: are you using UFS2 or something else?
Thanks,
-Garrett
The easiest way to figure out if you're running UFS2 is to go to the
disk label feature within sysinstall, and define a mount point for the
slice. Make sure _not_ to make any changes though as you'll be thrusting
yourself in the middle of a system upgrade (CTRL-C is your friend).
If it's ufs1, it should definitely be converted to ufs2. There were some
serious limitations in ufs1, in particular dealing with file size (2GB
limit I believe) and features. Someone else on the list might be able to
advise you or point you in the right direction if you want more details..
Also, you should be running softupdates. If not you're playing a risky
game of russian roulette with your data, where if corrupted things can
disappear between reboots if you didn't power down the machine properly
(power down via ATX dead man power switch, power loss, etc).
If all else fails and you're not running ufs1 on the disk, try upgrade
your bios or firmware controller that the disk is operating on, and get
back to us with more details.
Cheers,
-Garrett
In order to get to disk label without installing from scratch, go to
Configure - Label. Then select your Disk, press Ok. Once the next
window comes up, press M and select a mount point for the slice. Then
look off to the right and see what version of UFS the slice is using.
Another (maybe safer?) way to do this is to run /sbin/tunefs -p
/dev/{disk+slicename}. See if something like...
tunefs: soft updates: (-n) disabled
... pops up. I used my / slice as an example, so soft updates are
automatically disabled for it (I think this has to deal with single user
mode and fsck?).
A short description of softupdates is available here:
http://en.wikipedia.org/wiki/Softupdates, and you should read the 2nd
reference if you want more detailed info about them.
Also, could you please bottom post. Top posting is hard to read and
bottom-posting is the defacto standard on the FreeBSD lists.
Thanks,
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Sat, 17 Mar 2007 13:09:12 -0700 Garrett Cooper wrote: Drew Jenkins wrote: /etc/fstab says ufs. Is there a better way to check if its ufs2? Drew2 Garrett Cooper [EMAIL PROTECTED] wrote: On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote: How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew Well, I was curious because I thought it could be something to deal with the 2GB file limit. You still haven't answered my question about the filesystem though: are you using UFS2 or something else? Thanks, -Garrett The easiest way to figure out if you're running UFS2 is to go to the disk label feature within sysinstall, and define a mount point for the slice. Make sure _not_ to make any changes though as you'll be thrusting yourself in the middle of a system upgrade (CTRL-C is your friend). Perhaps even a bit easier: paqi% dumpfs /dev/ad0s2a | head -1 magic 19540119 (UFS2) timeSun Mar 18 15:48:35 2007 Also, 'dumpfs device | head -20' provides far more than anyone wants to know but including maxfilesize, flags (eg none or soft-updates) and fsmnt (last mounted on). Works on unmounted or mounted drives. Cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On 16/03/07, Drew Jenkins [EMAIL PROTECTED] wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. What are you trying to do? You could always go to /usr/src and do a make buildworld, which would rebuild the entire FreeBSD userland. Ports can be rebuilt, too, for example by doing a portupgrade -afk TIA, Drew Christian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Well, that's what I thought, I just wanted to be sure. I've done that once before. As I recall, there was a very long string of questions I had to answer at one point. I pretty much just told the system not to change things, go with defaults, etc. That's the safest bet, right? This is similar to reinstalling Windoze on top of an existing installation, right? TIA, Drew - Original Message From: Christian Walther [EMAIL PROTECTED] To: Drew Jenkins [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, March 16, 2007 6:45:40 AM Subject: Re: Corrupted OS On 16/03/07, Drew Jenkins [EMAIL PROTECTED] wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. What are you trying to do? You could always go to /usr/src and do a make buildworld, which would rebuild the entire FreeBSD userland. Ports can be rebuilt, too, for example by doing a portupgrade -afk TIA, Drew Christian Don't get soaked. Take a quick peek at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Hello Drew, The procedure is described in the handbook chapter 21. May I suggest that you look at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html In your case, if you don't want to upgrade your source code, you could probably skip to chapter 21.4 and also skip the buildkernel and mergemaster steps. I am assuming you have the source code to buildworld in /usr/src/? Good luck! Drew Jenkins skrev: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. TIA, Drew 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
How do I know the kernel has not become corrupted? Actually, as I think about it, I should probably rebuild the kernel anyway to work with packet filters. Here are my notes from the last time I updated: /usr/src/UPDATING and /usr/src/Makefile? I'm not sure what I mean by the above, but should I use the Makefile and not UPDATING? synch your source to 6.2 How? And is this necessary since it's already at 6.2? cvsup -g -L 2 supfile cd /usr/src make clean;make cleanworld make buildworld cd /usr/src/sys/i386/conf/ # back up any custom config there is cp GENERIC BACKUP_CONFIG cd /usr/src make buildkernel KERNCONF=LOCAL # use this from now on! make installkernel KERNCONF=LOCAL # use this from now on! # Note: LOCAL is a copy of GENERIC in the same folder (/usr/src/sys/i386/conf/GENERIC) # with changes for pf as follows: # # Packet Filters # device pf # device pflog # device pfsync # options ALTQ # options ALTQ_CBQ# Class Bases Queuing (CBQ) # options ALTQ_RED# Random Early Detection (RED) # options ALTQ_RIO# RED In/Out # options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) # options ALTQ_PRIQ # Priority Queuing (PRIQ) sh /etc/rc.shutdown # kills all your services pkill sendmail pkill syslogd mergemaster -p make installworld mergemaster reboot /usr/local/bin/portmanager -u -f -l -y make delete-old-libs What happens if my internet connection dies when I'm doing this? Will I still be able to SSH into my box? TIA, Drew We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Drew Jenkins wrote: How do I know the kernel has not become corrupted? Actually, as I think about it, I should probably rebuild the kernel anyway to work with packet filters. Here are my notes from the last time I updated: /usr/src/UPDATING and /usr/src/Makefile? I'm not sure what I mean by the above, but should I use the Makefile and not UPDATING? You meant to remind yourself to read those files. Esp. UPDATING. synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). OTOH, if you are attempting to get up to date on security fixes, etc., then you should read up on the Cutting Edge so that you understand the CVS tags, and use cvsup as shown below. Be *certain* you have the CVS tag you really want in the supfile before you press enter, though. Now, if you think that the system is corrupt because your source tree is corrupt, then you would also want to sync your source tree. Of course, why would it be corrupt? If a committer made an error, you'd probably see some discussion of it on this list of the stable@ list. cvsup -g -L 2 supfile cd /usr/src make clean;make cleanworld I never do this, and am not really familiar with that target. Same as `rm -rf /usr/obj`, perhaps? I'll have to check, heh make buildworld OK. Actually might need mergemaster -p before this on some occasions, but if you're not technically *updating* (i.e., you aren't getting new source code via cvsup), it shouldn't be an issue, but this is where it's supposed to go, not where you have it below. cd /usr/src/sys/i386/conf/ # back up any custom config there is cp GENERIC BACKUP_CONFIG cd /usr/src make buildkernel KERNCONF=LOCAL # use this from now on! make installkernel KERNCONF=LOCAL # use this from now on! # Note: LOCAL is a copy of GENERIC in the same folder (/usr/src/sys/i386/conf/GENERIC) # with changes for pf as follows: # # Packet Filters # device pf # device pflog # device pfsync # options ALTQ # options ALTQ_CBQ# Class Bases Queuing (CBQ) # options ALTQ_RED# Random Early Detection (RED) # options ALTQ_RIO# RED In/Out # options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) # options ALTQ_PRIQ # Priority Queuing (PRIQ) OK, that's fine. This next stuff is a tad strange, any reason you can't just shutdown -r now? The point is to attempt to boot with the new kernel, and going to single-user at this point doesn't do that. sh /etc/rc.shutdown # kills all your services pkill sendmail pkill syslogd mergemaster -p As noted above, this (mergemaster -p) is actually meant to be done pre-buildworld ... see mergemaster(8). Now, after the reboot (and technically, you're supposed to be in single-user now, but I've found on lower-traffic boxes it's generally not necessary for me to do that) you do this: make installworld mergemaster And you have a rebuilt system, kernel and userland. reboot A reboot is not needed at this point, because you did it above. /usr/local/bin/portmanager -u -f -l -y make delete-old-libs This is about ports, so a different subject. ;-) What happens if my internet connection dies when I'm doing this? Will I still be able to SSH into my box? Err, my first thought was, what kind of a question is that? Without an internet connection you can't use SSH ;-) Thinking a tad more clearly, I suppose you mean, since the process of upgrading (buildworld, installworld, whatever) is attached to my terminal (which is an SSH session), what happens if I'm disconnected - will my upgrade continue? The answer is that it will not continue unless you've planned for that possibility. Are you familiar with job control, e.g.: $ make buildworld HTH, Kevin Kinsey -- A real diplomat is one who can cut his neighbor's throat without having his neighbor notice it. -- Trygve Lie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
2Kevin Kinsey [EMAIL PROTECTED] wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Yes. The system was working fine. The problem is with an extra HD I have that I told the server farm to check out thoroughly before installing it in the new server because I knew it had a problem. They said they didand didn't. So that's what corrupted the system again...exactly the same way it did before, too. But yes, the system was working fine before I had data files on the HD in question linked to s/w on the SCSI hard drives. OTOH, if you are attempting to get up to date on security fixes, etc., then you should read up on the Cutting Edge so that you understand the CVS tags, and use cvsup as shown below. Well, it never hurts to get up to date on security, does it? Where do I find this cutting edge? Be *certain* you have the CVS tag you really want in the supfile before you press enter, though. Will that be outlined in the cutting edge, or elsewhere? Now, if you think that the system is corrupt because your source tree is corrupt, then you would also want to sync your source tree. Of course, why would it be corrupt? If a committer made an error, you'd probably see some discussion of it on this list of the stable@ list. The HD zapped two data files--MySQL and a Zope instance Data.fs--and that's what caused the problem both times. I doubt this would have hurt the source tree. Your thoughts? OK, that's fine. This next stuff is a tad strange, any reason you can't just shutdown -r now? The point is to attempt to boot with the new kernel, and going to single-user at this point doesn't do that. I need to avoid single user mode, as you probably recognize, since the machine is on the other side of the planet. The below worked when I upgraded once from 5.5 to 6.1. sh /etc/rc.shutdown # kills all your services pkill sendmail pkill syslogd mergemaster -p As noted above, this (mergemaster -p) is actually meant to be done pre-buildworld ... see mergemaster(8). In other words, it's not necessary since I'm just rebuilding what I already have, right? Thinking a tad more clearly, I suppose you mean, since the process of upgrading (buildworld, installworld, whatever) is attached to my terminal (which is an SSH session), what happens if I'm disconnected - will my upgrade continue? No, what I mean is if my connection gets dropped. The answer is that it will not continue unless you've planned for that possibility. Are you familiar with job control, e.g.: $ make buildworld Ah! Good idea! So just use the old symbol. How do I know when it's finished? Putting jobs in the background, one can't see their progress, that is, I don't know how to monitor it if it's not flashing before my face ;) And that's the only place I have to put a job in the background? Reviewing my notes again, that wouldn't be necessary for any of the following? make clean;make cleanworld make buildkernel KERNCONF=LOCAL make installkernel KERNCONF=LOCAL make installworld ...and I don't need this either, since I'm not doing mergmaster at all, right? mergemaster TIA, Drew - Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, 16 Mar 2007 07:16:33 -0700 (PDT) Drew Jenkins [EMAIL PROTECTED] wrote: Well, it never hurts to get up to date on security, does it? Where do I find this cutting edge? It's a badly named chapter in the handbook, but the process for following a security branch is the same as tracking a development branch. BTW if you are just rebuilding, or picking up minor changes on a security branch, there is no need for mergemaster. I don't bother with single user mode either, since so little's changing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Christian Walther wrote: On 16/03/07, Drew Jenkins [EMAIL PROTECTED] wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. What are you trying to do? You could always go to /usr/src and do a make buildworld, which would rebuild the entire FreeBSD userland. Ports can be rebuilt, too, for example by doing a portupgrade -afk TIA, Drew Christian Drew, Depends on how corrupted it is. Could you provide details? Thanks, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Thanks :) - Original Message From: RW [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Friday, March 16, 2007 10:31:53 AM Subject: Re: Corrupted OS On Fri, 16 Mar 2007 07:16:33 -0700 (PDT) Drew Jenkins [EMAIL PROTECTED] wrote: Well, it never hurts to get up to date on security, does it? Where do I find this cutting edge? It's a badly named chapter in the handbook, but the process for following a security branch is the same as tracking a development branch. BTW if you are just rebuilding, or picking up minor changes on a security branch, there is no need for mergemaster. I don't bother with single user mode either, since so little's changing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
You have probably already read those details in another one of my emails between when you emailed and when I responded to yours, but in case not, here it is again: I executed a bad command on my old server which I am convinced damaged a 500 GB HD I had. The server farm says otherwise, but it is in their best interest to talk a lot and do as little work as possible...and rake in more money for screwing up OS's, etc. So I had them build out another server which I built out after they got me up. First, however, I built a mirror server here and wrote down every command I executed in building it, to make sure there would be no mistakes. Then one day, all of a sudden, when I wasn't doing any work at all in the given areas, two of my databases got wiped: MySQL and one of my Zope instances' Data.fs, both of which were symlinked to the SCSI HDs from the 500 GB HD. This is exactly what happened on the old server, except on the old one it happened because of an erroneous copy command. Now, strange little things are happening for which there is no logical explanation other than corruption of the OS...exactly what transpired on the old server. Well, that's more detail than in my last email ;) TIA, Drew - Original Message From: Garrett Cooper [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Friday, March 16, 2007 10:43:38 AM Subject: Re: Corrupted OS Christian Walther wrote: On 16/03/07, Drew Jenkins [EMAIL PROTECTED] wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. What are you trying to do? You could always go to /usr/src and do a make buildworld, which would rebuild the entire FreeBSD userland. Ports can be rebuilt, too, for example by doing a portupgrade -afk TIA, Drew Christian Drew, Depends on how corrupted it is. Could you provide details? Thanks, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, Mar 16, 2007 at 05:09:15PM +0700, Drew Jenkins wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. I am not sure just what you are trying to avoid. First of all, strictly speaking, when installing FreeBSD you never format or reformat the hard-drive. That is a much lower level operation. FreeBSD and all other OSen use the factory format unless you do something unusually drastic. Doing fdisk/bsdlabel/newfs is not technically 'formatting' the drive but rather building slices, partitions and filesystems on the drive. Now. You do not have to redo the fdisk, bsdlabel and newfs to wipe out and reinstall things, but why not do them? They take very little time.The only reason I could think of would be if you have a lot of your own files you don't want to nuke. But, in that case, the better course of action would be to back them up somewhere safe and do the complete reinstall from scratch and then bring your own files back. jerry TIA, Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey [EMAIL PROTECTED] wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Drew, Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yes. The system was working fine. The problem is with an extra HD I have that I told the server farm to check out thoroughly before installing it in the new server because I knew it had a problem. They said they didand didn't. So that's what corrupted the system again...exactly the same way it did before, too. But yes, the system was working fine before I had data files on the HD in question linked to s/w on the SCSI hard drives. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. OTOH, if you are attempting to get up to date on security fixes, etc., then you should read up on the Cutting Edge so that you understand the CVS tags, and use cvsup as shown below. Well, it never hurts to get up to date on security, does it? Where do I find this cutting edge? Be *certain* you have the CVS tag you really want in the supfile before you press enter, though. Will that be outlined in the cutting edge, or elsewhere? Now, if you think that the system is corrupt because your source tree is corrupt, then you would also want to sync your source tree. Of course, why would it be corrupt? If a committer made an error, you'd probably see some discussion of it on this list of the stable@ list. The HD zapped two data files--MySQL and a Zope instance Data.fs--and that's what caused the problem both times. I doubt this would have hurt the source tree. Your thoughts? My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. The only ways that the new HD could be involved would be either if you executed something on that disk or if it was being improperly incorporated in to a mirror. jerry ..stuff about upgrading excised.. ...and I don't need this either, since I'm not doing mergmaster at all, right? mergemaster TIA, Drew - Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
I have lots of other files, yes, several gigabytes worth. I have a satellite dish connection, which for uploading has all the speed of a telephone line. It's a production server. And I don't have my hands on the console. I think I'll avoid fdisk, but thanks anyway ;) Drew - Original Message From: Jerry McAllister [EMAIL PROTECTED] To: Drew Jenkins [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Sent: Friday, March 16, 2007 11:17:55 AM Subject: Re: Corrupted OS On Fri, Mar 16, 2007 at 05:09:15PM +0700, Drew Jenkins wrote: 23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. I am not sure just what you are trying to avoid. First of all, strictly speaking, when installing FreeBSD you never format or reformat the hard-drive. That is a much lower level operation. FreeBSD and all other OSen use the factory format unless you do something unusually drastic. Doing fdisk/bsdlabel/newfs is not technically 'formatting' the drive but rather building slices, partitions and filesystems on the drive. Now. You do not have to redo the fdisk, bsdlabel and newfs to wipe out and reinstall things, but why not do them? They take very little time.The only reason I could think of would be if you have a lot of your own files you don't want to nuke. But, in that case, the better course of action would be to back them up somewhere safe and do the complete reinstall from scratch and then bring your own files back. jerry TIA, Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. Which I did. Trust me. I've ruled everything else out. It's the HD. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, and do it remotely? Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. That I am not doing. There are two other disks in the box that are SCSIs. My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. You misread. The files were on the new HD. The action scripts, or s/w that calls those dbase files, are on the SCSI drives. TIA, Drew - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
How do I access it (through SSH) if it's unmounted? Drew2 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 09:11:58AM -0700, Drew Jenkins wrote: Jerry McAllister wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. Which I did. Trust me. I've ruled everything else out. It's the HD. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, and do it remotely? Yes. You just have to have everything on that disk unmounted. Then you can run fdisk either directly or via sysinstall. I have lost track of where you have stuff you want to protect, etc, etc. But a separate disk that you want to wipe and start over again on can be fdisked, bsdlabeled and newfsed independently from the one you are booted from and not affect anything on any other disk and you don't need to be able to touch it, just unmount what is currently there. jerry Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. That I am not doing. There are two other disks in the box that are SCSIs. My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. You misread. The files were on the new HD. The action scripts, or s/w that calls those dbase files, are on the SCSI drives. TIA, Drew - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. - Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, Mar 16, 2007 at 09:12:02AM -0700, Drew Jenkins wrote: Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. Which I did. Trust me. I've ruled everything else out. It's the HD. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, and do it remotely? Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. That I am not doing. There are two other disks in the box that are SCSIs. My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. You misread. The files were on the new HD. The action scripts, or s/w that calls those dbase files, are on the SCSI drives. That is a much bigger problem then. You can't just go and rebuild stuff and expect to keep the files on that disk. You might be able to used fdisk if the slice table got smuched and if you put back exactly what was originally there. You might even be able to use bsdlabel to fix a partition table, again if the new was exactly the same as the old, but I am not sure of that. You must not attempt to build filesystems on the disk with newfs or then all will be gone and beyond recovery except by those very expensive spy type folk that try to get secret information from overwritten storage. But, what you are describing is not a corrupt OS. It is a problem with reading information from a disk.I have responded to several different people lately on similar issues and can't remember which is which. If it is a bad space on disk, then you are going to have to reconstruct the date by reading as much as you can and putting it together the hard way. If it is some incompatibilty the file system versions between how it written and being read, you need to track down just how it was written and try to bridge the difference. jerry TIA, Drew - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, 16 Mar 2007, Drew Jenkins wrote: How do I access it (through SSH) if it's unmounted? Drew2 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 09:11:58AM -0700, Drew Jenkins wrote: Jerry McAllister wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. Which I did. Trust me. I've ruled everything else out. It's the HD. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, and do it remotely? Yes. You just have to have everything on that disk unmounted. Then you can run fdisk either directly or via sysinstall. I have lost track of where you have stuff you want to protect, etc, etc. But a separate disk that you want to wipe and start over again on can be fdisked, bsdlabeled and newfsed independently from the one you are booted from and not affect anything on any other disk and you don't need to be able to touch it, just unmount what is currently there. jerry Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. That I am not doing. There are two other disks in the box that are SCSIs. My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. You misread. The files were on the new HD. The action scripts, or s/w that calls those dbase files, are on the SCSI drives. TIA, Drew In true grumpier old men style: you mount the disk son :) (after logging in via ssh). Jerry can provide you with the RAID specific details. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
I believe you misunderstand. I have 3 disks: 2 are SCSI RAID and are 80 GB each 1 is not and is 500 GB I don't actually need the 500 GB now. I haven't even used up the 80 GB HD's. So I can wipe the 500 GB clean. I don't have to keep data on it at all. But...can I do that remotely, and run those commands remotely, with that disk being unmounted, and if so...how? The problem *is* a corrupt OS. I currently don't have any data on that 500 GB HD. And the problems persist. Sorry to have confused you. Are things clearer now? TIA, Drew2 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 09:12:02AM -0700, Drew Jenkins wrote: Jerry McAllister wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. Which I did. Trust me. I've ruled everything else out. It's the HD. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, and do it remotely? Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. That I am not doing. There are two other disks in the box that are SCSIs. My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. You misread. The files were on the new HD. The action scripts, or s/w that calls those dbase files, are on the SCSI drives. That is a much bigger problem then. You can't just go and rebuild stuff and expect to keep the files on that disk. You might be able to used fdisk if the slice table got smuched and if you put back exactly what was originally there. You might even be able to use bsdlabel to fix a partition table, again if the new was exactly the same as the old, but I am not sure of that. You must not attempt to build filesystems on the disk with newfs or then all will be gone and beyond recovery except by those very expensive spy type folk that try to get secret information from overwritten storage. But, what you are describing is not a corrupt OS. It is a problem with reading information from a disk.I have responded to several different people lately on similar issues and can't remember which is which. If it is a bad space on disk, then you are going to have to reconstruct the date by reading as much as you can and putting it together the hard way. If it is some incompatibilty the file system versions between how it written and being read, you need to track down just how it was written and try to bridge the difference. jerry TIA, Drew - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, 16 Mar 2007, Drew Jenkins wrote: I believe you misunderstand. I have 3 disks: 2 are SCSI RAID and are 80 GB each 1 is not and is 500 GB I don't actually need the 500 GB now. I haven't even used up the 80 GB HD's. So I can wipe the 500 GB clean. I don't have to keep data on it at all. But...can I do that remotely, and run those commands remotely, with that disk being unmounted, and if so...how? The problem *is* a corrupt OS. I currently don't have any data on that 500 GB HD. And the problems persist. Sorry to have confused you. Are things clearer now? TIA, Drew2 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 09:12:02AM -0700, Drew Jenkins wrote: Jerry McAllister wrote: On Fri, Mar 16, 2007 at 07:16:33AM -0700, Drew Jenkins wrote: 2Kevin Kinsey wrote: synch your source to 6.2 How? And is this necessary since it's already at 6.2? The command below, cvsup -g -L 2 supfile. Assuming, of course, that the supfile is valid. Is it necessary? Depends; if you're convinced that something is wrong with your current installation, then you might not need to, because you can rebuild exactly the system that you *should* have (for example, perhaps you fat-fingered a chmod or rm call?). Can you finally learn to break you lines at about 70 characters in length. Having them run on long makes it much more difficult to make responses. Most Email clients allow you to configure it to break lines. If yours does not, just hit a a RETURN/ENTER about there each time. Yahoo's new beta must be the problem. Let's see if the old yahoo system works. Just switched back. Let me know. That I don't quite get. If you are just adding a disk to your machine, it is not likely to corript the rest of the system unless you execute something on that disk. Which I did. Trust me. I've ruled everything else out. It's the HD. When you fdisk, bsdlabel and newfs it, it is wiped and the previous contents are gone. If you precede that with a nice dd to overwrite initial sectors with zeros, then it is even more wiped before you even get to the fdisk. Can I bsdlabel, newfs and fdisk that disk without wiping the other disks, and do it remotely? Or are you trying to add this disk to a mirror in such a way that the raid controller thinks it is the good disk and the other is corrupt and tries to rebuild the mirror with the contents of the added disk? That you don't want to do. That I am not doing. There are two other disks in the box that are SCSIs. My thoughts are that something is happening that you haven't declared yet. An HD does not go out and zap files. That is like saying one book on a shelf skipped over and trashed the contents of another book on a shelf. You misread. The files were on the new HD. The action scripts, or s/w that calls those dbase files, are on the SCSI drives. That is a much bigger problem then. You can't just go and rebuild stuff and expect to keep the files on that disk. You might be able to used fdisk if the slice table got smuched and if you put back exactly what was originally there. You might even be able to use bsdlabel to fix a partition table, again if the new was exactly the same as the old, but I am not sure of that. You must not attempt to build filesystems on the disk with newfs or then all will be gone and beyond recovery except by those very expensive spy type folk that try to get secret information from overwritten storage. But, what you are describing is not a corrupt OS. It is a problem with reading information from a disk.I have responded to several different people lately on similar issues and can't remember which is which. If it is a bad space on disk, then you are going to have to reconstruct the date by reading as much as you can and putting it together the hard way. If it is some incompatibilty the file system versions between how it written and being read, you need to track down just how it was written and try to bridge the difference. jerry TIA, Drew As long as the disk isn't in use, yes you can do this type of thing anytime you like. So unless I'm missing the boat here, why in the world has this thread gone on so long if it was this trivial of an issue? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, Mar 16, 2007 at 01:33:42PM -0700, Drew Jenkins wrote: I believe you misunderstand. I have 3 disks: 2 are SCSI RAID and are 80 GB each 1 is not and is 500 GB I don't actually need the 500 GB now. I haven't even used up the 80 GB HD's. So I can wipe the 500 GB clean. I don't have to keep data on it at all. But...can I do that remotely, and run those commands remotely, with that disk being unmounted, and if so...how? You can do it remotely. Once everything on that disk is unmounted and unreferenced, then fdisk and bsdlabel will be happy to work on it. The best documentation for that is down in the examples of the bsdlabel man page. dd if=/dev/zero of=/dev/da0 bs=512 count=32 fdisk -BI da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 bsdlabel -w -B da0s1 bsdlabel -e da0s1 Change the device names to be what yours really are (da0 may be ad3 or something. I also upped the count on the dd, but it doesn't matter. Follow this with a newfs for each partition except swap that you create on this disk. The problem *is* a corrupt OS. I currently don't have any data on that 500 GB HD. And the problems persist. Sorry to have confused you. Are things clearer now? Well, it seems clear that there is no problem with the 500 GB disk. You can just fdisk it. If you want, write a few blocks of zeros to it first to make sure the system believes it clean if you want. Probably shouldn't need to, though. dd if=/dev/zero of=/dev/extra-drive-name bs=512 count=250 As for the corrupt OS, I don't understand what that is and why you think that or whatever. jerry TIA, Drew2 Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 09:12:02AM -0700, Drew Jenkins wrote: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
Thanks! That's great! Here's why the OS is corrupt: 1) Suddenly, large data files which were on the 500 GB HD were wiped. I hadn't been working in anything associated with them for some time before that. They just disappeared. This is exactly what happened before on the old server, but then I had done something to damage it (entered a bad command). 2) Now, as then, quirky things are happening, forcing me to do work-arounds when none should be done, or to abandon projects I'd like to do. For example, I copied a MySQL database as another dbase with another name, wiped all the data from the new dbase, and copied a shopping cart app I've built in Zope to a new site I'm building. I entered new categories into the new dbase. However, when I surf to my interface in the new Zope site I'm building, the old cats appear! There's no connection whatsoever. Even the background color of the display pages is picked up from the old site, goodness knows how. If I use the Zope interface to enter data into the products table, it works, but with the old cats. If I enter data into that table through MySQL, it displays in the new Zope site. I had to hard-wire the new cats to get it to work. I still don't know why the bgcolor for the page is the same as the old site, either. This kind of crap happens over and over again, and I have no explanation.2 Last time, it screwed up my clients' email, something I'm loathe to do. Eventually, the whole system died on me. TIA, Drew Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 01:33:42PM -0700, Drew Jenkins wrote: I believe you misunderstand. I have 3 disks: 2 are SCSI RAID and are 80 GB each 1 is not and is 500 GB I don't actually need the 500 GB now. I haven't even used up the 80 GB HD's. So I can wipe the 500 GB clean. I don't have to keep data on it at all. But...can I do that remotely, and run those commands remotely, with that disk being unmounted, and if so...how? You can do it remotely. Once everything on that disk is unmounted and unreferenced, then fdisk and bsdlabel will be happy to work on it. The best documentation for that is down in the examples of the bsdlabel man page. dd if=/dev/zero of=/dev/da0 bs=512 count=32 fdisk -BI da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 bsdlabel -w -B da0s1 bsdlabel -e da0s1 Change the device names to be what yours really are (da0 may be ad3 or something. I also upped the count on the dd, but it doesn't matter. Follow this with a newfs for each partition except swap that you create on this disk. The problem *is* a corrupt OS. I currently don't have any data on that 500 GB HD. And the problems persist. Sorry to have confused you. Are things clearer now? Well, it seems clear that there is no problem with the 500 GB disk. You can just fdisk it. If you want, write a few blocks of zeros to it first to make sure the system believes it clean if you want. Probably shouldn't need to, though. dd if=/dev/zero of=/dev/extra-drive-name bs=512 count=250 As for the corrupt OS, I don't understand what that is and why you think that or whatever. jerry TIA, Drew2 Jerry McAllister wrote: On Fri, Mar 16, 2007 at 09:12:02AM -0700, Drew Jenkins wrote: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] - Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Fri, 16 Mar 2007, Drew Jenkins wrote: Thanks! That's great! Here's why the OS is corrupt: 1) Suddenly, large data files which were on the 500 GB HD were wiped. I hadn't been working in anything associated with them for some time before that. They just disappeared. This is exactly what happened before on the old server, but then I had done something to damage it (entered a bad command). 2) Now, as then, quirky things are happening, forcing me to do work-arounds when none should be done, or to abandon projects I'd like to do. For example, I copied a MySQL database as another dbase with another name, wiped all the data from the new dbase, and copied a shopping cart app I've built in Zope to a new site I'm building. I entered new categories into the new dbase. However, when I surf to my interface in the new Zope site I'm building, the old cats appear! There's no connection whatsoever. Even the background color of the display pages is picked up from the old site, goodness knows how. If I use the Zope interface to enter data into the products table, it works, but with the old cats. If I enter data into that table through MySQL, it displays in the new Zope site. I had to hard-wire the new cats to get it to work. I still don't know why the bgcolor for the page is the same as the old site, either. This kind of crap happens over and over again, and I have no explanation.2 Last time, it screwed up my clients' email, something I'm loathe to do. Eventually, the whole system died on me. TIA, Drew Jerry McAllister [EMAIL PROTECTED] wrote: On Fri, Mar 16, 2007 at 01:33:42PM -0700, Drew Jenkins wrote: I believe you misunderstand. I have 3 disks: 2 are SCSI RAID and are 80 GB each 1 is not and is 500 GB I don't actually need the 500 GB now. I haven't even used up the 80 GB HD's. So I can wipe the 500 GB clean. I don't have to keep data on it at all. But...can I do that remotely, and run those commands remotely, with that disk being unmounted, and if so...how? You can do it remotely. Once everything on that disk is unmounted and unreferenced, then fdisk and bsdlabel will be happy to work on it. The best documentation for that is down in the examples of the bsdlabel man page. dd if=/dev/zero of=/dev/da0 bs=512 count=32 fdisk -BI da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 bsdlabel -w -B da0s1 bsdlabel -e da0s1 Change the device names to be what yours really are (da0 may be ad3 or something. I also upped the count on the dd, but it doesn't matter. Follow this with a newfs for each partition except swap that you create on this disk. The problem *is* a corrupt OS. I currently don't have any data on that 500 GB HD. And the problems persist. Sorry to have confused you. Are things clearer now? Well, it seems clear that there is no problem with the 500 GB disk. You can just fdisk it. If you want, write a few blocks of zeros to it first to make sure the system believes it clean if you want. Probably shouldn't need to, though. dd if=/dev/zero of=/dev/extra-drive-name bs=512 count=250 As for the corrupt OS, I don't understand what that is and why you think that or whatever. jerry TIA, Drew2 How large is large? Why filesystem are you using with what options? -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
23Hi; Is it possible to rebuild an OS without reformatting the hard drive? I have FBSD6.2, so I can't upgrade. upgrade to what? of course it's is possible to do this with any version. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew - Get your own web address. Have a HUGE year through Yahoo! Small Business. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
2How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. The MySQL was called from the Zope, of course. Then suddenly, poof! They were gone. Drew - Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Corrupted OS
On Mar 16, 2007, at 7:34 PM, Drew Jenkins wrote: How large is large? Why filesystem are you using with what options?The MySQL database was just under a gigabyte, and the Zope Data.fs file/database was somewhere under 2 gigabytes. Options? No options. I had symlinks from where these dbases were supposed to live on the SCSI drives to the 500 GB drive. Then suddenly, poof! They were gone. Drew Well, I was curious because I thought it could be something to deal with the 2GB file limit. You still haven't answered my question about the filesystem though: are you using UFS2 or something else? Thanks, -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
