XPost: linux.debian.bugs.dist   
   From: carnil@debian.org   
      
   Control: tags -1 + moreinfo   
      
   Hi David,   
      
   On Mon, Feb 02, 2026 at 03:59:38PM +0100, Z80user wrote:   
   > ============================================   
   > NOTES to understand the rest of the message:   
   > ============================================   
   > English isn't my natural language   
   > Dates are as YYYY-MM-DD   
   >   
   > all of the partitions I talking are NTFS partitions, is just because if the   
   > partition is corrupted I know how to rescue it more easy   
   >   
   > Type of data corruptions   
   > Type 1. the partition can NOT be mount with gnome-disk-utility but it can   
   > be mount with the mount command or if it is added to the /mnt/   
   > Type 2. the partition can NOT be mount with gnome-disk-utility either with   
   > mount on /mnt/ but if the partition is copy into a file with "dd" or   
   > "ddrescue" and you mount it in a loop device you can read the data from it   
   > Type 3. the partition can NOT be mount with gnome-disk-utility, mount or   
   > the loop device trick and the data is lost unless you used a data rescue   
   > software   
   >   
   > only Type 1 and 2 are present on this problems, so is possible to read it   
   > back and isn't data corruption but as normal people can not access it's   
   > almost like a data corruption, is needed to use some trick to can read it   
   > I didn't have any Type 3 data corruption yet   
   >   
   > at the end of the first report I wrote a lot of extra info too but as is   
   > the first time I made a report I didn't know where to place that info   
   > ============================================   
   > The video show the problem, sometimes on the top left corner appear a box   
   > where I enter the root password to allow changes   
   > 0:40 the Operating system didn't leave me to unmount the partition because   
   > ffmpeg was creating a miniature because "caja" was open.   
   >   
   > it happen the same on two of my physical computers   
   > On the computer on the shop I have (the one that create the report, install   
   > on 2025-01-09):   
   > 6.12.48+deb13-amd64 *1   
   > 6.12.57+deb13-amd64 *2   
   > 6.12.63+deb13-amd64 *3   
   > 6.17.13+deb13-amd64 *4  in use   
   >   
   > On the computer I have at home: (I install it 2026-11-21)   
   > 6.12.41+deb13-amd64 *5   
   > 6.12.57+deb13-amd64   
   > 6.12.63+deb13-amd64 in use   
   >   
   > I have a VM on proxmox that don't show that problem with Debian 12 (I   
   > create it 2026-01-09)   
   > 6.1.0-22-amd64   
   > 6.1.0-42-amd64 in use   
   >   
   >   
   > *1 I didn't test it yet   
   > *2 it have the problem   
   > *3 it have the problem   
   > *4 it have the problem, I manually install and this days is the one is use   
   >   
   >   
   > -. It's not too easy to replicate it, only if I move a lot of data between   
   > one disk and another, usually if the NvME drivers are used   
   > -. mount and unmount any partition does not create this problems and you   
   > can see on the video   
   > -. if I reboot or power off the computer and a external HDD is mount, the   
   > partition get "corrupted" with the Type 2 of corruption (see the start of   
   > the post)   
   > -. data lost when the computer is turn off by software   
   > -. sometimes data lost when the computer crash is Type 1 on internal   
   > devices (I don't know on external devices)   
   > -. data lost when the computer have a silence crash most of the times is   
   > Type 2 on internal an internal devices (when / root disappear)   
   >   
   > And maybe one strange thing is:   
   > It happens most of the times with new NTFS partitions (created with   
   > gnome-disk-utility). and I mean new partitions are partitions created   
   > recently, with old partitions created way before I move from Debian 12 to   
   > Debian 13 look like they are not affected by this bug   
   >   
   > I can keep the state of that machine frozen in time to can made more test   
   > on it and I have some 40, 100, 120 and (8) 160 GB HDDs to can test almost   
   > anything if will be needed if someone said me a new test   
      
   If nothing get logged in time to your system logs, we might try to   
   gather more information by attaching a netconsole. You need a second   
   device in your lan to recieve the netconsole messages.   
      
   Instructions on how to do it are documented in:   
   https://docs.kernel.org/networking/netconsole.html   
      
   To make things handy once it work to send messaged to the remote host,   
   add (temporary, it can be dropped again after the debug session) a   
   dropin file /etc/default/grub.d/netconsole.cfg containing the required   
   settings:   
      
   GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX netconsole=[...]"   
      
   and then run update-grub2.   
      
   Can you please try that and then wait to trigger the problem and   
   collect the logs sent via netconsole.   
      
   Regards,   
   Salvatore   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)