On 1 Sep 2025 at 22:56, Samuel Sieb wrote: Date sent: Mon, 1 Sep 2025 22:56:10 -0700 Subject: Re: Failure in switching Disk that I don't understand. To: Community support for Fedora users <[email protected]> From: Samuel Sieb <[email protected]> Send reply to: Community support for Fedora users <[email protected]>
> On 2025-09-01 22:53, Michael D. Setzer II wrote: > > On 1 Sep 2025 at 22:36, Samuel Sieb wrote: > > > > Date sent: Mon, 1 Sep 2025 22:36:13 -0700 > > Subject: Re: Failure in switching Disk that I don't > > understand. > > To: [email protected] > > From: Samuel Sieb <[email protected]> > > Send reply to: Community support for Fedora users > > <[email protected]> > > > >> On 2025-09-01 22:32, Michael D. Setzer II via users wrote: > >>> Have a dell lattitude 5580. > >>> It originally had a 500M nvme card that was showing as SDA > >>> Installed a 1TB SSD drive and imaged the 500M to 1TB and it > >>> showd up as SDB. Booted fine after swapping out nvme since they > >>> had same UUID for partitions. > >>> > >>> Went to upgrade the SDB 1TB to nvme 2TB. But ended up with a > >>> non-bootable system. > >>> Did image, and removed the SSD SDB drive from computer, but > >>> booting fails with message it can't find partitions with UUID? > >>> logging in with debug root password, and chec, the UUIDs, and > >>> they match exactly for all partitions. Difference is that partitions > >>> are not showing as /dev/sd? setting but as /dev/nvme.... > >>> > >>> fstab has > >>> UUID=de10a0a9-fd86-4625-a768-67477a8a802d / > >>> ext4 defaults 1 1 > >>> UUID=01d61794-271a-4d17-a901-47afee995382 /boot > >>> ext4 defaults 1 2 > >>> UUID=B5B5-43CF /boot/efi vfat > >>> umask=0077,shortname=winnt 0 2 > >>> UUID=a041e51f-4fcb-48c3-b249-c39c1af03b5e /home > >>> ext4 defaults 1 2 > >>> UUID=892e9432-1c99-4357-8213-6683c0692b55 /data > >>> ext4 defaults 1 2 > >>> UUID=375c1b5d-f295-4319-8014-cb800bb6a938 /data2 > >>> ext4 defaults 1 2 > >>> > >>> And the uuids are same on the /dev/sdb and /dev/nvme.... > >>> Machine boots fine with only /dev/sdb installed, but if only the nvme > >>> drive it after a long time comes up with a failed boot and drops to > >>> the root debug login. > >>> > >>> So have no clue why it isn't working when the UUIDs are exactly > >>> the same. Image is a straight dd image. > >>> > >>> At moment, I'm doing a clean install of Fedora 42 to the 2TB nvme > >>> on another Dell 5580 and it it also, showing nvme?? > >>> > >>> Will have to do a lot of manual work to setup it up to have the setup > >>> I need rather than just image? > >>> > >>> Any ideals on what might have caused the fail, or ways to fix it. > >>> Tried using recovery kernel option, but does same thing. > >> > >> The nvme driver might not be in the initramfs. Try booting the rescue > >> option which includes all the drivers. > > > > I had tried booting with the rescue kernel, and it gives same error. > > After logining in for the root password, it puts me in the /root > > directory, and shows the files that are in that directory. > > > > That is same with regular and with rescue kernel. > > Then check the logs and see what's failing. > Not sure were logs would be. After debug login, it seemed to just put in the /root directory, and didn't show anything else to be mounted. Did say something about copy a file to a USB device to save a copy, but is my primary notebook. Am currently 7 timezones away from my primary machines, so just have 3 notebooks with me. Did a clean install of Fedora 42 on the 2TB nvme device. Went fine, but noticed it gave no option to use regular partitions Info from 2TB nvme with clean install. cat /etc/fstab # # /etc/fstab # Created by anaconda on Tue Sep 2 05:42:59 2025 # # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info. # # After editing this file, run 'systemctl daemon-reload' to update systemd # units generated from this file. # UUID=e5f816a5-2f9b-4f32-bc08-4435bca1e1ab / btrfs subvol=root,compress=zstd:1 0 0 UUID=3983df11-d173-46fe-9ffc-5a73fe3521ca /boot ext4 defaults 1 2 UUID=0C1D-A067 /boot/efi vfat umask=0077,shortname=winnt 0 2 UUID=e5f816a5-2f9b-4f32-bc08-4435bca1e1ab /home btrfs subvol=home,compress=zstd:1 0 0 root@fedora:/home/msetzerii# hdparm -Tt /dev/nvme0n1 /dev/nvme0n1: Timing cached reads: 28332 MB in 1.99 seconds = 14272.35 MB/sec Timing buffered disk reads: 4280 MB in 3.00 seconds = 1426.58 MB/sec Cached speed is a little slower on nvme, but buffered speed is about 3 1/2 times faster The SSD drive in primary machine hdparm -Tt /dev/sdb /dev/sdb: Timing cached reads: 29804 MB in 1.98 seconds = 15061.62 MB/sec Timing buffered disk reads: 1138 MB in 3.01 seconds = 377.72 MB/sec This machine has an nvme disk, but it shows as /dev/sda not /dev/nvme... hdparm -Tt /dev/sda /dev/sda: Timing cached reads: 25526 MB in 1.98 seconds = 12894.37 MB/sec Timing buffered disk reads: 1414 MB in 3.00 seconds = 470.74 MB/sec So, not sure why one uses /dev/sda for the nvme disk and other uses /dev/nvme0n1? Had a compress disk image of the original /dev/sdb disk. 90953390895 Sep 2 2025 sdb-all.lzo compresses from 1TB to 85G sfdisk -l /dev/sdb Disk /dev/sdb: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: Fanxiang S101Q 1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 70647742-8953-40B3-8BDE-1C14F7B6D51B Device Start End Sectors Size Type /dev/sdb1 2048 1230847 1228800 600M EFI System /dev/sdb2 1230848 3327999 2097152 1G Linux filesystem /dev/sdb3 3328000 150128639 146800640 70G Linux filesystem /dev/sdb4 150128640 1590808575 1440679936 687G Linux filesystem /dev/sdb5 1590808576 2000408575 409600000 195.3G Linux filesystem All unused sectors zeroed out before image. sfdisk info for 2TB nvme sfdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: CT2000T500SSD8 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 9A06BD15-90EE-4358-8978-89ED6EB10686 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 1230847 1228800 600M EFI System /dev/nvme0n1p2 1230848 3327999 2097152 1G Linux extended boot /dev/nvme0n1p3 3328000 3907028991 3903700992 1.8T Linux filesystem > -- > _______________________________________________ > users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:[email protected] mailto:[email protected] mailto:[email protected] Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+ -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
