Subject: Re: Installing NetBSD 2.0 - second harddisk affected?
To: Alex Pelts <email@example.com>
From: Pete Rushmere <firstname.lastname@example.org>
Date: 03/29/2005 20:23:08
Only ever seems to install on the first drive leaving all other
data intact, even on the TeraQube with 3 drives!
At 19:47 29/03/2005, Alex Pelts wrote:
>I do not believe second hard disk would be affected. Only first device is
>mentioned in the install scripts. I would assume it is pretty safe to
>leave second HD plugged in.
>As far as OS version goes, you can use 1.6.2 which has been very good to
>me. I do not experience any corruptions or lockups with any file size. Of
>course people reported increased performance with 2.0 but with data
>corruption it does not help much.
>Janko Knops wrote:
>>----- Original Message ----- From: "Carsten Pache" <email@example.com>
>>To: "port-cobalt" <firstname.lastname@example.org>
>>Sent: Tuesday, March 29, 2005 2:18 PM
>>Subject: Installing NetBSD 2.0 - second harddisk affected?
>>>As my Qube II crashed several times during file transfers via Samba (I
>>>upgraded NetBSD 1.6.1 to 2.0 but it seems I missed something special -
>>>file transfers using Samba froze my Qube II after transferring a few
>>>files - this never happened with NetBSD 1.6.1) and left the boot drive
>>>in an unusable state, I now want to install NetBSD 2.0 using the
>>>restore CD 2.0-1.
>>>My Qube II currently contains two disks. Will the second one be
>>>affected when NetBSD is installed using the restore CD? Or will the
>>>restore CD use only the first drive, leaving the second one in the
>>>state that it already is?
>>>Of course, I could disconnect the second drive during installation in
>>>order to be absolutely sure that only the first drive will be touched
>>>by the restore CD. But most of you know the procedure of opening and
>>>closing the Qube's housing (although it is not really difficult).
>>I don't know if your second harddisk would be affected, but the crashes
>>after using samba I've also experienced here.
>>I solved that by disabling dma, and now runs stable again. Maybe a
>>solution if you would need to backup the second hdd.