Package: zoneminder
Version: 1.35.5~20200707.77-buster
Severity: critical
Since a recent upgrade, we found the following message in the log
repeatedly:
Jul 12 07:59:12 felix zma_m6[19229]: ERR [zma_m6] [Got empty memory map file
size 0, is the zmc process for this monitor running?]
... and thi
ael wrote:
> A.E.Lawrence wrote:
>> # fdrawcmd read 0 0 0 1 2 18 1 1 length=18432 >/dev/null
>> remaining= 17920
>> 0: 40 <== So this is "Abnormal termination"?
>> 1: 20 <== CRC error? (id or data)
>> 2: 20 <== CRC error? (data)
>
> Did I decode them correctly?
>
> ael
Yes, that's correc
A.E.Lawrence wrote:
> Alain Knaff wrote:
>> ael wrote:
>>> Is that what you wanted?
>>>
>>> ael
>> Yes. All sectors are there, ... so I wonder why you are getting errors.
>>
>>
>> So, next round of tests: trying to read these sectors:
>
ael wrote:
>
> Is that what you wanted?
>
> ael
Yes. All sectors are there, ... so I wonder why you are getting errors.
So, next round of tests: trying to read these sectors:
fdrawcmd recalibrate 0
fdrawcmd read 0 0 0 1 2 18 1 1 length=18432 >/dev/null
Alain
--
To UNSUBSCRIBE, email t
ael wrote:
> Alain Knaff wrote:
> > Could you try the same with a "higher" repetition count:
>
> On same floppy (medium) as before:
[...]
All sector ids seem to be present (although occasionally they are
skipped during read...), and track is correct everywhere... bu
ael wrote:
> Mark Hounschell wrote:
>> On 12/15/2009 10:08 AM, Alain Knaff wrote:
>
>> I mentioned I had multiple machines with this problem. Some running
>> different versions of SuSE. Mainly 11.0, which is where all the info
>> I've provided came from thus far
On 15/12/09 15:59, ael wrote:
> For what it is worth, here are the results from my debian testing box
> under 2.6.32_exact-55846-gf405425
>
> $ lsmod |grep floppy
> floppy 45327 0
>
> # setfdprm /dev/fd0 HD
> # fdformat /dev/fd0
> Double-sided, 80 tracks, 18 sec/track. Total capa
On 14/12/09 16:24, ael wrote:
> Alain Knaff wrote:
>> On 14/12/09 15:58, ael wrote:
>>> Any point in running under strace?
>>
>> Yes, this would be useful, especially for analyzing the "Invalid
>> argument"
>> issue.
>
> Looks as if th
On 14/12/09 15:58, ael wrote:
> Any point in running under strace?
Yes, this would be useful, especially for analyzing the "Invalid argument"
issue.
Regards,
Alain
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...
On 14/12/09 12:27, ael wrote:
> # getfdprm -o /dev/fd0u1440
> 2880 18 2 80 0 0x1b 0x00 0xcf 0x6c
>
> # fdrawcmd drive=/dev/fd0u1440 readid 0 repeat=18
> raw cmd: Invalid argument
... and if you try with /dev/fd0 instead?
Alain
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.o
On 03/12/09 16:28, ael wrote:
>
>> I tested both fdformat and superformat (from fdutils 5.5-20060227-3,
>> and then also from 20081027) with kernel 2.6.32-rc6 and on Kubuntu
>> 9.04, and both worked fine. Could it be a bad drive or a bad disk?
>
> No. I have used several known good discs and on
On 10/11/09 17:42, ael wrote:
> I tried setting the density to dd instead of hd -- something that I
> had also tried on fdformat without success. gfloppy managed to
This is indeed very useful information, sorry to have not spotted this
earlier. Double density disks cannot be formatted as high den
On 14/10/09 05:27, Aníbal Monsalve Salazar wrote:
> Sending this bug report to alain @ linux.lu
>
> You can see the discussion about this bug at:
>
> http://bugs.debian.org/548434
I tested both fdformat and superformat (from fdutils 5.5-20060227-3, and
then also from 20081027) with kernel 2.6.3
13 matches
Mail list logo
