Hello list,
I am having problems with my server, this box has been running OBSD
for the last 3/4 years without problems. A few months ago the box
begun to experience lockups once time at week during peak hours, now
the lockup is several times a week.
The last messages in the system logs are "/bs
Bob Beck wrote:
I am having problems with my server, this box has been running OBSD
for the last 3/4 years without problems. A few months ago the box
begun to experience lockups once time at week during peak hours, now
the lockup is several times a week.
The last messages in the system logs are
Darren Tucker wrote:
> If you have a logged-in shell you can do "exec ps -auwx" which won't
require a new process table slot. It replaces the shell so you'll be
effectively logged out after the ps completes, but hopefully with better
information :-)
"exec ps -auwx" doesn't helps here because
Hello,
I'm trying to install OpenBSD in three servers with
identical hardware and I was able to install it in two
of them but not in the third.
Each server detects a diferent geometry for the SCSI
disks :-?
server1 -> geometry: 817199/87/1 [71096313 Sectors]
server2 -> geometry: 2843852/25/1
K WESTERBACK wrote:
> --- "Josi M. Fandiqo" <[EMAIL PROTECTED]> wrote:
> > I'm trying to install OpenBSD in three servers with
> > identical hardware and I was able to install it in
> > two
> > of them but not in the third.
> >
> > Each server detects a diferent geometry for the SCSI
> > disks :-
Otto Moerbeek wrote:
> On Wed, 29 Jun 2005, [iso-8859-15] Josi M. [iso-8859-15] Fandiqo wrote:
> > I'm trying to install OpenBSD in three servers with
> > identical hardware and I was able to install it in two
> > of them but not in the third.
> >
> > Each server detects a diferent geometry for th
Nick Holland wrote:
> >> Each server detects a diferent geometry for the SCSI
> >> disks :-?
> >>
> >> server1 -> geometry: 817199/87/1 [71096313 Sectors]
> >> server2 -> geometry: 2843852/25/1 [71096300 Sectors]
> >> server3 -> geometry: 4425/255/63 [71087625 Sectors]
> >> dmesg, fdisk and disk
Marco Peereboom wrote:
>
> Are you sure you wiped all RAID meta data of the disks?
> Did you reuse a disk that was part of a RAID set by any chance?
> Go to the card BIOS and wipe all RAID sets; that might just fix your
> problem.
the raid was reconstructed with the vendor utilities and finally
I
more on this issue.
K WESTERBACK wrote:
> sd0: 34715MB, 34715 cyl, 16 head, 128 sec, 512
> bytes/sec, 71096320 sec total
> sd0: 34715MB, 34715 cyl, 16 head, 128 sec, 512
> bytes/sec, 71096320 sec total
> sd0: 34715MB, 34715 cyl, 16 head, 128 sec, 512
> bytes/sec, 71096320 sec total
>
> sd1: 34715
Hello list,
I'm in a situation where I must configure a couple of soekris boxes (net4801)
with very minimal services (pf and syslogd sending all logs to a remote
server), they will be unattended and various thousands of kilometers away.
Also the system is probable to suffer electrical failures
> Also the system is probable to suffer electrical failures and since OBSD
> is contained in a CF card I become very interested in running it over an
> unique read-only partition.
>
> The first option was add the "ro" flag to the fstab file, but it's ignored
> and the system leaves the root fs in
11 matches
Mail list logo
