I just had to do that a few days ago, but it didn't work. Apparently
DOS is very stupid, and without dding the entire DOS partition it
wouldn't work. Who knows why. Low-levels are a bad idea. I know
someone who managed to ruin a number of disks trying that.
Laurence
Matthew Dillon wrote:
>
Forrest Aldrich wrote:
>
> Is not sysinstall built and installed with a typical make
> buildworld/installworld?
No.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
One Unix to rule them all, One Resolver to find them,
One
On 23-Mar-00 Mike Smith wrote:
> Just rebuild sysinstall, like I told you to start with. Or just bring
> the disks up by hand, which is much faster. Or even try Warner's
> 'diskprep' tool.
If anyone want diskprep, its at...
http://people.freebsd.org/~imp/diskprep
---
Daniel O'Connor sof
> Is not sysinstall built and installed with a typical make
> buildworld/installworld?
As I told you in my original reply, _NO_.
> Anyways, I rebuilt it and it works now. Sysinstall was the culprit.
"I told you so".
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tel
Is not sysinstall built and installed with a typical make
buildworld/installworld?
Anyways, I rebuilt it and it works now. Sysinstall was the culprit.
_F
At 10:08 AM 3/23/00 -0800, Mike Smith wrote:
> > I tend to think there is something wrong with sysinstall... obviously, the
> > OS works
:I normally wouldn't recommend it. But the same situation with a different (not to be
:mentioned) OS happened to me.
:After hours of being frustrated, I decided the scsi controller went south. A
:cow-orker told me to LL the drive,
:and voila, magic. These were IBM LVD 10kRPM drives, brand spank
> I tend to think there is something wrong with sysinstall... obviously, the
> OS works as the internal drives (also LVD 10KRPM drives) work. Sysinstall
> just tells me there aren't any disks in the system.
>
> So, hope whomever maintains sysinstall is monitoring this conversation.
Sysinsta
I say again, DO NOT low-level format the drive. The _only_ situation
where it's worth taking this risk is when you're seeing errors from the
drive itself specifically referring to formatting issues; eg. 'address
mark not found'. There are no other circumstances which justify this
action, an
I tend to think there is something wrong with sysinstall... obviously, the
OS works as the internal drives (also LVD 10KRPM drives) work. Sysinstall
just tells me there aren't any disks in the system.
So, hope whomever maintains sysinstall is monitoring this conversation.
I will attempt ano
I normally wouldn't recommend it. But the same situation with a different (not to be
mentioned) OS happened to me.
After hours of being frustrated, I decided the scsi controller went south. A cow-orker
told me to LL the drive,
and voila, magic. These were IBM LVD 10kRPM drives, brand spankin new
:
:> Why not? The drives are empty LVD Drives, nothing bad'll happen.
:
:Apart from screwing up the factory format.
:
:> I mean, it may very well be sysinstall being massively out of sync, but it
:shouldn't hurt to LL the drives.
:
:It should, and will.
:
:--
:\\ Give a man a fish, and you feed
> Why not? The drives are empty LVD Drives, nothing bad'll happen.
Apart from screwing up the factory format.
> I mean, it may very well be sysinstall being massively out of sync, but it shouldn't
>hurt to LL the drives.
It should, and will.
--
\\ Give a man a fish, and you feed him for a da
Why not? The drives are empty LVD Drives, nothing bad'll happen.
I mean, it may very well be sysinstall being massively out of sync, but it shouldn't
hurt to LL the drives.
-eric
Mike Smith wrote:
> > Try low-levelling the drives. The behavior sounds similar to what I had a long
>time ago, l
> Try low-levelling the drives. The behavior sounds similar to what I had a long time
>ago, low level formatting them fixed the problem.
Not a good idea. Sounds more like sysinstall is massively out of sync
with the rest of the system; it's not updated with the rest of the world.
>
> -eric
>
Yep.
-eric
Forrest Aldrich wrote:
> Interesting point... these ARE new drives that were put in today.
>
> I presume you mean to use the BIOS scsi utility?
>
> _F
>
> At 06:16 PM 3/22/00 -0800, Eric Sabban wrote:
> >Try low-levelling the drives. The behavior sounds similar to what I had a
> >lon
Interesting point... these ARE new drives that were put in today.
I presume you mean to use the BIOS scsi utility?
_F
At 06:16 PM 3/22/00 -0800, Eric Sabban wrote:
>Try low-levelling the drives. The behavior sounds similar to what I had a
>long time ago, low level formatting them fixed the pr
Try low-levelling the drives. The behavior sounds similar to what I had a long time
ago, low level formatting them fixed the problem.
-eric
Forrest Aldrich wrote:
> Since this is a fairly current issue, I'm posting this appropriately.
>
> I have a DELL server that has hooked up to it a PowerVa
At 2:50 PM -0500 2000/3/22, Forrest Aldrich wrote:
> da4 at ahc0 bus 0 target 1 lun 0
> da4: Fixed Direct Access SCSI-3 device
> da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged
>Queueing Enabled
> da4: 34732MB (71132998 512 byte sectors: 255H 63S/T 4427C)
This just
Sorry:
da4 at ahc0 bus 0 target 1 lun 0
da4: Fixed Direct Access SCSI-3 device
da4: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da4: 34732MB (71132998 512 byte sectors: 255H 63S/T 4427C)
_F
At 02:47 PM 3/22/00 -0500, Bill Fumerola wrote:
>On Wed, Mar 22, 2000
On Wed, Mar 22, 2000 at 02:42:44PM -0500, Forrest Aldrich wrote:
> Since this is a fairly current issue, I'm posting this appropriately.
>
> I have a DELL server that has hooked up to it a PowerVault, with 8 36gb
> 10krpm LVD drives. The system has recognized these previously and dmesg
> sho
Since this is a fairly current issue, I'm posting this appropriately.
I have a DELL server that has hooked up to it a PowerVault, with 8 36gb 10krpm LVD
drives. The system has recognized these previously and dmesg shows them present;
however, /stand/sysinstall says that I don't have ANY disks
21 matches
Mail list logo
