[Bug 1921009] [NEW] Failure applying dump from m.5 drive to SCSI drive
Kevin O'Gorman
1921009 at bugs.launchpad.net
Tue Mar 23 21:48:09 UTC 2021
Public bug reported:
I have a dump from an M.5 drive named "/dev/nvme0n1" that I wanted to
apply to a regular SCSI drive /dev/sdc. This got the GPT built but when
it tried to work on partitions, it failed, giving the error message
sfdisk: failed to parse partition number: '/dev/sdc'
This is probably due to the oddity of drive names for M.5 drives -- they
end in a digit, so a "p" is inserted before the actual partition
numbers. So the first partition may appear to be "p1" instead of "1".
I know, I ran into it working on some software of my own.
Anyway, the dump is attached. Try applying it to a regular "/dev/sd?"
drive and you will prpbably see the same thing.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: fdisk 2.34-0.1ubuntu9.1
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Mar 23 14:39:53 2021
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2021-02-19 (32 days ago)
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Attachment added: "output of sfdisk --dump on M.5 drive (/dev/nvme0n1)"
https://bugs.launchpad.net/bugs/1921009/+attachment/5480322/+files/dump.txt
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921009
Title:
Failure applying dump from m.5 drive to SCSI drive
Status in util-linux package in Ubuntu:
New
Bug description:
I have a dump from an M.5 drive named "/dev/nvme0n1" that I wanted to
apply to a regular SCSI drive /dev/sdc. This got the GPT built but
when it tried to work on partitions, it failed, giving the error
message sfdisk: failed to parse partition number: '/dev/sdc'
This is probably due to the oddity of drive names for M.5 drives --
they end in a digit, so a "p" is inserted before the actual partition
numbers. So the first partition may appear to be "p1" instead of "1".
I know, I ran into it working on some software of my own.
Anyway, the dump is attached. Try applying it to a regular "/dev/sd?"
drive and you will prpbably see the same thing.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: fdisk 2.34-0.1ubuntu9.1
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Mar 23 14:39:53 2021
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2021-02-19 (32 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1921009/+subscriptions
More information about the foundations-bugs
mailing list