[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: transferring boot





On 7/31/25 13:21, Nicolas George wrote:
Eben King (HE12025-07-31):
I recently got some SSDs, and decided to use one of them (a 256G model) to
boot from.  I want the change to be undetectable, in that from a user
perspective, nothing seems different, just faster.

I currently have a 2T HD, partitioned with GPT but booting by MBR.  Yes,
that's probably weird.  When I installed Debian I was unaware that the
installer would only install grub to boot using the method that the
installer booted.  My BIOS/firmware will boot using either method, but
defaults to MBR if both methods work.  You can force it to use UEFI on a
one-time basis.  I want the SSD to boot using UEFI.  Is that possible, and
if so, what's the best method to go about it?

The most convenient method depends on what exactly you have right now.
Can you share the output of lsblk and df?

eben@cerberus:~$ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda       8:0    0 238.5G  0 disk
└─sda1    8:1    0 238.5G  0 part
sdb       8:16   0   1.8T  0 disk
├─sdb1    8:17   0   953M  0 part /boot
├─sdb2    8:18   0     2G  0 part /
├─sdb3    8:19   0    20G  0 part /usr
├─sdb5    8:21   0   953M  0 part
├─sdb6    8:22   0   300G  0 part
├─sdb7    8:23   0    30G  0 part /misc/export
├─sdb8    8:24   0   130G  0 part /misc/media
├─sdb9    8:25   0   165G  0 part /misc/mp3
├─sdb10   8:26   0    74G  0 part /misc/torrent
├─sdb11   8:27   0     9G  0 part /home
├─sdb12   8:28   0    75G  0 part /misc/scratch
└─sdb13   8:29   0    48G  0 part [SWAP]
sdc       8:32   0 238.5G  0 disk
├─sdc1    8:33   0   5.1G  0 part /var/cache
└─sdc2    8:34   0 182.7G  0 part /misc/iso
sdd       8:48   1     0B  0 disk
sr0      11:0    1   7.5G  0 rom
0
eben@cerberus:~$ df
Filesystem          1K-blocks      Used  Available Use% Mounted on
udev                 16132328         0   16132328   0% /dev
tmpfs                 3229464      1796    3227668   1% /run
/dev/sdb2             2047208    802856    1123116  42% /
/dev/sdb3            20557912   8146532   11439652  42% /usr
tmpfs                16147316     71380   16075936   1% /dev/shm
tmpfs                    5120        16       5104   1% /run/lock
/dev/sdc1             5157164   1373336    3501616  29% /var/cache
/dev/sdc2           187459092  79418636   98445320  45% /misc/iso
/dev/sdb7            30786644  19419460    9777988  67% /misc/export
/dev/sdb1              941740    132468     744096  16% /boot
/dev/sdb8           133589828 122712680    4045076  97% /misc/media
/dev/sdb12           76832012  43023296   29860172  60% /misc/scratch
/dev/sdb9           169191044 156127788    4396124  98% /misc/mp3
/dev/sdb10           75799884  46825720   25078052  66% /misc/torrent
/dev/sdb11            9278492   7747788    1042472  89% /home
tmpfs                 3229460      2484    3226976   1% /run/user/1000
nascent:/nfs/Media 1918708224 774040384 1125174848  41% /mnt/nascent-Media
0
eben@cerberus:~$

sda is the new SSD. sdb is my HD. sdc is another SSD. nascent is a NAS. No idea what sdd is:

eben@cerberus:~$ sudo fdisk -l /dev/sdd
fdisk: cannot open /dev/sdd: No medium found




Reply to: