dn't that be
> >
> > smartd_enable="YES"
> >
> > conforming to the syntax of other service start commands?
> > At least that might be the reason why smartd doesn't
> > automatically start. Sadly I can't find a reference to
> > how to edit rc.
S"
>
> conforming to the syntax of other service start commands?
> At least that might be the reason why smartd doesn't
> automatically start. Sadly I can't find a reference to
> how to edit rc.conf in "man smartd"; at least the manual
>
tax of other service start commands?
> At least that might be the reason why smartd doesn't
> automatically start. Sadly I can't find a reference to
> how to edit rc.conf in "man smartd"; at least the manual
> explains the options well... ;-)
This is correct, as per:
that might be the reason why smartd doesn't
automatically start. Sadly I can't find a reference to
how to edit rc.conf in "man smartd"; at least the manual
explains the options well... ;-)
--
Polytropon
Magdeburg, Germany
Happ
Hi!
I installed smartmontools, "start_smartd=yes" I have in rc.conf and I edited
/usr/local/etc/smart.conf where I have:
/dev/ada0 -a -d auto -o on -S on -s (S/../.././02|L/../../6/03) -m root
When I use top there are no smartd and if I run smartd again than top shows me
smartd for f
--On 13 November 2012 11:14 -0600 Dan Nelson
wrote:
Can anyone think of a 'simple' fix for this? - Is there anything I can do
to '/usr/local/etc/rc.d/smartd' to make it run later in the startup
process?
Try adding "mail" to the REQUIRE: line, since sendmail
In the last episode (Nov 13), Karl Pielorz said:
> I've noticed on our systems (9.0-Stable, amd64) that starting smartd at
> boot time massively extends the startup time of the box.
>
> I think I've traced this down to smartd, and our use of the '-M test'
>
Hi,
I've noticed on our systems (9.0-Stable, amd64) that starting smartd at
boot time massively extends the startup time of the box.
I think I've traced this down to smartd, and our use of the '-M test'
config option (which sends a test message, apparently forking to &
slave UDMA100
I ended up with a mountroot command prompt. After fiddling around, I
finally was able to change the boot order so that it boots from
/dev/ad2s1. I also had to edit the /etc/fstab. After rebooting, I was
able to boot up the system successfully except that I now received an
error mes
I'm seeing these sorts of messages in syslog output
Mar 12 15:06:10 app3 smartd[519]: Device: /dev/ad4, 6 Currently unreadable
(pending) sectors
Mar 12 15:06:10 app3 smartd[519]: Device: /dev/ad4, 6 Offline uncorrectable
sectors
Mar 12 15:29:39 app3 kernel: ad4: FAILURE - READ_DMA stat
Uwe Laverenz schrieb:
On Sat, Jun 21, 2008 at 01:38:25PM +1200, Steven Samuel Cole wrote:
Also, the disks are SATA300, the controller supports SATA150 only; there
is a jumper on the disks that limits them to SATA150 which I removed.
Could that be relevant ?
Yes, it could be relevant. Several
On Sat, Jun 21, 2008 at 01:38:25PM +1200, Steven Samuel Cole wrote:
> Also, the disks are SATA300, the controller supports SATA150 only; there
> is a jumper on the disks that limits them to SATA150 which I removed.
> Could that be relevant ?
Yes, it could be relevant. Several controllers have s
Hello,
I see an error message every time I boot my AMD64 FreeBSD 7.0 system or
when I restart smartd. These are the dmesg lines that seem relevant to
the issue (shortened for clarity):
kernel: FreeBSD 7.0-RELEASE #0: Fri Jun 6 22:06:44 NZST 2008
kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core
Hello.
I recently enabled smartd on a 5.4 SCSI-only box, and since then I'm
getting the following messages. Everything seems to work right, but I'd
like to understand if these are warnings, whether they should be taken
seriously, etc...
They seem to come in half-hour steps (i.e., in
14 matches
Mail list logo
