Marco Möller wrote:
> Often during boot, not always though, and never after KDE Plasma already
> began to start, I observe a kernel panic. The system is Debian stable
> "bookworm", but using kernel 6.12.12 from backports. I know, this is not
> the officially recommended way to use Debian stable.
On 2025-02-27 15:59, Gary Dale wrote:
On 2025-02-14 22:00, Michael Stone wrote:
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
All 3 systems have the linux-image-amd64 metapackage installed.
What does apt show -a linux-image-amd64 | grep -e Version -e Sources
-e Depends
return o
> > > On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
> > > > All 3 systems have the linux-image-amd64 metapackage installed.
On Sat 15 Mar 2025 at 10:44:40 (-0400), Gary Dale wrote:
> After today's upgrades, I note that RM1 showed these autoremove
> messages "Removing linux-headers-6.1
On 12.03.2025 04:12, Alex King wrote:
Yes, I can tell you more. The hardware as you guessed is not actually
new, it is recycled equipment that is new to me and newly installed
with Debian.
...
*-scsi
description: SCSI storage controller
product: S
On 3/11/25 18:12, Alex King wrote:
Yes, I can tell you more. The hardware as you guessed is not actually
new, it is recycled equipment that is new to me and newly installed
with Debian.
The machine is a Cisco MCS server, possibly a Cisco MCS7800 series.
(I'm not where the server is physi
Yes, I can tell you more. The hardware as you guessed is not actually
new, it is recycled equipment that is new to me and newly installed with
Debian.
The machine is a Cisco MCS server, possibly a Cisco MCS7800 series. (I'm
not where the server is physically now to check.) (Cisco MCS7800
se
On 3/11/25 8:48 AM, gene heskett wrote:
A problem that does not exist in gpt partition tables. Unforch, changing
it now will require a 100% backup/restore OR a reinstall to fix. fdisk
can do this table change by entering a g at the main screen, creating an
empty gpt table, and then an n will al
Le 3/11/25 à 09:17, Alexander V. Makartsev a écrit :
Can you tell us more information about hardware setup?
Could RAID setup play a role?
Best,
--
yassine -- sysadm
http://about.me/ychaouche
Looking for side gigs.
On 3/11/25 06:26, to...@tuxteam.de wrote:
On Tue, Mar 11, 2025 at 08:13:16PM +1300, Alex King wrote:
Hi,
hi
I've installed a large disk in a new machine and loaded Debian (bookworm) on
it, but it's showing as limited to 2TB when the disk should be larger.
How can I get Debian to use the fu
Le Tue, 11 Mar 2025 20:13:16 +1300,
Alex King a écrit :
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT: present
>
> Found valid GPT with protective MBR; using GPT.
Try to remove protective MBR.
Hi,
Timothy M Butterworth wrote:
> I have a 16TB drive that is working properly. I reformatted the drive to the
> ext4 file system with default settings and it works great. Try to reformat
> the drive especially if the current format is FAT.
Several of the shown inquiry methods did not refer to f
On Tue, Mar 11, 2025 at 6:26 AM wrote:
> On Tue, Mar 11, 2025 at 08:13:16PM +1300, Alex King wrote:
> > Hi,
>
> hi
>
> > I've installed a large disk in a new machine and loaded Debian
> (bookworm) on
> > it, but it's showing as limited to 2TB when the disk should be larger.
>
I have a 16TB drive
Timothy M Butterworth (HE12025-03-11):
> I have a 16TB drive that is working properly. I reformatted the drive to
> the ext4 file system with default settings and it works great. Try to
Good for you.
> reformat the drive especially if the current format is FAT.
We have both the kernel and gdisk
Hi,
Alex King wrote:
> I've installed a large disk in a new machine and loaded Debian (bookworm) on
> it, but it's showing as limited to 2TB when the disk should be larger.
> root@fj2:/home/installer# smartctl -i /dev/sdb
> [...]
> User Capacity: 8,001,563,222,016 bytes [8.00 TB]
> Sector Size
On Tue, Mar 11, 2025 at 11:40:29AM +0100, Nicolas George wrote:
> to...@tuxteam.de (HE12025-03-11):
> > It seems that the combination of MBR partition table and 512 byte blocks
> > limits you to partition sizes (and offsets) of roughly 2T, so it might
> > be this what's biting you:
>
> Highly doub
to...@tuxteam.de (HE12025-03-11):
> It seems that the combination of MBR partition table and 512 byte blocks
> limits you to partition sizes (and offsets) of roughly 2T, so it might
> be this what's biting you:
Highly doubtful considering these informations:
>> 8 16 2147483647 sdb
>> Fou
On Tue, Mar 11, 2025 at 08:13:16PM +1300, Alex King wrote:
> Hi,
hi
> I've installed a large disk in a new machine and loaded Debian (bookworm) on
> it, but it's showing as limited to 2TB when the disk should be larger.
>
> How can I get Debian to use the full 8TB on this disk?
It seems that th
Hi,
correction of the usual copy+paste error:
I wrote:
> 8001563222016 / 512 / 4294967296 = 7.277379356324673
The result stems from a different calculation with 2 exp 31.
With 2 exp 32 it is 3.638689678162337 .
Have a nice day :)
Thomas
On 11.03.2025 13:49, Yassine Chaouche wrote:
Le 3/11/25 à 09:17, Alexander V. Makartsev a écrit :
Can you tell us more information about hardware setup?
Could RAID setup play a role?
I don't think so, because of the way RAID controllers work, they
basically hide the real hardware HDDs behind
On 11.03.2025 12:13, Alex King wrote:
Hi,
I've installed a large disk in a new machine and loaded Debian
(bookworm) on it, but it's showing as limited to 2TB when the disk
should be larger.
How can I get Debian to use the full 8TB on this disk?
Can you tell us more information about hardwa
On 2025-02-14 22:00, Michael Stone wrote:
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
All 3 systems have the linux-image-amd64 metapackage installed.
What does apt show -a linux-image-amd64 | grep -e Version -e Sources
-e Depends
return on each system?
If you
apt update
on ea
On 14/02/2025 21:49, Gary Dale wrote:
On 2025-02-09 11:46, Max Nikulin wrote:
I recommend to compare
apt policy linux-image-amd64
and
apt policy
I can't see any differences between them on the various systems.
If it is true and the latest kernel is installed on all systems then
you
On Fri, Feb 14, 2025 at 09:42:10AM -0500, Gary Dale wrote:
All 3 systems have the linux-image-amd64 metapackage installed.
What does
apt show -a linux-image-amd64 | grep -e Version -e Sources -e Depends
return on each system?
If you
apt update
on each system, are there any error messages?
On 2025-02-09 11:46, Max Nikulin wrote:
On 09/02/2025 00:05, Gary Dale wrote:
VM1: /etc/apt/sources.list
I recommend to compare
apt policy linux-image-amd64
and
apt policy
I can't see any differences between them on the various systems.
On 2025-02-09 09:01, Greg Wooledge wrote:
On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote:
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
I have a few systems running Debian/Stable (Bookworm). However the kernel
version isn't always the same for some reason. After this mornin
On 2025-02-09 06:22, Henrik Ahlgren wrote:
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
I have a few systems running Debian/Stable (Bookworm). However the kernel version isn't always the same for some reason. After this morning's update, I noticed that 2 of the 3 systems upgraded the ke
On 09/02/2025 00:05, Gary Dale wrote:
VM1: /etc/apt/sources.list
I recommend to compare
apt policy linux-image-amd64
and
apt policy
Dis you install the package "linux-image-amd64" ? If yes, the it should always
update to the newest kernel.
(Same for package "linux-headers-amd64")
Hans
On Sun, Feb 09, 2025 at 13:22:50 +0200, Henrik Ahlgren wrote:
> On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
> > I have a few systems running Debian/Stable (Bookworm). However the kernel
> > version isn't always the same for some reason. After this morning's update,
> > I noticed that 2 of
On Sat, 2025-02-08 at 12:05 -0500, Gary Dale wrote:
>
> I have a few systems running Debian/Stable (Bookworm). However the kernel
> version isn't always the same for some reason. After this morning's update, I
> noticed that 2 of the 3 systems upgraded the kernel but to different
> versions. T
On 2024-07-31 16:00, Celejar wrote:
Update: FWIW, Debian Developer Ben Hutchings actually assigned this
issue a "grave" severity, and it was ultimately moved to the
initramfs-tools package. It's now fixed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076561
Well done! Thank you for helpin
Ash Joubert wrote:
> On 2024-07-20 03:39, Celejar wrote:
>
> Thanks much!
>
> [...]
>
> As per another message in this thread, I've already filed a bug against
> linux-image-6.9.9-amd64, but I suppose I should update the report with
> this information, indicating that it's not r
On Sat 20 Jul 2024 at 12:13:28 (+1200), Ash Joubert wrote:
> On 2024-07-20 03:39, Celejar wrote:
> > Thanks much!
> [...]
> > As per another message in this thread, I've already filed a bug against
> > linux-image-6.9.9-amd64, but I suppose I should update the report with
> > this information, indi
On 2024-07-20 03:39, Celejar wrote:
Thanks much!
[...]
As per another message in this thread, I've already filed a bug against
linux-image-6.9.9-amd64, but I suppose I should update the report with
this information, indicating that it's not really a problem with that
package.
You are welcome!
Ash Joubert wrote:
> On 2024-07-19 02:32, Celejar wrote:
>
> I'm currently on kernel 6.9.8 (amd64 / Sid). Installing 6.9.9 fails due to
> running out of space on /boot:
> update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
> zstd: error 70 : Write error : cannot write block
The Wanderer wrote:
...
> By taking on yourself the risk and burden of running sid, you are
> volunteering to be one of those who helps notice issues before they
> reach testing, and report those issues so that the machinery of the
> archive can stop the package versions which those issues from mig
On 2024-07-19 02:32, Celejar wrote:
I'm currently on kernel 6.9.8 (amd64 / Sid). Installing 6.9.9 fails due to
running out of space on /boot:
update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
zstd: error 70 : Write error : cannot write block : No space left on device
E: mkinitramfs failur
On 2024-07-18 at 10:32, Celejar wrote:
> Hello,
>
> I'm currently on kernel 6.9.8 (amd64 / Sid). Installing 6.9.9 fails due to
> running out of space on /boot:
>
> *
> update-initramfs: Generating /boot/initrd.img-6.9.9-amd64
> zstd: error 70 : Write error : cannot write block : No space lef
The Wanderer wrote:
> On 2024-07-18 at 13:50, Celejar wrote:
>
> > Andrew M.A. Cater wrote:
>
> >> This is not the place for debugging Sid, I'm afraid, there are too
> >> few
> >
> > It's not? Where, then, is the place for debugging Sid?
>
> I'm no longer anything *close* to an expert in this
On 18 Jul 2024 13:47 -0400, from cele...@gmail.com (Celejar):
>> I don't mean this to be snarky, but that desire seems incompatible
>> with running Debian sid. I honestly think it's an unreasonable
>> expectation to want official guides for every transitory broken
>> state in a development tree.
>
On 2024-07-18 at 13:50, Celejar wrote:
> Andrew M.A. Cater wrote:
>> This is not the place for debugging Sid, I'm afraid, there are too
>> few
>
> It's not? Where, then, is the place for debugging Sid?
I'm no longer anything *close* to an expert in this area (having not run
sid myself in well o
On Thu, Jul 18, 2024 at 13:50:21 -0400, Celejar wrote:
> Really? I had the impression that lots of list subscribers / readers
> run Sid. Are there statistics on this?
Nah, sid users are just louder, on average. Stable users don't have
as much to talk about, because our stuff just works. ;-)
Andrew M.A. Cater wrote:
> On Thu, Jul 18, 2024 at 03:42:30PM +, Andy Smith wrote:
> > Hi,
> >
> > On Thu, Jul 18, 2024 at 11:35:15AM -0400, Celejar wrote:
> > > I'd rather not mess around with stuff I don't really understand
> > > without an official guide to the process.
> >
> > I don't me
Andy Smith wrote:
> Hi,
>
> On Thu, Jul 18, 2024 at 11:35:15AM -0400, Celejar wrote:
> > I'd rather not mess around with stuff I don't really understand
> > without an official guide to the process.
>
> I don't mean this to be snarky, but that desire seems incompatible
> with running Debian sid.
On Thu, Jul 18, 2024 at 03:42:30PM +, Andy Smith wrote:
> Hi,
>
> On Thu, Jul 18, 2024 at 11:35:15AM -0400, Celejar wrote:
> > I'd rather not mess around with stuff I don't really understand
> > without an official guide to the process.
>
> I don't mean this to be snarky, but that desire seem
Hi,
On Thu, Jul 18, 2024 at 11:35:15AM -0400, Celejar wrote:
> I'd rather not mess around with stuff I don't really understand
> without an official guide to the process.
I don't mean this to be snarky, but that desire seems incompatible
with running Debian sid. I honestly think it's an unreasona
Dan Ritter wrote:
> Celejar wrote:
> > Hello,
> >
> > I'm currently on kernel 6.9.8 (amd64 / Sid). Installing 6.9.9 fails due to
> > running out of space on /boot:
>
> ...
>
> > I'm not sure why I'm hitting this now - did Debian just change
> > something? Is anyone else hitting this? Is this
Celejar wrote:
> Hello,
>
> I'm currently on kernel 6.9.8 (amd64 / Sid). Installing 6.9.9 fails due to
> running out of space on /boot:
...
> I'm not sure why I'm hitting this now - did Debian just change
> something? Is anyone else hitting this? Is this documented somewhere?
> Is there a str
On Mon, 2024-07-08 at 17:46 +, Andrew M.A. Cater wrote:
> On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> > I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique
> > Dell
> > Vostro 1700. Occasionally it crashes with
> >
> > "Kernel Panic - not syncing: Can not alloc
On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
> Vostro 1700. Occasionally it crashes with
>
> "Kernel Panic - not syncing: Can not allocate SWIOTLB buffer earlier
> and can't now provide you with the DMA bounce
On Sun, Jul 07, 2024 at 07:07:26PM -0700, Van Snyder wrote:
> I recently installed Debian 12.5 with kernel 6.5.0.0 on an antique Dell
> Vostro 1700. Occasionally it crashes with
>
So you installed this kernel from where?
Stable (Debian 12/ bookworm) uses linux kernal 6.1.XXX
> "Kernel Panic - no
many java dev ecosystem (such as big data stacks) are in debian 11.
it's hard to upgrade to 12 at this time.
Thanks.
Keep in mind that Debian 11 will be out of oldstable in about a year,
with the release of 13/Trixie; and it will be out of security support
in a few weeks, with the transition
On 9 Jun 2024 07:41 +0800, from j...@tls-mail.com (Jeff Peng):
> debian 11 installed.
Keep in mind that Debian 11 will be out of oldstable in about a year,
with the release of 13/Trixie; and it will be out of security support
in a few weeks, with the transition to long-term support. Depending on
t
On Sun, Jun 09, 2024 at 06:58:21AM +0200, to...@tuxteam.de wrote:
> On Sun, Jun 09, 2024 at 07:41:58AM +0800, Jeff Peng wrote:
> > Hello
> >
> > I am using the VMs from big providers such as AWS and Azure.
>
> I'd ask AWS/Azure support for that.
Yes, talking _with_ your vendor is the way to go.
On Sun, Jun 09, 2024 at 07:41:58AM +0800, Jeff Peng wrote:
> Hello
>
> I am using the VMs from big providers such as AWS and Azure.
I'd ask AWS/Azure support for that. They do knowi their infrastructure
best, we hope, and, after all, they are taking money for their service.
Cheers
--
t
signat
On 9/6/24 07:41, Jeff Peng wrote:
Hello
I am using the VMs from big providers such as AWS and Azure.
most of the VMs are 2core/4gb ram/100gb disk etc.
They are used for running the regular web services (java, php etc),
with debian 11 installed.
Every VM I just use the default system configu
On 2024-01-10, Herb Garcia wrote:
> Does this method also create the modules?
>> make menuconfig
this one permits you to change kernel parameters if needed
>> make bindeb-pkg
this one compiles kernel and produces
linux-headers-*.deb
linux-image-*.deb
linux-image contains kernel and internal
Does this method also create the modules?
-Herb
On Tue, 2024-01-09 at 13:17 +0100, Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
> > I download the required depen
On 2024-01-09, HP Garcia wrote:
> What dependencies did you install?
All are installed with those commands, thanks Debian :)
apt build-dep linux
apt install build-essential libncurses-dev
(last one for running menuconfig with ncurses)
What dependencies did you install?
~Herb
On Tue, Jan 9, 2024, 7:23 AM Michel Verdier wrote:
> On 2024-01-08, Herb Garcia wrote:
>
> > I was able to compile Linux kernel 6.1.X.
> >
> > When I tried compiling kernel 6.5.x and ran into issues.
> >
> > I download the required dependencies as requir
On 2024-01-08, Herb Garcia wrote:
> I was able to compile Linux kernel 6.1.X.
>
> When I tried compiling kernel 6.5.x and ran into issues.
>
> I download the required dependencies as required per
> https://www.kernel.org/doc/html/v6.7/process/changes.html#changes
To compile 6.5 I do
apt build-
On Thu, 2023-08-24 at 10:06 +0200, Erwan David wrote:
> I had an upgrade failure today, when upgrading kernel to 6.4.0-3 :
> virtualbox-dkms needs a function which disappeared from kernel headers.
>
> I opened the bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050406
>
Which has been ma
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
1 - 100 of 4986 matches
Mail list logo
