Your message dated Sun, 6 Jul 2025 11:30:16 -0700
with message-id
<7h2a4irm6v6amcyiswltv2cuyhpl6ehmbrj5w3elgp4hrnb26c@ba2qetdfxmjb>
and subject line Re: Bug#1108871: bugs.debian.org: xhci hostcontroller not
responding assume dead after 283m formatting a 5GB USB enclosure hdd
has caused the Debian Bug report #1108871,
regarding bugs.debian.org: xhci hostcontroller not responding assume dead after
283m formatting a 5GB USB enclosure hdd
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1108871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bugs.debian.org
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: bigf...@killerhippy.de, bigf...@killerhippy.de
I use rear, relax and recover from git: https://github.com/rear/rear
with 2 other, younger computers. On my old, an Dell Optiplex 7010 I
can't use rear, because it cannot format an 5G HDD enclosure
connected via usb using the build in usb-2.0 ports.
sascha@uranus:~/git/rear$ time sudo ./usr/sbin/rear format /dev/sdd
USB or disk device /dev/sdd is not formatted with ext2/3/4 or btrfs filesystem
Formatting /dev/sdd will remove all currently existing data on that whole device
Type exactly 'Yes' to format /dev/sdd with ext3 filesystem
(default 'No' timeout 300 seconds)
Yes
ERROR: Failed to create ext3 filesystem on ReaR data partition /dev/sdd3
Some latest log messages since the last called script 300_format_usb_disk.sh:
2025-07-06 11:58:53.828037465 Setting 'bios_grub' flag on BIOS boot partition
/dev/sdd1
2025-07-06 11:58:54.035346197 Making an EFI bootable device /dev/sdd
2025-07-06 11:58:54.039567964 Creating EFI system partition 2 on device
/dev/sdd with size 1024 MiB aligned at 8 MiB
2025-07-06 11:58:54.240233325 Setting 'esp' flag on EFI partition 2 on device
/dev/sdd
2025-07-06 11:58:54.468633594 Creating ReaR data partition 3 on /dev/sdd up
to 100% of /dev/sdd
2025-07-06 11:58:54.890114726 Setting 'legacy_boot' flag on ReaR data
partition 3 on device /dev/sdd
2025-07-06 11:59:00.344023960 Creating vfat filesystem on EFI system
partition on /dev/sdd2
2025-07-06 11:59:00.612236321 Creating ext3 filesystem with label 'REAR-000'
on ReaR data partition /dev/sdd3
Some messages from /var/tmp/rear.AnWeQjZuDF3AWVt/tmp/rear.format.stdout_stderr
since the last called script 300_format_usb_disk.sh:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: 583/37253
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: mkfs.ext3:
Input/output error while writing out and closing file system
Use debug mode '-d' for some debug messages or debugscript mode '-D' for full
debug messages with 'set -x' output
Aborting due to an error, check
/home/sascha/git/rear/var/log/rear/rear-uranus.log for details
Beendet
real 283m16,167s
The problem is not rear but the xhci host croller, see attached files
dmesg.6.1.0-35-amd64-2025-07-06.txt
rear-uranus.log
When xhci dies, my usb mouse is dead, too. I can rmmod and modprobe xhci
to get the mouse back but the rear problem persists. Not so at the other
computers that have usb-3.0 or usb-c to connect such an usb enclosure.
I am pretty shure, that this is a kernel bug. Please help me to get this
problem solved.
debian_version 12.11
Greetings from Wolfenbuettel,
Sascha
--- End Message ---
--- Begin Message ---
On Sun, 06 Jul 2025, Sascha Wuestemann wrote:n
> Allocating group tables: done
> Writing inode tables: 583/37253
> Creating journal (262144 blocks): done
> Writing superblocks and filesystem accounting information: mkfs.ext3:
> Input/output error while writing out and closing file system
> Use debug mode '-d' for some debug messages or debugscript mode '-D' for full
> debug messages with 'set -x' output
> Aborting due to an error, check
> /home/sascha/git/rear/var/log/rear/rear-uranus.log for details
> Beendet
This is almost certainly a hardware issue, not a software issue. [I'd
suspect overheating, but with a very old system it's hard to say.]
Regardless, it's not grave, and it's also not a bug against the bug
tracking system, so I'm closing it.
That said, thanks for giving enough information so we could see what the
issue likely was.
--
Don Armstrong https://www.donarmstrong.com
Logs drowse in the pond
Dreaming of their heroes
Alligator and crocodile
-- Vern Rutsala "Poetry in Motion" p77
--- End Message ---
