Your message dated Thu, 20 Feb 2025 12:22:44 +0100 (CET)
with message-id <20250220112244.028e3be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #930594,
regarding Partitions only usable with the sata-controller it has been created
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.)
--
930594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.144-2
Severity: normal
Hello,
maybe this is an known problem, because i found an extended description of this
problem in the internet:
https://linux-blog.anracom.com/2018/12/03/linux-ssd-partition-alignment-problems-with-external-usb-to-sata-controllers-i/
The problem first was that an harddisk did not work any more on an pc.
So i extracted it and analyzed it connected with an USB-Adapter on an other PC.
I found out that the partition-list was deleted and reconstructed it.
After that all data could be rescued and an e2fsck-check of the partitions
where successful.
But after reintegrating of the harddisk the partitions are still unreadable!
After searching for the problem i found the article above and i had to connect
and restore it with the original controller.
That is unbelievable, because how can the partitions be dependent on the
Sata-controller used?
That is really strange!
Where can this be reported to the kernel team or is this problem solved in
actual kernel versions?
Here an example of this harddisk:
-------------------------------------------
Correct is this paritioning shown with fdisk and readable with the USB
controller:
Disk /dev/sdd: 931,5 GiB, 1000204886016 bytes, 244190646 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x5537c98f
Device Boot Start End Sectors Size Id Type
/dev/sdd1 256 10486015 10485760 40G 83 Linux
/dev/sdd2 10486016 20971775 10485760 40G 83 Linux
/dev/sdd3 20971776 21233919 262144 1G 82 Linux swap / Solaris
/dev/sdd4 21233920 244190645 222956726 850,5G 83 Linux
Connecting the disk direct to the onboard Sata controller shows:
Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x5537c98f
Device Boot Start End Sectors Size Id Type
/dev/sdc1 256 10486015 10485760 5G 83 Linux
/dev/sdc2 10486016 20971775 10485760 5G 83 Linux
/dev/sdc3 20971776 21233919 262144 128M 82 Linux swap / Solaris
/dev/sdc4 21233920 244190645 222956726 106,3G 83 Linux
and the partitions can't be mounted of course:
mount /dev/sdc4 /media/sdc4
mount: wrong fs type, bad option, bad superblock on /dev/sdc4,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
Cheers
karsten
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
