On 06/02/2023 00:11, Richmond wrote:
Max Nikulin writes:
On 05/02/2023 03:12, Richmond wrote:
The errors about sr0 come before the stuff about resume.
Does the following command generate similar errors (taken from initrd
scripts, UUID is intentionally not from the set of existing
partitions)
Max Nikulin writes:
> On 05/02/2023 03:12, Richmond wrote:
>> The errors about sr0 come before the stuff about resume.
>
> Does the following command generate similar errors (taken from initrd
> scripts, UUID is intentionally not from the set of existing
> partitions)?
>
> blkid -l -t UUID=11
On 05/02/2023 03:12, Richmond wrote:
The errors about sr0 come before the stuff about resume.
Does the following command generate similar errors (taken from initrd
scripts, UUID is intentionally not from the set of existing partitions)?
blkid -l -t UUID=---- -
Richmond wrote:
> David Wright writes:
>
>> On Sat 04 Feb 2023 at 17:38:25 (+), Richmond wrote:
>>> David Wright writes:
On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote:
> Max Nikulin writes:
>> On 03/02/2023 01:47, Richmond wrote:
>>> It might be a good way for someo
David Wright writes:
> On Sat 04 Feb 2023 at 17:38:25 (+), Richmond wrote:
>> David Wright writes:
>> > On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote:
>> >> Max Nikulin writes:
>> >> > On 03/02/2023 01:47, Richmond wrote:
>> >> >> It might be a good way for someone to reproduce the
On Sat 04 Feb 2023 at 17:38:25 (+), Richmond wrote:
> David Wright writes:
> > On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote:
> >> Max Nikulin writes:
> >> > On 03/02/2023 01:47, Richmond wrote:
> >> >> It might be a good way for someone to reproduce the error on some
> >> >> other
>
David Wright writes:
> On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote:
>> Max Nikulin writes:
>> > On 03/02/2023 01:47, Richmond wrote:
>> >> It might be a good way for someone to reproduce the error on some
>> >> other
>> >> machine. I have no problems with the CD/DVD writer and have us
Hi,
i wrote:
> > Maybe the script which runs blkid or alike has vanished during the recent
> > reconstruction of the initrd which fixed the problems ?
Richmond wrote:
> I didn't need to reconstruct initrd to cause the problems. As far as I
> remember all I did was destroy the swap space, having c
On Sat 04 Feb 2023 at 12:37:27 (+), Richmond wrote:
> Max Nikulin writes:
> > On 03/02/2023 01:47, Richmond wrote:
> >> It might be a good way for someone to reproduce the error on some
> >> other
> >> machine. I have no problems with the CD/DVD writer and have used it a
> >> few times recentl
Max Nikulin writes:
> On 03/02/2023 01:47, Richmond wrote:
>> It might be a good way for someone to reproduce the error on some
>> other
>> machine. I have no problems with the CD/DVD writer and have used it a
>> few times recently.
>
> Do you see the same errors if kernel command line is edited
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> /tmp/initrd21/scripts/local:[ "${quiet?}" != "y" ] && log_begin_msg
>> "Running /scripts/local-block"
>> [...]
>> local_block()
>> {
>>[ "${quiet?}" != "y" ] && log_begin_msg "Running /scripts/local-block"
>>run_scripts /s
Hi,
Richmond wrote:
> /tmp/initrd21/scripts/local:[ "${quiet?}" != "y" ] && log_begin_msg
> "Running /scripts/local-block"
> [...]
> local_block()
> {
>[ "${quiet?}" != "y" ] && log_begin_msg "Running /scripts/local-block"
>run_scripts /scripts/local-block "$@"
> [...]
> Then
On 03/02/2023 01:47, Richmond wrote:
It might be a good way for someone to reproduce the error on some other
machine. I have no problems with the CD/DVD writer and have used it a
few times recently.
Do you see the same errors if kernel command line is edited from grub to
pass non-existing UUI
sorry, replied to wrong list.
On Fri, 03 Feb 2023 16:55:18 -0500,
John Covici wrote:
>
> For instance I just got a post from Freedom Scientific which had the
> announcement in the Email and also link to the post.
> On Fri, 03 Feb 2023 15:28:55 -0500,
> David Wright wrote:
> >
> > On Fri 03 Feb 2
For instance I just got a post from Freedom Scientific which had the
announcement in the Email and also link to the post.
On Fri, 03 Feb 2023 15:28:55 -0500,
David Wright wrote:
>
> On Fri 03 Feb 2023 at 13:12:05 (+), Richmond wrote:
> > David Wright writes:
> > > On Thu 02 Feb 2023 at 21:58:
On Fri 03 Feb 2023 at 13:12:05 (+), Richmond wrote:
> David Wright writes:
> > On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote:
> >> "Thomas Schmitt" writes:
> >> >
> >> > (If not there, then in the /scripts/local-block directory of the initrd
> >> > ?)
> >>
> >> I don't know how I w
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> No local block. :-?
>
> Maybe you can find our from where the message comes:
>
> grep -r 'Running.*scripts.*local-block' /tmp/initrd21
>
>
grep -r 'Running.*scripts.*local-block' /tmp/initrd21
/tmp/initrd21/scripts/local:[ "${quiet?}"
Hi,
Richmond wrote:
> No local block. :-?
Maybe you can find our from where the message comes:
grep -r 'Running.*scripts.*local-block' /tmp/initrd21
Have a nice day :)
Thomas
David Wright writes:
> On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote:
>> "Thomas Schmitt" writes:
>> >
>> > (If not there, then in the /scripts/local-block directory of the initrd ?)
>>
>> I don't know how I would look in that. Is it in RAM at boot time?
>
>Choose your kernel ↓
Michel Verdier writes:
> Le 2 février 2023 Richmond a écrit :
>
>> There is no such file. Earlier I ran this:
>>
>> find / -print|grep "scripts/local-block"
>>
>> and it found nothing, which led me to believe it is some temporary file...
>>>
>>> (If not there, then in the /scripts/local-block dir
On Thu 02 Feb 2023 at 21:58:54 (+), Richmond wrote:
> "Thomas Schmitt" writes:
> >
> > (If not there, then in the /scripts/local-block directory of the initrd ?)
>
> I don't know how I would look in that. Is it in RAM at boot time?
Choose your kernel ↓↓Pick any name ↓↓
Le 2 février 2023 Richmond a écrit :
> There is no such file. Earlier I ran this:
>
> find / -print|grep "scripts/local-block"
>
> and it found nothing, which led me to believe it is some temporary file...
>>
>> (If not there, then in the /scripts/local-block directory of the initrd ?)
its part o
"Thomas Schmitt" writes:
> Indeed. But why should only the kernel be brain damaged ?
>
> (I expect some generic UUID searcher for block devices. Probably the sr
> devices are near the end of its iteration. So one would not see any
> protest in the log if the UUID is found on the device which is t
Hi,
Richmond wrote:
> Perhaps the system was looking for resume space on sr0?
That's my guess too. We already knew that the read address and block size
come from the kernel's brain damaged representation of a drive which has
not seen a medium since boot. My suspicion was that libblkid is involved
piorunz writes:
> On 02/02/2023 14:05, Richmond wrote:
>> After I did this, the errors went away.
>> I don't know why the errors reference sr0, it's a mystery.
>
> They will most likely come back, this error is related to optical
> drive, nothing to do with swap space.
Perhaps the system was loo
On 02/02/2023 14:05, Richmond wrote:
After I did this, the errors went away.
I don't know why the errors reference sr0, it's a mystery.
They will most likely come back, this error is related to optical drive,
nothing to do with swap space.
--
With kindest regards, Piotr.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ De
Richmond writes:
> It may be a coincidence but yesterday I installed some
> libguestfs-tools. Now I see errors when booting, which also appear in
> /var/log/messages:
>
> kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
> kernel:
Hi,
Thomas Amm wrote:
> First you might remove the pktcdvd module:
> Not sure if it causes this specific problem but it is for pre-
> growisofs CD-RW writing.
The packet writing device bundles smaller write requests in larger chunks
and ensures to write only at addresses and with sizes which are
On Mon, 2023-01-23 at 17:34 +, Richmond wrote:
> Sven Joachim writes:
>
> > On 2023-01-23 16:13 +, Richmond wrote:
> >
> > > I put a dvd in and mounted it. Then rebooted. I saw these
> > > messages:
> > >
> > > [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0
> > > [ 3.744658
Hi,
piorunz wrote:
> read attempts continue,
Obviously your drive groper is different from Richmond's. Both get lured
into their activities by the kernel bugs.
> Inserting blank disc on every reboot is not a solution in my opinion. And I
> didn't verified it myself,
It would be interesting to
On 25/01/2023 15:26, Thomas Schmitt wrote:
it might be that there are no further (periodic) read attempts.
If the messages only appear once during the boot procedure, then i think
the issue is explored as far as possible without starting kernel
programming.
Just to briefly comment on this - re
Hi,
Richmond wrote:
> VENDOR MODEL SIZE PHY-SEC LOG-SEC
> HL-DT-ST HL-DT-ST_DVDRAM_GH15F 204820482048
> It has stayed like this after I removed it.
Next question would be whether the error messages stopped after this.
But re-reading your initial post:
> > I see erro
Richmond writes:
> "Thomas Schmitt" writes:
>
>> Hi,
>>
>> i wrote:
>>> > If you have some blank optical medium, then try whether the emitter of
>>> > the read attempt can be discouraged if the drive is perceived as offering
>>> > just one block of 2048 bytes.
>>
>> Richmond wrote:
>>> I don't k
"Thomas Schmitt" writes:
> Hi,
>
> i wrote:
>> > If you have some blank optical medium, then try whether the emitter of
>> > the read attempt can be discouraged if the drive is perceived as offering
>> > just one block of 2048 bytes.
>
> Richmond wrote:
>> I don't know how to do that. Do you mean
Hi,
i wrote:
> > If you have some blank optical medium, then try whether the emitter of
> > the read attempt can be discouraged if the drive is perceived as offering
> > just one block of 2048 bytes.
Richmond wrote:
> I don't know how to do that. Do you mean make a DVD with 1 block of data?
Just
"Thomas Schmitt" writes:
> I assume that you will see the same result there.
lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr*
VENDOR MODEL SIZE PHY-SEC LOG-SEC
HL-DT-ST HL-DT-ST_DVDRAM_GH15F 1073741312 512 512
5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-
On 25/01/2023 10:38, Thomas Schmitt wrote:
Are users of Debian 10 (actually of kernel 4.19) here who are willing to
run
lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr*
directly after booting with empty drive tray ?
$ lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr*
VENDOR MODE
Hi,
i wrote:
> > Back in 2020 i would quite surely have noticed
> > if that behavior had been shown.
Richmond wrote:
> lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr*
> VENDOR MODELSIZE PHY-SEC LOG-SEC
> TSSTcorp TSSTcorp_DVD+_-RW_TS-L632H 1073741312 512
"Thomas Schmitt" writes:
>
> Are users of Debian 10 (actually of kernel 4.19) here who are willing to
> run
> lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr*
> directly after booting with empty drive tray ?
lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr*
VENDOR MODEL
Hi,
piorunz wrote:
> CD inserted:
> $ lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr0
> VENDOR MODEL SIZE PHY-SEC LOG-SEC
> hp hp_DVDRW_GUE1N 62765670420482048
> DVD inserted:
> $ lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SEC /dev/sr0
> VENDOR MODEL
On 24/01/2023 18:58, Thomas Schmitt wrote:
Hi,
the log messages about "unaligned transfer" would be explained if indeed
the block size of the drive would be mistaken as 512 bytes rather than
2048 bytes.
So it might be interesting to let lsblk report "sector" sizes as perceived
by the kernel:
Hi,
the log messages about "unaligned transfer" would be explained if indeed
the block size of the drive would be mistaken as 512 bytes rather than
2048 bytes.
So it might be interesting to let lsblk report "sector" sizes as perceived
by the kernel:
lsblk -b -o VENDOR,MODEL,SIZE,PHY-SEC,LOG-SE
Hi,
piorunz wrote:
> Today, kernel 5.10, Debian 11 Bullseye, and problem still exists :D
>
> $ lsblk -b -o VENDOR,MODEL,SIZE /dev/sr0
> VENDOR MODELSIZE
> hp hp_DVDRW_GUE1N 1073741312
Now that's a strange size: 1 GiB - 512 bytes.
The readable data capacity of an optical dr
On 23/01/2023 15:01, Thomas Schmitt wrote:
I wonder what might have caused this. But this line brings me to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948358
where pior...@gmail.com tried to get this processed as bug of udev.
No solution was found.
That would be me. Over three years
David Wright writes:
> On Mon 23 Jan 2023 at 13:34:50 (+), Richmond wrote:
>> It may be a coincidence but yesterday I installed some
>> libguestfs-tools. Now I see errors when booting, which also appear in
>> /var/log/messages:
>>
>> kernel: [ 9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result
On Mon 23 Jan 2023 at 13:34:50 (+), Richmond wrote:
> It may be a coincidence but yesterday I installed some
> libguestfs-tools. Now I see errors when booting, which also appear in
> /var/log/messages:
>
> kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result:
> hostbyte=DID_OK driver
Sven Joachim writes:
> On 2023-01-23 16:13 +, Richmond wrote:
>
>> I put a dvd in and mounted it. Then rebooted. I saw these messages:
>>
>> [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0
>> [3.744658] sr 3:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram
>> cd/rw xa/form2
Hi,
Richmond wrote:
> I put a dvd in and mounted it. Then rebooted. I saw these messages:
>
> [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0
> [3.744658] sr 3:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram
> cd/rw xa/form2 cdda tray
> [ 19.585098] pktcdvd: pktcdvd0: writer
On 2023-01-23 16:13 +, Richmond wrote:
> I put a dvd in and mounted it. Then rebooted. I saw these messages:
>
> [ 756.539018] pktcdvd: pktcdvd0: writer mapped to sr0
> [3.744658] sr 3:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram
> cd/rw xa/form2 cdda tray
> [ 19.585098] pkt
"Thomas Schmitt" writes:
> Hi,
>
> Richmond wrote:
>> kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result:
>> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
>> kernel: [9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready
>> [current]
>> kernel: [9.507146] sr 3:0:0:0:
Hi,
Richmond wrote:
> kernel: [9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
> kernel: [9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready
> [current]
> kernel: [9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not
Curt writes:
> On 2014-07-25, Sharon Kimble wrote:
>>
>> Every day the following appears in my logwatch email
>>=2D-8<---cut here---start->8---
>> WARNING: Kernel Errors Present
>> EXT4-fs (sde1): error count: 1 ...: 1 Time(s)
>> EXT4-fs (sde1): ini
On 2014-07-25, Sharon Kimble wrote:
>
> Every day the following appears in my logwatch email
>=2D-8<---cut here---start->8---
> WARNING: Kernel Errors Present
> EXT4-fs (sde1): error count: 1 ...: 1 Time(s)
> EXT4-fs (sde1): initial error at 139738147
On Tue, Aug 20, 2013 at 11:39:52AM +0200, François Patte wrote:
> Bonjour,
>
> In logwatch report, I have some kenel errors:
>
> 1-ACPI:
>
> ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF]
> (Node 88040e097ec0), AE_NOT_FOUND (20110623/psparse-536
>
> ACPI Error: [DSSP]
Hello,
On 20/08/13 11:39, François Patte wrote:
> Bonjour,
>
> In logwatch report, I have some kenel errors:
>
> 1-ACPI:
>
> ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF]
> (Node 88040e097ec0), AE_NOT_FOUND (20110623/psparse-536
>
> ACPI Error: [DSSP] Namespace look
Joel Konkle-Parker wrote:
I just compiled a fresh 2.2.20 kernel and rebooted into it for the first
time. During the boot, the kernel went into an endless cycle of the same
error message, something to the effect of "cannot modprobe
binfmt###c; error=8". That's from memory, so I forget
what th
On Tue, Mar 04, 2003 at 09:41:52PM -0500, Joel Konkle-Parker wrote:
> During the boot, the kernel went into an endless cycle of the same
> error message, something to the effect of "cannot modprobe
> binfmt###c; error=8".
Gee, turn off ELF, or something?
> Did I set a configuration setting w
On Tue, Mar 04, 2003 at 09:41:52PM -0500, Joel Konkle-Parker wrote:
> I just compiled a fresh 2.2.20 kernel and rebooted into it for the first
> time. During the boot, the kernel went into an endless cycle of the same
> error message, something to the effect of "cannot modprobe
> binfmt###c;
Marlon Urias writes:
> ANYWAYS after dialing up and installing some packages via apt PPP my
> dialup STOPPED working.
What packages did you install?
> This time the errors showed up in /var/log/messages so I've appended them
> to the end of this email incase anybody can help.
Can't tell much fro
59 matches
Mail list logo
