Does FreeBSD damage hardware?

Does FreeBSD damage hardware?

Post by Jeffrey M. Metcal » Fri, 28 Feb 1997 04:00:00



Hello,

I am concerned with a strange sound coming from one of my hard drives when using
FreeBSD-2.1.5.  Here is a brief background description.

I have two Maxtor IDE hard drives on the wd0 controller.  Both the Master and Slave
drives are set with dual partitions, DOS/Win95 and FreeBSD.  The beginning portions
of each drive are dedicated to DOS/FreeBSD and the later sectors are
dedicated to FreeBSD.  The FreeBSD operating system that I use actually
resides on disk wd0, and a large root partition (obtained through the sysinstall
facility of the FreeBSD on wd0) resides on disk wd1.  The reason I have this
setup as opposed to one OS per drive is that I want the wd1 drive to act as a
backup for both opperating systems.  I have had to reinstall FreeBSD too many times
from floppies, due to corruption problems with msdosfs, to not have fast backups
available.  I have no SCSI controllers that support tape drives and I am told that
floppy tape drive support is slow and is not very reliable under FreeBSD.
Hence the best backup solution for me for both DOS and Win95 was to have two
independent drives with DOS and FreeBSD; one primary (wd0), and one backup (wd1).

Here's the problem.  From FreeBSD, I mount my wd1 drive to perform backup storage
operations:

mount -rw -t ufs /dev/wd1s2 /mnt

Again, the second drive, wd1 has a single large root partition (/dev/wd1s2a and
nothing else) starting from a sector somewhere in the middle of the drive, and
ending at the last sector of the drive.

I periodically hear a relatively loud and unhealthy sounding click (or it may be described
as a scratch) coming from the drive.  This sound does not occur on the primary hard drive
on wd1 where I normally would run FreeBSD.  It does not occur when accessing the DOS
partition on wd1s1 from the Win95 operating system on wd0s1.  The sound only occurs when I
mount wd1s2 and perform backup operations from the FreeBSD on wd0d2.  I had previously had a
refurbished hard drive containing the
/dev/wd1s2 partition, but it died very quicky (fortunately for me within the short warranty
period).  That drive made the same scratching noises I hear now.  The latest hard drive I have
has lasted quite some time like this, but the sound is disconcerting.  Any thoughts?

Thanks So Much,

J. Metcalf  

PS.  I thought that maybe switching the order of the FreeBSD residence on the wd1 hard drive
might help.  In other words, install the FreeBSD portion at the beginning of the drive , and
the DOS portion at the end.  Would this be a waste of time with respect to this problem?

 
 
 

Does FreeBSD damage hardware?

Post by J Wuns » Sun, 02 Mar 1997 04:00:00



Quote:> I periodically hear a relatively loud and unhealthy sounding click
> (or it may be described as a scratch) coming from the drive.  This
> sound does not occur on the primary hard drive on wd1 where I
> normally would run FreeBSD.

That's definately a bad sound.  I've also heard it from SCSI drives
(no, they didn't run FreeBSD but HP-UX :), and they were simply dead
afterwards.

Quote:>   I had previously had a
> refurbished hard drive containing the /dev/wd1s2 partition, but it
> died very quicky (fortunately for me within the short warranty
> period).  That drive made the same scratching noises I hear now.

Maybe your controller misbehaves?  Cabling problem?  OTOH, these
drives are `intelligent' enough to catch out-of-bound accesses etc.,
so it's hard to imagine either.

One thing that comes to mind: noisy powersupplies aren't something
unusual in the PC world.  For sure, they can disturb almost any kind
of hardware.

--
cheers, J"org


Never trust an operating system you don't have sources for. ;-)

 
 
 

1. How to reset damaged colormap (damaged by netscape -install)

Since I'm stupid, I decided to try out NS 4.0b2.
Also, since I have an 8bit display, I launch NS with the -install option,
which makes it take a private colormap.

However, the damn thing dies often and from time to time, if it dies while I
have focus  on it, X  doesn't restore my "normal"  colormap (the one  I have
when I move my mouse away from NS).

My current colors are green on  yellow, and other nice things like that. The
easy way to fix  this is to exit X and start over,  but I can't currently do
that because of active sessions I have and that I can't kill easily.

1) Can I reset the colormap to a "sane" state?
2) Am I screwed, but is there a way to same my "sane" colormap so that I can
   restore it if the same problem happens again??

Thanks a bunch,
Marc

PS: CC me a copy (I read this group, but not as often as Email, and the
sooner I get back to normal colors, the better for my eyes :-D)
--
Home page: http://www.efrei.fr/~merlin/ (browser friendly)

2. Redirecting requests

3. Installing X -> hardware damage - any advice?

4. HP Omnibook 4150b (AtiRage Mobility) which FB-Device

5. Fonts Degrading/Possible Hardware Damage? (SONY Monitor)

6. HELP! Gateway 2000 w/ Utra ATA <-> RH 5.0

7. Software Causing Hardware Damage??

8. Partition settings Suggestions???

9. Can linux damage my hardware?

10. Linux damaging hardware through kernel patch????

11. dev drivers & hardware damage?

12. Damaged my dos partition. HELP!!!!!

13. what damage will be caused by accidentally doing this