You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   176-200 
 201-225   226-250   251-275   276-300   301-325   326-350   351-375   376-400   401-425 
 426-450   451-475   476-500   501-525   526-547      
 
Author Message
25 new of 547 responses total.
gull
response 201 of 547: Mark Unseen   May 9 12:59 UTC 2003

If Leeron doesn't have one, try www.atozcables.com.  That's where I got
mine last time I needed one.  They have them for either $20 or $28 each,
depending on whether or not you need one with termination.
aruba
response 202 of 547: Mark Unseen   May 9 14:29 UTC 2003

Thanks David.  Leeron says he can order some adapters for us, for about
$10 each, but they will take 7-10 days.  I understand the difference
between the cables now - the 80-pin cable (which our drive wants) includes
not only the data interface, but also power and SCSI ID setting.  (The
SCSI ID is set by the adapter via software, instead of being a jumper
setting right on the drive.)

These Seagate drives come in two versions, one with an 80-pin connection
and one with a 68-pin connection (plus power connection and SCSI ID jumper
block).  At the moment, I'm inclined to send back what we have and get the
68-pin version, so that our drives are compatible with our interface card.
Getting adapters for all the drives seems like a hack, and will make the
inside of the case more complicated than it needs to be.  (Here's a
picture of an adapter; it's got a little circuit board:
http://www.mycableshop.com/popups/SCA806850.htm)  Plus, we'd need two
types of cables. 

Unless, that is, there's an important advantage to having 80-pin drives.
dang
response 203 of 547: Mark Unseen   May 9 15:55 UTC 2003

I'd vote for sending them back and getting the correct drives. I've used the adaptors, and they're usually fairly shoddy (although they *do* work). I have a free 68-pin SCSI drive that I can temprorarily donate for testing/burn-in purposes, so that this doesn't waste any time for us.
aruba
response 204 of 547: Mark Unseen   May 9 18:01 UTC 2003

OK, I called NewEgg and got an RMA number to send back the 80-pin drive.  It
was going to be a pain to re-order the right drive from them, so I called
Leeron and told him to send back the two he just got for us, and in their
place get us 3 with the correct connectors.  This will cost us about $17
more per drive than going through NewEgg, but Leeron is a lot faster and
more accomodating. :)
scg
response 205 of 547: Mark Unseen   May 10 19:42 UTC 2003

The general rule with non-obvious changes and warranties is that you void the
warranty if you tell them you made the change.
aruba
response 206 of 547: Mark Unseen   May 10 23:25 UTC 2003

I turned off NextGrex last night because some big thunderstorms were
approaching Ann Arbor, and I don't have a UPS.  It had been up for over 5
days, running the memory test, with no errors.

We'll put the IDE disk in tomorrow, and test the SCSI controller with a disk
of dang's.
gull
response 207 of 547: Mark Unseen   May 12 12:52 UTC 2003

Sounds like the right decision, disk-wise.  SCA connectors seem to be 
mostly made for plugging hotswappable drives into backplanes.  Any other 
use of them is kind of a hack.
scott
response 208 of 547: Mark Unseen   May 12 13:50 UTC 2003

Ditto.  Much better to fix it now than to forever curse the adapters.
aruba
response 209 of 547: Mark Unseen   May 13 04:34 UTC 2003

I put the IDE disk in yesterday, and installed Windows 98 on it in order to
test out our hardware.  (Don't panic, it's only temporary.)  I had to hack
system.ini because Windows gets confused by how much memory we have, but now
everything seems fine.  I installed a driver for the ethernet chip on our
motherboard, connected the computer to the LAN in my house, and created an
internet connection through the router in the basement, and voila, here I am
talking to OldGrex from NextGrex.  Everything looks good.
polytarp
response 210 of 547: Mark Unseen   May 13 04:46 UTC 2003

WE SHOUYLD HAVE OLDGRAX USEABLE EVEN AFTER NEWGREx, YOu're saying?
janc
response 211 of 547: Mark Unseen   May 13 13:22 UTC 2003

We, I guess.  No parts from old grex will be used in newgrex.  However, I
can't, off hand, think of any use for old grex, and don't think we have any
plans to keep it running.
other
response 212 of 547: Mark Unseen   May 13 13:30 UTC 2003

And, before anyone asks, once the user partitions are successfully copied to
nextgrex, the disks will be destroyed to insure the privacy of Grex's users.

As far as I'm concerned, anyone willing to cart away the current machine after
the new machine takes over (with appropriate transition period) is welcome
to it.  (Minus the user disks, of course.)
janc
response 213 of 547: Mark Unseen   May 13 13:40 UTC 2003

I can't imagine why we'd destroy the disks, and I can't imagine Marcus
and STeve agreeing that we don't need the old Grex anymore.
gelinas
response 214 of 547: Mark Unseen   May 13 13:48 UTC 2003

Sufficiently sophisticated disk-recovery tools can do some amazing things.
The only way to ensure these tools don't work is physical destruction of the
disks.  I can see an argument that nothing on grex should be that sensitive,
but we aren't talking about *my* data on grex.  As long as we retain physical
possession, there is no need to destroy the disks.
cross
response 215 of 547: Mark Unseen   May 13 14:13 UTC 2003

I can't imagine anyone being that interested in grex's user disks,
despite what some folks think.  I'd say scrub them and give them
away.
scott
response 216 of 547: Mark Unseen   May 13 14:39 UTC 2003

I can't imagine there being any real value in the old Grex hardware.
keesan
response 217 of 547: Mark Unseen   May 13 15:26 UTC 2003

What is it that is supposed to be kept private, the passwords?
scott
response 218 of 547: Mark Unseen   May 13 16:00 UTC 2003

Files in home directory, email, staff conference.
drew
response 219 of 547: Mark Unseen   May 13 18:24 UTC 2003

If you can get good enough random numbers, it might suffice to do a
dd if=/dev/random of=/dev/sdx.
hal9
response 220 of 547: Mark Unseen   May 13 20:25 UTC 2003

`shred' (a GNU coreutils software) announces that it can prevent
recovery of erased data by writing sucessively several different
bit patterns over the files.  More details on the paper "Secure
Deletion of Data from Magnetic and Solid-State Memory", by Peter
Gutmann.  (http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html).

The only drawback is that, since it overwrits the disk several times,
it is extremely slow.  But, after the transition, I don't think time
will be a problem for oldgrex.

Also note that nothing is 100% effective, of course.  Physical destruction
is the only guaranteed way of safeguarding the disk contents.  shred's
info page goes to the extreme of telling that the /only/ 100% way is
melting the disk on *-acid.
other
response 221 of 547: Mark Unseen   May 13 22:26 UTC 2003

Why the heck would we KEEP the current Grex one we complete the migration 
to the next Grex?

Do we still need the first Grex?  Or the second?  So why not give it away 
to someone else who might actually put it to use?  Including Marcus or 
STeve, if they want to take it away.

And, if we're not going to use the current disks on the new system, then 
why should we keep them?  And if we're not going to keep them, then we 
damn well ought to destroy them because it is the only way to absolutely 
insure that their contents are unrecoverable.

I don't think my comment was radical, and I DO think it was logically 
sound and consistent with both our past practices and our current 
philosophies.
keesan
response 222 of 547: Mark Unseen   May 13 22:45 UTC 2003

Can't you simply overwrite the entire disk with 0's?
other
response 223 of 547: Mark Unseen   May 13 23:08 UTC 2003

There are a lot of levels of sophistication of data recovery tools 
available, and I don't know how available products of any particular 
level are, but it is quite possible that no reasonable amount of 
overwriting with 1s, 0s and/or random ASCII values would entirely 
obliterate and render irretrievable someone's personal data on these 
disks.

styles
response 224 of 547: Mark Unseen   May 13 23:11 UTC 2003

/dev/zero is your friend.
dd if=/dev/zero of=/dev/whatever bs=8192 (blocksize on grex is probably lower)

there may be some concern about the disks being magnetic and the zero's not
doing enough.
gelinas
response 225 of 547: Mark Unseen   May 14 00:34 UTC 2003

(The question is not, "Who would be interested in the data on the disks?" 
The question is, "Who would be interested in _their_ data on the disks being
released or revealed?"  We've too many users to get ALL of them to answer that
question negatively.)
 0-24   25-49   50-74   75-99   100-124   125-149   150-174   175-199   176-200 
 201-225   226-250   251-275   276-300   301-325   326-350   351-375   376-400   401-425 
 426-450   451-475   476-500   501-525   526-547      
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss