Of course I have none, and Bits has supported the cause for some time.
So a bit of google turned a howto page. It seems quite simple.
The page suggests
e2label /dev/sda1 Boot
OR
# tune2fs -L Boot /dev/sda1
The page does not say that it can't be done on a running system.
Is it safe to do so?
It does also say that
mkfs.ext4 /dev/sda1 -L ROOT
can also be done but not on existing partitions with a file system - obviously
Of course I have none, and Bits has supported the cause for some time.
The page does not say that it can't be done on a running system.
Is it safe to do so?
On Sat, 31 Aug 2019 15:00:29 +1000, faeychild wrote:
Of course I have none, and Bits has supported the cause for some time.
I am not supporting the cause for labels.
Of course I have none, and Bits has supported the cause for some time.
So a bit of google turned a howto page. It seems quite simple.
The page suggests
e2label /dev/sda1 Boot
OR
# tune2fs -L Boot /dev/sda1
The page does not say that it can't be done on a running system.
Is it safe to do so?
It does also say that
mkfs.ext4 /dev/sda1 -L ROOT
can also be done but not on existing partitions with a file system - obviously
regards
I have a script to change clean install's /etc/fstab
from UUID=xxx to LABEL=xxx
On 31/8/19 6:14 pm, Bit Twister wrote:
I have a script to change clean install's /etc/fstab
from UUID=xxx to LABEL=xxx
! would be interested in seeing that one
I haven't paid any attention to Grub and my last dual boot arrangement
was with Windows and Lilo last century.
But I like the idea of a rescue application available at boot
I am still reading and googling the 20b_rescue_cd_xx__grub script
On Mon, 2 Sep 2019 12:33:46 +1000, faeychild wrote:functions.
On 31/8/19 6:14 pm, Bit Twister wrote:
I have a script to change clean install's /etc/fstab
from UUID=xxx to LABEL=xxx
! would be interested in seeing that one
It runs to over 300 lines and includes another 100+ lines of include
Post your /etc/fstab here and I'll give you a much smaller script.
On Mon, 02 Sep 2019 07:10:21 -0400, Bit Twister<BitTwister@mouse-potato.com> wrote:
On Mon, 2 Sep 2019 12:33:46 +1000, faeychild wrote:
On 31/8/19 6:14 pm, Bit Twister wrote:
I have a script to change clean install's /etc/fstab
from UUID=xxx to LABEL=xxx
! would be interested in seeing that one
It runs to over 300 lines and includes another 100+ lines of include functions.
Post your /etc/fstab here and I'll give you a much smaller script.
Here's an old one that works. IIRC it's one that you posted sometime ago.
$ cat bin/uuidlabel.sh
#!/bin/bash
[[ $(whoami) != root ]] && echo "Must be root" && exit
[[ ! -r $1 ]] && echo "Can't read $1" && exit
cp /dev/null $1.new
while read line; do
if [[ "$line" == *UUID=* ]]; then
uuid1=${line#*UUID=}
uuid=${uuid1%%[[:blank:]]*}
dev=$(findfs UUID="$uuid")
labelarray=($(/sbin/blkid -o udev -s LABEL "$dev"))
echo labelarray[0]="${labelarray[0]}"
label="${labelarray[0]#*=}"
[[ -n "$label" ]] && line=${line//UUID=$uuid/LABEL=$label}
fi
echo $line >>$1.new
done < $1
On Mon, 2 Sep 2019 12:33:46 +1000, faeychild wrote:functions.
On 31/8/19 6:14 pm, Bit Twister wrote:
I have a script to change clean install's /etc/fstab
from UUID=xxx to LABEL=xxx
! would be interested in seeing that one
It runs to over 300 lines and includes another 100+ lines of include
Post your /etc/fstab here and I'll give you a much smaller script.
I am still reading and googling the 20b_rescue_cd_xx__grub script
20b_rescue_cd_xx__grub is my custom script. I created it by copying one
of the scripts in /etc/grub.d and used
https://www.gnu.org/software/grub/manual/grub.html
as reference.
Here's an old one that works. IIRC it's one that you posted sometime ago.
$ cat bin/uuidlabel.sh
#!/bin/bash
[[ $(whoami) != root ]] && echo "Must be root" && exit
[[ ! -r $1 ]] && echo "Can't read $1" && exit
cp /dev/null $1.new
while read line; do
if [[ "$line" == *UUID=* ]]; then
uuid1=${line#*UUID=}
uuid=${uuid1%%[[:blank:]]*}
dev=$(findfs UUID="$uuid")
labelarray=($(/sbin/blkid -o udev -s LABEL "$dev"))
echo labelarray[0]="${labelarray[0]}"
label="${labelarray[0]#*=}"
[[ -n "$label" ]] && line=${line//UUID=$uuid/LABEL=$label}
fi
echo $line >>$1.new
done < $1
Right!! Don't go there.
*******************
cat /etc/fstab
/dev/nvme0n1p2 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
UUID=ddce96e5-77d9-45dd-b1c7-4bf10d42fff7 /video ext4 noatime,acl 1 2 /dev/nvme0n1p3 swap swap defaults 0 0
*********************
Looking like you have not created the clean. testing partitions
and do not have a partition for hot backups.
I use the same value for mount point, Partition_Name, and Volume/Medialabel.
Setting Partition_Name makes using gfdisk a little more informative.
# gdisk -l /dev/sda
Number Start (sector) End (sector) Size Code Name
1 2048 83888127 40.0 GiB 8300 mga6
2 83888128 171864063 42.0 GiB 8300 mga5
3 171864064 257384447 40.8 GiB 8300 mga7
4 257384448 342192127 40.4 GiB 8300 cauldron
5 342192128 387309567 21.5 GiB 8300 local
6 387309568 434296831 22.4 GiB 8300 accounts
7 434296832 558874623 59.4 GiB 8300 misc
8 558874624 712286207 73.2 GiB 8300 spare
9 712286208 1471924223 362.2 GiB 8300 vmguest
10 1471924224 1471926271 1024.0 KiB EF02 bios_grub
11 1471926272 1562466303 43.2 GiB 8300 mga61
Ok, here is the script. save it, chmod +x it, and run it as user.
I will assume you have booted a rescue cd,
used gparted to Name Partitions and add a label if partitions
do not have a label or partition Name.
On 3/9/19 11:27 am, Bit Twister wrote:
Looking like you have not created the clean. testing partitions
and do not have a partition for hot backups.
Correct! not yet
I use the same value for mount point, Partition_Name, and Volume/Media label.
Setting Partition_Name makes using gfdisk a little more informative.
All good arguments
# gdisk -l /dev/sda
Number Start (sector) End (sector) Size Code Name
9 712286208 1471924223 362.2 GiB 8300 vmguest
10 1471924224 1471926271 1024.0 KiB EF02 bios_grub
11 1471926272 1562466303 43.2 GiB 8300 mga61
If bios_grub is your EFI partition then I could look towards reducing
the size of mine a little
Ok, here is the script. save it, chmod +x it, and run it as user.
I will assume you have booted a rescue cd,
used gparted to Name Partitions and add a label if partitions
do not have a label or partition Name.
No! Not yet.
********************
stream]$ ./fstab-label.sh* #********************************************************************
#* /etc/fstab
#* Created by ./fstab-label.sh Wed 04 Sep 17:03 2019
#*
#******************************************************************** /dev/nvme0n1p2 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2 UUID=ddce96e5-77d9-45dd-b1c7-4bf10d42fff7 /video ext4 noatime,acl 1 2 /dev/nvme0n1p3 swap swap defaults 0 0
#****************** end /etc/fstab ******************
You need to be root to actually overwrite /etc/fstab
removed '/home/faeychild/tmp/fstab-label.sh.tmp'
removed '/home/faeychild/tmp/fstab'
[faeychild@unimatrix stream]$
*************************
Stupid question.
If I change the partition names with gparted what
re-writes the fstab file to reflect the changes?
If any partition is formatted, I do not have to maintain the changed
UUID in fstab. Since I have a multi-boot install I do not have to modify
any of the other install's /etc/fstab.
On 31/8/19 6:14 pm, Bit Twister wrote:
If any partition is formatted, I do not have to maintain the changed
UUID in fstab. Since I have a multi-boot install I do not have to modify
any of the other install's /etc/fstab.
I read something about this a few months back. I may have remembered it wrong.
Firstly, swap is not a e2fs file system. Any commands you mention won't
work on swap.
Secondly, Bits mentions that changing a label will nuke the drive's file system.
That was what I was taught, but gparted will change the label
and leave your data intact. So long as you can unmount the drive, you
should be able to use gparted. I have never tried to change a disk that
is in use, or "busy."
If the drive already has a label, and you want to edit fstab to use that label instead of a UUID, go right ahead. fstab is read once on bootup,
and again if you use a command like "mount".
I would like you to post results from
sblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
please
If I change the partition names with gparted what
re-writes the fstab file to reflect the changes?
The biological software between keyboard and chair,
OS Software installer, or sys admin running a custom script. :)
Secondly, Bits mentions that changing a label will nuke the drive's file system. That was what I was taught, but gparted will change the label
On 4/9/19 6:02 pm, Bit Twister wrote:
~]$ lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
nvme0n1 119.2G
sda 5.5T
sdb 29.7G
sr0 1024M
`-sda1 5.5T ext4 /video
`-nvme0n1p4 12.2G ext4 /tmp /tmpRight click select Name Partition and set it tmp. click Apply,
`-sdb1 29.7G vfat
|-nvme0n1p1 299M vfat /boot/EFI
|-nvme0n1p2 44G ext4 /
|-nvme0n1p3 10.6G swap [SWAP] /swap
If I change the partition names with gparted what
re-writes the fstab file to reflect the changes?
The biological software between keyboard and chair,
OS Software installer, or sys admin running a custom script. :)
Oh God!! I thought it may have to he him :-)
On Thu, 5 Sep 2019 07:18:19 +1000, faeychild wrote:
On 4/9/19 6:02 pm, Bit Twister wrote:
~]$ lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
nvme0n1 119.2G
sda 5.5T
sdb 29.7G
sr0 1024M
`-sda1 5.5T ext4 /video
I would bet you have 5% of 5.5T as reserved blocks.
If it were I, I would boot the systemrescecd, click the third icon
bottom left. (gparted)
Right click /sda1, select Name Partition and set it video. click Apply,
Right click /sda1, select Label file system and set it video. click Apply
`-nvme0n1p4 12.2G ext4 /tmp /tmpRight click select Name Partition and set it tmp. click Apply,
Right click select Label file system and set it tmp. click Apply
`-sdb1 29.7G vfat
Here it would be D_vfat or C_vfat if using microsoft or whatever yousystem.
are storing there.
|-nvme0n1p1 299M vfat /boot/EFI
Here I would use boot_efi for Partition Name and maybe not Label file
Just not sure of the ramifications of mounting it in a EFI setup.
New kernel will update on the mount point. So we should not make
the mount point as boot_efi.
|-nvme0n1p2 44G ext4 /
Right click, select Name Partition and set it mga7. click Apply
Right click, select Label file system and set it mga7. click Apply
|-nvme0n1p3 10.6G swap [SWAP] /swap
Right click, select Name Partition and set it swap. click Apply
reboot and
lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
If looks good, run the fstab_changes script as user to see what would
happen.
lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
If looks good, run the fstab_changes script as user to see what would
happen.
I will probably find time this afternoon to trash everything.
regards
If it were I, I would boot the systemrescecd, click the third icon
bottom left. (gparted)
Right click /sda1, select Name Partition and set it video. click Apply,
Right click /sda1, select Label file system and set it video. click Apply
Also very importantly, Bits. How do you check the viability of the
backup? How do you know it will work when restored?
On 5/9/19 8:55 am, Bit Twister wrote:
On Thu, 5 Sep 2019 07:18:19 +1000, faeychild wrote:
On 4/9/19 6:02 pm, Bit Twister wrote:
~]$ lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
nvme0n1 119.2G
sda 5.5T
sdb 29.7G
sr0 1024M
`-sda1 5.5T ext4 /video
I would bet you have 5% of 5.5T as reserved blocks.
that is quite a lot of reserved space, Bits. Are you suggesting that it could be a lot smaller.
The 5.5 & disk is not going to fill up soon,
it's only junk and transient video flies being processed
On 5/9/19 8:55 am, Bit Twister wrote:
If it were I, I would boot the systemrescecd, click the third icon
bottom left. (gparted)
Right click /sda1, select Name Partition and set it video. click Apply,
Right click /sda1, select Label file system and set it video. click Apply
I booted system rescue and split the spare partition into approx 20+ gig sections named back_up-1 and back_up-2.
lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
nvme0n1 119.2G
sda 5.5T
sdb 29.7G
sr0 1024M
`-nvme0n1p6 28.6G ext2 back_up-2
`-sda1 5.5T ext4 /video
`-sdb1 29.7G vfat
|-nvme0n1p1 299M vfat /boot/EFI
|-nvme0n1p2 44G ext4 /
|-nvme0n1p3 10.6G swap [SWAP] /swap
|-nvme0n1p4 12.2G ext4 /tmp /tmp
|-nvme0n1p5 23.6G ext2 back_up-1
You may have noticed that I am wasting quite a lot of space on root.
The partition is 44G only 9G is used.
.
df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 29M 3.9G 1% /dev/shm
tmpfs 3.9G 1.2M 3.9G 1% /run
/dev/nvme0n1p2 44G 9.0G 32G 22% /
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/nvme0n1p4 12G 12G 227M 99% /tmp
/dev/nvme0n1p1 299M 136K 299M 1% /boot/EFI
/dev/sda1 5.5T 2.5T 2.7T 49% /video
tmpfs 794M 20K 794M 1% /run/user/1000
~]$ lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
nvme0n1 119.2G
sda 5.5T
sdb 29.7G
sr0 1024M
`-nvme0n1p6 28.6G ext2 back_up-2
`-sda1 5.5T ext4 /video
`-sdb1 29.7G vfat
|-nvme0n1p1 299M vfat /boot/EFI
|-nvme0n1p2 44G ext4 /
|-nvme0n1p3 10.6G swap [SWAP] /swap
|-nvme0n1p4 12.2G ext4 /tmp /tmp
|-nvme0n1p5 23.6G ext2 back_up-1
So I could revamp the whole drive, shrink the original root partition
and have several spare partitions.
I was really lazy when I first installed and the drama with EFI back
with M6 left me just glad to have anything running.
maybe it's time to get serious
I use rsync. It verifies what was written as it goes. No need to run
a second task to verify backup is valid.
The 5.5 & disk is not going to fill up soon,
it's only junk and transient video flies being processed
Hmmmm, I thought transient video flies being processed were done in /tmp since you had created a 12.2G ext4 /tmp partition.
I do not have a /tmp partition. My /tmp is just a sub directory under /
You need to format new partitions as ext4. They have journaling which improves reliability in the event partition/system goes down.
As root run
gdisk -l /dev/nvme0n1
and post just the
Number Start (sector) End (sector) Size Code Name
section.
On 5/9/19 6:12 pm, Bit Twister wrote:
I use rsync. It verifies what was written as it goes. No need to run
a second task to verify backup is valid.
Can you boot that backup to be sure?
As root run
gdisk -l /dev/nvme0n1
On 5/9/19 11:09 pm, faeychild wrote:
\I have been dinking around, Bits
lsblk -i -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
`-nvme0n1p6 2G ext4 sysres sysres
`-sda1 5.5T ext4 data /video data
|-nvme0n1p1 299M vfat /boot/EFI EFI
|-nvme0n1p2 22.3G ext4 MG7 / MG7
|-nvme0n1p3 10.6G swap [SWAP] /swap
|-nvme0n1p4 12.2G ext4 /tmp /tmp
|-nvme0n1p5 20.4G ext4 MG7_bu MG7_bu
On 5/9/19 11:09 pm, faeychild wrote:
\I have been dinking around, Bits
As root run
gdisk -l /dev/nvme0n1
On 6/9/19 3:34 pm, faeychild wrote:
On 5/9/19 11:09 pm, faeychild wrote:
\I have been dinking around, Bits
As root run
gdisk -l /dev/nvme0n1
Number Start (sector) End (sector) Size Code Name
1 2048 614433 299.0 MiB EF00 EFI
2 616448 47400959 22.3 GiB 8300 MG7
3 227776512 250068991 10.6 GiB 8200 swap
4 202270720 227776511 12.2 GiB 8300 tmp
5 47400960 90144767 20.4 GiB 8300 MG7_bu
6 198010880 202270719 2.0 GiB 8300 sysrescue
lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
nvme0n1 119.2G
sda 5.5T
sr0 1024M
└─nvme0n1p6 2G ext4 sysrescue sysrescue
└─sda1 5.5T ext4 data /video data
├─nvme0n1p1 299M vfat /boot/EFI EFI
├─nvme0n1p2 22.3G ext4 MG7 / MG7
├─nvme0n1p3 10.6G swap swap [SWAP] swap
├─nvme0n1p4 12.2G ext4 tmp /tmp tmp
├─nvme0n1p5 20.4G ext4 MG7_bu MG7_bu
your script run as user
]$ ./fstab-label.sh
./fstab-label.sh: line 75: PARTLABEL: unbound variable
Attempting to label EFI results in an endless run with gparted.
You did reference this in an earlier post.
Currently sysrescue doesn't work. I'm not surprised !!
and ran update-grub2.
It was not picked up by grub.
I tried setting boot flags on the partition also - no go.
The sysrescue page is well documented. I shall read the instructions
slowly with much coffee
On 6/9/19 3:34 pm, faeychild wrote:
I have copied the files from the sysrescue ISO
On 7/9/19 9:38 am, Bit Twister wrote:
I am getting an error when selecting sysrescue in grub menu. Bits
^^^^^^^^^^^^^^^^^^^
error: file "/isolinux/rescue64" not found
error: you need to load the kernel first
***********************
Well, shame on me for not testing that the latest rescue cd boots
with my custom grub script.
#**********************************************************************http://www.system-rescue-cd.org/manual/Installing_SystemRescueCd_on_the_disk/
#* 20b_rescue_cd_xx__grub - boots system rescue cd iso Version 1.0
#* Iso can be found on http://www.sysresccd.org/Main_Page
#*
#* Reference material:
#*
#* http://www.system-rescue-cd.org/manual/Booting_SystemRescueCd/whatever you want.
#*
#* Assumptions:
#* downloaded systemrescuecd iso is in the "/spare" partition
#* and the partition is labeled spare.
#* If not change the _iso_loc variable to your labeled location.
#*
#* You have either saved the downloaded iso and moved/copied
#* it to systemrescuecd.iso or just created a systemrescuecd.iso
#* to the downloaded iso.
#*
#* Install procedure:
#* save script in /etc/grub.d/ or set a link to actual location
#* chmod +x /etc/grub.d/20b_rescue_cd_xx__grub
#* and rebuild /boot/grub*/grub.cfg with
#* update-grub
#* or update-grub2 depending on your install
#*
#* Note: name of script dictates location in menu. Run
#* ls -1 /etc/grub.d/*_* to see menu selection order.
#*
#* This is free software released to public domain. Do with it
#*loop=/systemrescuecd.iso archisobasedir=sysresccd copytoram setkmap=us dostartx
#**********************************************************************
menuentry 'System Rescue ISO (64-bit) ' {
insmod regexp
insmod part_gpt
insmod ext2
_iso_loc=sysrescue
search --no-floppy --label $_iso_loc --set=root
for _fn in systemrescuecd*.iso ; do
_iso_fn=$_fn
done
loopback loop /$_iso_fn
echo 'Loading kernel ...'
linux (loop)/sysresccd/boot/x86_64/vmlinuz img_label=$_iso_loc
echo 'Loading initramfs ...'
initrd (loop)/sysresccd/boot/x86_64/sysresccd.img
}
#* cd /etc/grub.d/ ; make ; sleep 2 ; new_boot_logs
On 7/9/19 11:21 pm, Bit Twister wrote:
There is NO line wrapping in the actual script
exec tail -n +3 $0
#**********************************************************************
#* 20b_rescue_cd_xx__grub - boots system rescue cd iso Version 1.0
You missed the first line in your script "#!/bin/sh" .
Check this snippet.
#!/bin/sh
exec tail -n +3 $0 #**********************************************************************
#* 20b_rescue_cd_xx__grub - boots system rescue cd iso Version 1.0
On 8/9/19 9:20 am, Bit Twister wrote:
You missed the first line in your script "#!/bin/sh" .I cannot believe that I dropped that off!!!!
Check this snippet.
#!/bin/sh
exec tail -n +3 $0
#**********************************************************************
#* 20b_rescue_cd_xx__grub - boots system rescue cd iso Version 1.0
******************** It ran..
update-grub2
I now have two "20b_rescue_cd_xx__grub" entries in
/boot/grub2/grub.cfg with the different layouts.
I can delete the dud section later.
I now have two "20b_rescue_cd_xx__grub" entries in
/boot/grub2/grub.cfg with the different layouts.
Then I have to guess you have two rescue_cd_xx_ files in /etc/grub.d/.
There should only be one script.
If there is only one rescue_cd_xx script then my suggestion is delete
the rescue script in /etc/grub.d/ get a fresh copy,
set execute permission bit and run update-grub2 again.
On 8/9/19 7:39 pm, Bit Twister wrote:
I now have two "20b_rescue_cd_xx__grub" entries in
/boot/grub2/grub.cfg with the different layouts.
Then I have to guess you have two rescue_cd_xx_ files in /etc/grub.d/.
There should only be one script.
Replaced 20b_rescue_cd_xx__grub in grub.d with latest version.
grub.d]$ ls -l
total 72
-rwxr-xr-x 1 root root 8703 May 12 03:21 00_header*
-rwxr-xr-x 1 root root 236 May 12 03:21 01_users*
-rwxr-xr-x 1 root root 10594 May 12 03:22 10_linux*
-rwxrwxr-x 1 root root 2004 Sep 8 14:45 20b_rescue_cd_xx__grub*
-rwxr-xr-x 1 root root 10487 May 12 03:21 20_linux_xen*
-rwxr-xr-x 1 root root 2562 May 12 03:21 20_ppc_terminfo*
-rwxr-xr-x 1 root root 11817 May 12 03:21 30_os-prober*
-rwxr-xr-x 1 root root 218 May 12 03:21 40_custom*
-rwxr-xr-x 1 root root 220 May 12 03:21 41_custom*
-rw-r--r-- 1 root root 483 May 22 2015 README
If there is only one rescue_cd_xx script then my suggestion is delete
the rescue script in /etc/grub.d/ get a fresh copy,
set execute permission bit and run update-grub2 again.
Done!!
grep 'System Rescue' /boot/grub2/grub.cfg
menuentry 'System Rescue ISO (64-bit) ' {
*************************
ERROR mounting /dev/disk/by-lable/ to run/archiso/bootmnt
then waits 30 sec for /dev/disk/by-lable/
device did not show up fall back to prompt
sh can't access tty job control turned of
****************************
/dev/disk/by-lable/ does not look good, Bits
Hmmmmm, other than hardware and iso location, the iso works for both
of us. That leaves the iso location partition name as the last suspect
it this Who Done It mystery.
If your sysresccd.iso is a /sysresccd partition, then you need to
change the partition name and label to something like sysRcd and
update /etc/fstab and _iso_loc in 20b_rescue_cd_xx__grub and run
update-grub2
Oh, yeah, I do not know if you also removed the files you had copied
off the .iso or not. All I have on my system is the iso
On 9/9/19 7:30 am, Bit Twister wrote:
Hmmmmm, other than hardware and iso location, the iso works for both
of us. That leaves the iso location partition name as the last suspect
it this Who Done It mystery.
Correct
If your sysresccd.iso is a /sysresccd partition, then you need to
The "systemrescuecd-6.0.3.iso" is on the sysrescue partition
change the partition name and label to something like sysRcd and
update /etc/fstab and _iso_loc in 20b_rescue_cd_xx__grub and run
update-grub2
I'll try that a bit laterr
Oh, yeah, I do not know if you also removed the files you had copied
off the .iso or not. All I have on my system is the iso
Yes They're gone. Only systemrescuecd-6.0.3.iso now.
Sysrescue partition is not listed in fstab and not mounted/mounting -
should it be?
On Mon, 9 Sep 2019 08:04:01 +1000, faeychild wrote:
On 9/9/19 7:30 am, Bit Twister wrote:
Hmmmmm, other than hardware and iso location, the iso works for both
of us. That leaves the iso location partition name as the last suspect
it this Who Done It mystery.
Ah, hopefully you followed my instructions, and created a soft link as indicated in my new/improved script.
On 9/9/19 11:48 am, faeychild wrote:
A new approach
Similar
I have followed the systemrescuecd page instructions
A slightly different script and a different position for
systemrescuecd.iso -- in /boot.
On 8/9/19 7:39 pm, Bit Twister wrote:
<snip>I now have two "20b_rescue_cd_xx__grub" entries in
/boot/grub2/grub.cfg with the different layouts.
Then I have to guess you have two rescue_cd_xx_ files in /etc/grub.d/.
There should only be one script.
-rwxrwxr-x 1 root root 2004 Sep 8 14:45 20b_rescue_cd_xx__grub*
*************************
ERROR mounting /dev/disk/by-lable/ to run/archiso/bootmnt
then waits 30 sec for /dev/disk/by-lable/
device did not show up fall back to prompt
sh can't access tty job control turned of ****************************
/dev/disk/by-lable/ does not look good, Bits
Reagards
On Mon, 09 Sep 2019 07:00:03 +1000, faeychild wrote:
On 8/9/19 7:39 pm, Bit Twister wrote:
<snip>I now have two "20b_rescue_cd_xx__grub" entries in
/boot/grub2/grub.cfg with the different layouts.
Then I have to guess you have two rescue_cd_xx_ files in /etc/grub.d/.
There should only be one script.
-rwxrwxr-x 1 root root 2004 Sep 8 14:45 20b_rescue_cd_xx__grub*
*************************
ERROR mounting /dev/disk/by-lable/ to run/archiso/bootmnt
then waits 30 sec for /dev/disk/by-lable/
device did not show up fall back to prompt
sh can't access tty job control turned of ****************************
/dev/disk/by-lable/ does not look good, Bits
Reagards
Odd question: "/dev/disk/by-lable
There is a typo somewhere. /dev/disk/by-label might work better.
A slightly different script and a different position for
systemrescuecd.iso -- in /boot.
Do have fun, I used the same page to get my script to run.
Do keep in mind,
requires you to have a partition labeled boot.
On 9/9/19 7:54 pm, Bit Twister wrote:
Do keep in mind,
http://www.system-rescue-cd.org/manual/Installing_SystemRescueCd_on_the_disk/ >> requires you to have a partition labeled boot.
Mine didn't
search --no-floppy --label boot --set=root
Do have fun, I used the same page to get my script to run.
Do keep in mind,
requires you to have a partition labeled boot.
On Tue, 10 Sep 2019 07:44:49 +1000, faeychild wrote:error this didn't refer to boot
On 9/9/19 7:54 pm, Bit Twister wrote:
Do keep in mind,
http://www.system-rescue-cd.org/manual/Installing_SystemRescueCd_on_the_disk/ >>> requires you to have a partition labeled boot.
Mine didn't
Nope, no gold star for you. :)or in your script the variable $_iso_loc
search --no-floppy --label boot --set=root
The above line instructs grub to scan all partitions on all media,
except floppy, for a partition containing the label "boot"
https://www.gnu.org/software/grub/manual/grub/grub.html#search
The page says to copy the ISO into /boot and not just a partition named
boot.
And every installation has "/boot"
Not that it works anyway.. How well tested was this instruction.
Re your soft link, Bits
How does installing the ISO directly or using a link make any difference??
On Tue, 10 Sep 2019 08:02:20 +1000, faeychild wrote:not.
And every installation has "/boot"
And grub will find it if /boot is in a partition labeled "boot". Yours is
The label of the partition where /boot is on your system is MGA7
On Mon, 9 Sep 2019 18:17:55 -0500, Bit Twister wrote:
And grub will find it if /boot is in a partition labeled "boot". Yours is not.
The label of the partition where /boot is on your system is MGA7
You would have to have the iso in / and set img_label=MGA7
I renamed the "sysrescue" partition to "boot"
Copied the "sysrescuecd.iso" into "boot"
I updated grub with the systemrescue 25_rescue_cd_grub file.
It worked.
I don't understand why other set up failed
I don't know why I failed with your version.
On Tue, 10 Sep 2019 15:49:50 +1000, faeychild wrote:
I renamed the "sysrescue" partition to "boot"
Copied the "sysrescuecd.iso" into "boot"
Just to keep Murphy out of the loop, I would not be using "boot" as
a partition label.
Entirely possible that will bite you down the road at some point.
Question, does yours boot into graphical screen or do you have to
enter startx?
You take a rest now. :-)
On Wed, 11 Sep 2019 08:02:47 +1000, faeychild wrote:
You take a rest now. :-)
Which gets us back to the fstab_changes script.
Which gets us back to the fstab_changes script.
Ah Ha !
My current fstab was manually edited when dinking around with rescue grub.
cat /etc/fstab
#/dev/nvme0n1p2 / ext4 noatime,acl 1 1
LABEL=MG7 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
#/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2
LABEL=tmp /tmp ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
#UUID=ddce96e5-77d9-45dd-b1c7-4bf10d42fff7 /video ext4 noatime,acl 1 2\ LABEL=data /video ext4 noatime,acl 1 2
#/dev/nvme0n1p3 swap swap defaults 0 0
LABEL=swap swap swap defaults 0 0
/tmp and EFI are the partitions still not labeled.
Should we continue?
On 11/9/19 8:27 am, Bit Twister wrote:
On Wed, 11 Sep 2019 08:02:47 +1000, faeychild wrote:
You take a rest now. :-)
Which gets us back to the fstab_changes script.
Ah Ha !
My current fstab was manually edited when dinking around with rescue grub.
cat /etc/fstab
#/dev/nvme0n1p2 / ext4 noatime,acl 1 1
LABEL=MG7 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
#/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2
LABEL=tmp /tmp ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
#UUID=ddce96e5-77d9-45dd-b1c7-4bf10d42fff7 /video ext4 noatime,acl 1 2\
LABEL=data /video ext4 noatime,acl 1 2
#/dev/nvme0n1p3 swap swap defaults 0 0
LABEL=swap swap swap defaults 0 0
/tmp and EFI are the partitions still not labeled.
Should we continue?
On 11/9/19 11:42 am, faeychild wrote:
/tmp and EFI are the partitions still not labeled.
Should we continue?
On Wed, 11 Sep 2019 15:04:12 +1000, faeychild wrote:
On 11/9/19 11:42 am, faeychild wrote:
/tmp and EFI are the partitions still not labeled.
Should we continue?
Why not, someone may come along and want a working copy. :)
On 11/9/19 8:54 pm, Bit Twister wrote:
On Wed, 11 Sep 2019 15:04:12 +1000, faeychild wrote:
On 11/9/19 11:42 am, faeychild wrote:
/tmp and EFI are the partitions still not labeled.
Should we continue?
Why not, someone may come along and want a working copy. :)
A phenomenal script, Bits
On Wed, 11 Sep 2019 22:53:54 +1000, faeychild wrote:
On 11/9/19 8:54 pm, Bit Twister wrote:
A phenomenal script, Bits
It's not bad, but after finding your fstab bug I've improved
it to catch an unknown device entry.
Attempting to label EFI results in an endless run with gparted.
You did reference this in an earlier post.
On Wed, 11 Sep 2019 08:50:35 -0500, Bit Twister wrote:
On Wed, 11 Sep 2019 22:53:54 +1000, faeychild wrote:
On 11/9/19 8:54 pm, Bit Twister wrote:
A phenomenal script, Bits
It's not bad, but after finding your fstab bug I've improved
it to catch an unknown device entry.
Please provide a copy of the following output.
lsblk -io NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT,LABEL,PARTLABEL
On 12/9/19 12:06 am, Bit Twister wrote:
On Wed, 11 Sep 2019 08:50:35 -0500, Bit Twister wrote:
On Wed, 11 Sep 2019 22:53:54 +1000, faeychild wrote:
On 11/9/19 8:54 pm, Bit Twister wrote:
A phenomenal script, Bits
LABEL=MG7 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
|-nvme0n1p1 299M part vfat /boot/EFI EFI
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev ; echo rtn=$?
blkid -o value -s PARTLABEL $_dev ; echo rtn=$?
|-nvme0n1p1 299M part vfat /boot/EFI EFI
Did you know, you can add noauto to fstab for any partitions you
do not want mounted during boot. Example:
/dev/nvme0n1p1 /boot/EFI vfat noauto,umask=000,iocharset=utf8 0 0
if you add users, users can mount the partition.
`-nvme0n1p6 2G part ext4 boot boot
I suggest that should be something like boot_iso.
As a rule, I never label/name a partition with something I do not want
as a mount point.
On 12/9/19 10:38 am, Bit Twister wrote:
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev ; echo rtn=$?
blkid -o value -s PARTLABEL $_dev ; echo rtn=$?
[root@unimatrix ~]# _dev=/dev/nvme0n1p1
[root@unimatrix ~]# blkid -o value -s LABEL $_dev ; echo rtn=$?
rtn=0
[root@unimatrix ~]# blkid -o value -s PARTLABEL $_dev ; echo rtn=$?
EFI
rtn=0
Thunderbird is indenting each entry and the page is running off the
right hand side of the panel.
I may have to start a new thread or find Thunderbird's switch.
On Thu, 12 Sep 2019 16:56:33 +1000, faeychild wrote:user.
On 12/9/19 10:38 am, Bit Twister wrote:
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev ; echo rtn=$?
blkid -o value -s PARTLABEL $_dev ; echo rtn=$?
[root@unimatrix ~]# _dev=/dev/nvme0n1p1
[root@unimatrix ~]# blkid -o value -s LABEL $_dev ; echo rtn=$?
rtn=0
[root@unimatrix ~]# blkid -o value -s PARTLABEL $_dev ; echo rtn=$?
EFI
rtn=0
Heheh, ah, Murphy is at it again. I expected you to run the commands as
Do not need the return code so as a user, run
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev
blkid -o value -s PARTLABEL $_dev
On 12/9/19 6:18 pm, Bit Twister wrote:
I suppose I should put sbin is user path
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev
blkid -o value -s PARTLABEL $_dev
[faeychild@unimatrix ~]$ _dev=/dev/nvme0n1p1
[faeychild@unimatrix ~]$ /usr/sbin/blkid -o value -s LABEL $_dev [faeychild@unimatrix ~]$ /usr/sbin/blkid -o value -s PARTLABEL $_dev
EFI
On Thu, 12 Sep 2019 20:12:20 +1000, faeychild wrote:
On 12/9/19 6:18 pm, Bit Twister wrote:
I suppose I should put sbin is user path
Yeah, I put a .sh file in /etc/profile.d to add the sbin and other
locations to PATH for all users.
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev
blkid -o value -s PARTLABEL $_dev
[faeychild@unimatrix ~]$ _dev=/dev/nvme0n1p1
[faeychild@unimatrix ~]$ /usr/sbin/blkid -o value -s LABEL $_dev
[faeychild@unimatrix ~]$ /usr/sbin/blkid -o value -s PARTLABEL $_dev
EFI
Well I am stumped. commands were cut from the fstab_changes script and
they work from user terminal which means script should work.
Save this script, change _fn_in=/etc/fstab_new
then run it as root.
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev
blkid -o value -s PARTLABEL $_dev
[faeychild@unimatrix ~]$ _dev=/dev/nvme0n1p1
[faeychild@unimatrix ~]$ /usr/sbin/blkid -o value -s LABEL $_dev
[faeychild@unimatrix ~]$ /usr/sbin/blkid -o value -s PARTLABEL $_dev
EFI
Well I am stumped.
Save this script, change _fn_in=/etc/fstab_new
then run it as root.
Forgot to say cp /etc/fstab /etc/fstab_new before running script.
Heheh, ah, Murphy is at it again. I expected you to run the commands asuser.
Do not need the return code so as a user, run
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev
blkid -o value -s PARTLABEL $_dev
On Thu, 12 Sep 2019 04:18:25 -0400, Bit Twister<BitTwister@mouse-potato.com> wrote:
_dev=/dev/nvme0n1p1
blkid -o value -s LABEL $_dev
blkid -o value -s PARTLABEL $_dev
Just a reminder. From man cache ...
Note that blkid reads information directly from devices and for non-root users it returns cached unverified information.
Well I am stumped. commands were cut from the fstab_changes script and
they work from user terminal which means script should work.
Save this script, change _fn_in=/etc/fstab_new
then run it as root.
----8<----8<----8<----8<---cut below this line----8<----8<-8<
#!/bin/bash
#**************************************************************
#*
#* fstab_changes - change fstab to use labels Version 1.2
#*************** end fstab_changes ******************************
On 12/9/19 9:15 pm, Bit Twister wrote:
[root@unimatrix stream]# cat /etc/fstab_new #********************************************************************
#* /etc/fstab_new
#* Created by ./fstab_new.sh Fri 13 Sep 15:37 2019
#*
#******************************************************************** LABEL=MG7 / ext4 noatime,acl 1 1
PARTLABEL=EFI /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
LABEL=tmp /tmp ext4 noatime,acl 1 2
PARTLABEL=swap swap swap defaults 0 0
#****************** end /etc/fstab_new ******************
Some changes,Bits.. It looks neater than my mess.
On Fri, 13 Sep 2019 15:46:42 +1000, faeychild wrote:
On 12/9/19 9:15 pm, Bit Twister wrote:
[root@unimatrix stream]# cat /etc/fstab_new
#********************************************************************
#* /etc/fstab_new
#* Created by ./fstab_new.sh Fri 13 Sep 15:37 2019
#*
#********************************************************************
LABEL=MG7 / ext4 noatime,acl 1 1
PARTLABEL=EFI /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
LABEL=tmp /tmp ext4 noatime,acl 1 2
PARTLABEL=swap swap swap defaults 0 0
#****************** end /etc/fstab_new ******************
Some changes,Bits.. It looks neater than my mess.
You need to verify that all old fstab entries are in new fstab file.
For some reason your LABEL=data /video partition is not in new fstab. :-( Going to guess it is because of the backslash (\) on end of line 8
On 13/9/19 9:42 pm, Bit Twister wrote:
On Fri, 13 Sep 2019 15:46:42 +1000, faeychild wrote:
On 12/9/19 9:15 pm, Bit Twister wrote:
[root@unimatrix stream]# cat /etc/fstab_new
#********************************************************************
#* /etc/fstab_new
#* Created by ./fstab_new.sh Fri 13 Sep 15:37 2019
#*
#********************************************************************
LABEL=MG7 / ext4 noatime,acl 1 1
PARTLABEL=EFI /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
LABEL=tmp /tmp ext4 noatime,acl 1 2
PARTLABEL=swap swap swap defaults 0 0
#****************** end /etc/fstab_new ******************
Some changes,Bits.. It looks neater than my mess.
You need to verify that all old fstab entries are in new fstab file.
For some reason your LABEL=data /video partition is not in new fstab. :-(
Going to guess it is because of the backslash (\) on end of line 8
A bit of confusion,Bits
Should I be running your script on the original fstab with the
/dev/***** entries
My current fstab is a mishmash
cat /etc/fstab
#/dev/nvme0n1p2 / ext4 noatime,acl 1 1
LABEL=MG7 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
#/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2
LABEL=tmp /tmp ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
LABEL=data /video ext4 noatime,acl 1 2
#/dev/nvme0n1p3 swap swap defaults 0 0
LABEL=swap swap swap defaults 0 0
I have removed the line 8 with the trailing slash.
My morning will hopelessly interrupted so nothing will
On 13/9/19 9:42 pm, Bit Twister wrote:
You need to verify that all old fstab entries are in new fstab file.
For some reason your LABEL=data /video partition is not in new fstab. :-(
Going to guess it is because of the backslash (\) on end of line 8
A bit of confusion,Bits
Should I be running your script on the original fstab with the
/dev/***** entries
My current fstab is a mishmash
cat /etc/fstab
#/dev/nvme0n1p2 / ext4 noatime,acl 1 1
LABEL=MG7 / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /boot/EFI vfat umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
#/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2
LABEL=tmp /tmp ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
LABEL=data /video ext4 noatime,acl 1 2
#/dev/nvme0n1p3 swap swap defaults 0 0
LABEL=swap swap swap defaults 0 0
I have removed the line 8 with the trailing slash.
My morning will hopelessly interrupted so nothing will
On 14/9/19 6:36 pm, Bit Twister wrote:
current fstab
cat /etc/fstab
#/dev/nvme0n1p2 / ext4 noatime,acl 1 1
LABEL=mageia / ext4 noatime,acl 1 1
/dev/nvme0n1p1 /efi vfat users,noauto,umask=000,iocharset=utf8 0 0
none /proc proc defaults 0 0
#/dev/nvme0n1p4 /tmp ext4 noatime,acl 1 2
LABEL=tmp /tmp ext4 noatime,acl 1 2
# Entry for /dev/sda1 :
LABEL=video /video ext4 noatime,acl 1 2
#/dev/nvme0n1p3 swap swap defaults 0 0
LABEL=swap swap swap defaults 0 0
result from script
/dev/nvme0n1p1 /efi vfat users,noauto,umask=000,iocharset=utf8 0 0
lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL | sort -V
I spent some time this morning - early and uninterrupted - trying
different labels for the rescue partition.
It was interesting.
Editing both "grub.cfg" and the partition labels.
"boot" works, but "boot_iso and boot-iso and bootiso and sysrescue" don't.
Hmmm, when you are ready to start backing up into mageia_bu
start a new thread. Suggest How do I create a hot backup?.
I know I would not have the backup on the same device as source.
If device fails, you lose both :-(
change partition NAME and Label to "boot_iso" and fix fstab.
make the same changes in your /etc/grub.d/whatever_script_fn_here
that I show in grub.cnf
in grub.cnf you would have
search --no-floppy --label boot_iso --set=root
linux (loop)/sysresccd/boot/x86_64/vmlinuz img_label=boot_iso ......
lsblk -o NAME,SIZE,FSTYPE,LABEL,MOUNTPOINT,PARTLABEL
NAME SIZE FSTYPE LABEL MOUNTPOINT PARTLABEL
sda 5.5T
└─sda1 5.5T ext4 video /video video
sdb 29.7G
└─sdb1 29.7G vfat
├─nvme0n1p1 299M vfat efi
On Tue, 17 Sep 2019 07:39:24 +1000, faeychild wrote:
Go ahead and put partition name and label on /dev/sdb1
├─nvme0n1p1 299M vfat efi
and put a label "efi" on /dev/nvme0n1p1
And I can give you a script to automagically add any partitions to fstab where there is no fstab entry.
On 17/9/19 9:07 am, Bit Twister wrote:
On Tue, 17 Sep 2019 07:39:24 +1000, faeychild wrote:
Go ahead and put partition name and label on /dev/sdb1
sdb1 is a USB stick. It should have been pulled before lsblk was run.
├─nvme0n1p1 299M vfat efi
and put a label "efi" on /dev/nvme0n1p1
Gparted will not label efi. The progress bar cycles continually. Force
On Wed, 18 Sep 2019 07:27:59 +1000, faeychild wrote:
On 17/9/19 9:07 am, Bit Twister wrote:
On Tue, 17 Sep 2019 07:39:24 +1000, faeychild wrote:
Go ahead and put partition name and label on /dev/sdb1
sdb1 is a USB stick. It should have been pulled before lsblk was run.
Ok, go ahead and name/label it. :)
Now that is weird.
changed partition flag to efi (hfs), I think,
added/modified label and set name for the partition clicking Apply
at each step and was not able to hang gparted. I was using the
gparted installed on mga7, not the rescue disk.
If it were I on your system, i would
o load gparted on mga7,
o create a new partition,
o format it dos 16bit,
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 85:28:35 |
Calls: | 6,658 |
Files: | 12,203 |
Messages: | 5,333,708 |