You are not logged in.

#26 2023-03-02 11:06:12

d.ALT
Member
Registered: 2019-05-10
Posts: 924

Re: [Solved] Same disk mounting to two locations after changing boot disk

Shibboleth wrote:

Also, regarding the incorrect partition size of nvme0n1p1 - am I right in thinking that this could be sorted with the following?

resize2fs /dev/nvme0n1

lsblk output:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 447.1G  0 disk
└─sda1        8:1    0 447.1G  0 part /ssd
sdb           8:16   0 931.5G  0 disk
└─sdb1        8:17   0 931.5G  0 part /mnt
nvme0n1     259:0    0 931.5G  0 disk
└─nvme0n1p1 259:1    0 447.1G  0 part /

What do you read under the TYPE column? (emphasis' mine)


Did you try the temporary woorkaround?

d.ALT wrote:
Shibboleth wrote:

rebuilding the initramfs

While still in GRUB's menu, edit (press "e") the default ArchLinux's entry like this:

linux	/boot/vmlinuz-linux root=/dev/nvme0n1p1 rw

<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#27 2023-03-02 11:35:13

Shibboleth
Member
Registered: 2023-03-01
Posts: 15

Re: [Solved] Same disk mounting to two locations after changing boot disk

DESCRIPTION
       The  resize2fs  program  will resize ext2, ext3, or ext4 file systems.  It can be used to en‐
       large or shrink an unmounted file system located on device.  If the file system  is  mounted,
       it  can  be  used  to expand the size of the mounted file system, assuming the kernel and the
       file system supports on-line resizing.

I thought the device in the man page was the disk - I take it that's incorrect?
I've not tried the workaround yet, I'll give it a go now if it fails to boot again after rebuilding the initramfs again there

Offline

#28 2023-03-02 11:38:34

Shibboleth
Member
Registered: 2023-03-01
Posts: 15

Re: [Solved] Same disk mounting to two locations after changing boot disk

Rebooting works fine now without the workaround - not really sure what's changed aside from that second rebuild

Offline

#29 2023-03-02 12:51:09

d.ALT
Member
Registered: 2019-05-10
Posts: 924

Re: [Solved] Same disk mounting to two locations after changing boot disk

Shibboleth wrote:

Rebooting works fine now without the workaround

I'm glad for you! Please, edit your 1st Post's title adding [SOLVED].


Shibboleth wrote:

not really sure what's changed aside from that second rebuild

Me too tongue But let's wait for experts here to enlighten us about your situation! wink


<49,17,III,I>    Fama di loro il mondo esser non lassa;
<50,17,III,I>    misericordia e giustizia li sdegna:
<51,17,III,I>    non ragioniam di lor, ma guarda e passa.

Offline

#30 2023-03-02 13:09:25

Shibboleth
Member
Registered: 2023-03-01
Posts: 15

Re: [Solved] Same disk mounting to two locations after changing boot disk

d.ALT wrote:
Shibboleth wrote:

not really sure what's changed aside from that second rebuild

Me too tongue But let's wait for experts here to enlighten us about your situation! wink

Yeah, still not sure what caused that issue - resizing the nvme partition with parted sorted the last issue. I'll flag the thread as solved now. Thanks a lot for your help smile

Offline

#31 2023-03-06 20:30:40

GregTheHun
Member
Registered: 2023-03-06
Posts: 4

Re: [Solved] Same disk mounting to two locations after changing boot disk

d.ALT wrote:
  1. Boot into ArchLinux's Live Environment (ISO or USB medium)

  2. Mount /dev/nvme0n1p1 into /mnt

  3. Mount /dev/sda1 into /mnt/ssd

  4. Mount /dev/sdb1 into /mnt/mnt

  5. # cp /mnt/etc/fstab /mnt/etc/fstab.bkp
  6. # genfstab -U /mnt > /mnt/etc/fstab
  7. # arch-chroot /mnt
  8. Reinstall GRUB into the BIOS' MBR: https://wiki.archlinux.org/title/GRUB#M … structions

  9. Re-generate grub.cfg

  10. Un-mount everything and Reboot

Sorry to bring up a slightly old thread, but how would this differ is I was using GPT with UEFI?

I'm trying to get the order from top to bottom, I've already cloned my old ssd to my nvme ssd, this was using Clonezilla and using biginner mode, device-to-device, and selecting -k1 to expand the btrfs partition.

So, here is some info:

- BLKID -

[root@sysrescue /dev]# blkid
/dev/nvme0n1p1: UUID="D341-2F9B" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="49483d97-926c-4134-9aa4-64dc623ce717"
/dev/nvme0n1p2: UUID="2b189ba1-e0bb-4e1d-a929-36cac285e69b" UUID_SUB="5c2465e4-10e2-4ac6-b0fc-6cecc8bd5b05" BLOCK_SIZE="4096" TYPE="btrfs" PARTLABEL="primary" PARTUUID="57cec0a0-e7f7-4d5b-b27a-ffb40fe08e81"
/dev/sda1: LABEL="Ventoy" UUID="86C5-D93A" BLOCK_SIZE="512" TYPE="exfat" PTTYPE="dos" PARTLABEL="Ventoy" PARTUUID="45376275-07fe-cb41-6300-a39f75322b91"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="VTOYEFI" LABEL="VTOYEFI" UUID="B228-8EFB" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="VTOYEFI" PARTUUID="0bdc5c9a-9675-f203-99d1-85aac0b82c52"

- GPARTED INFO -
fjMDsR2.png

The only differences from these steps that I can see would be 8 and 9 for me, but if I'm missing anything else I would love to know what to do?

Thanks all!

Last edited by GregTheHun (2023-03-06 20:32:02)

Offline

Board footer

Powered by FluxBB