|
dear stan,
the setup broken were wear two part for fedora either one root and one home in addtion the fat32 was a windows ten although fedora start with the pen USB unfortunately it start broken firstly the troubleshouting ask either one first boot nor one second boot
however it go back for start in easy displaying,
secondly if i want attach the part sdb1 i happen one error explaining by the shell who say that the system is readen only in read :
[liveuser@localhost-live ~]$ sudo mount /dev/sdb1 /mnt/sysimage
mount: /mnt/sysimage: ATTENTION: source protégée en écriture, montée en lecture seule.
I show the happening from one good line of command :
[liveuser@localhost-live ~]$ lsblk --fs
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
squash 4.0
loop1
ext4 1.0 Anaconda
2074eb84-624c-4790-83b6-8f3e4a82ae85
├─live-rw
│ ext4 1.0 Anaconda
│ 2074eb84-624c-4790-83b6-8f3e4a82ae85 1,4G 80% /
└─live-base
ext4 1.0 Anaconda
2074eb84-624c-4790-83b6-8f3e4a82ae85
loop2
└─live-rw
ext4 1.0 Anaconda
2074eb84-624c-4790-83b6-8f3e4a82ae85 1,4G 80% /
sda
├─sda1
│ vfat FAT32 8610-1067
└─sda2
ntfs fedora
62C48A62C48A3875
sdb
└─sdb1
vfat FAT32 FEDORA-WS-L
B099-D599 5,4G 27% /mnt/sysimage
/run/initra
mfs/live
zram0
[SWAP]
SDA1 was windows ten thus why it doesn't reach the start of the setup, right ?
the part vfat should be the part of the pen USB also why you ask to myself to mount the pen USB, right ?
it doesn't maker the setup because it seems lose the part home finaly does i need for start the pen USB choose the second boot of troubleshooting if it should be the part home who is better to give a back ?
if anybody has a good tutorial of page web for have the back of the three parts (fedora root with fedora home and windows ten) please yours help will have a good behaviour,
thanks you in advance for your help,
have a good week,
regards.
Dorian ROSSE.
De : stan <upaitag@xxxxxxxx>
Envoyé : dimanche 23 avril 2023 22:25
À : users@xxxxxxxxxxxxxxxxxxxxxxx <users@xxxxxxxxxxxxxxxxxxxxxxx>
Cc : Dorian ROSSE <dorianbrice@xxxxxxxxxx> Objet : Re: Broken by the grub startup after have move whole the system from one SSHDD more small to a SSD more big by a software acronis On Fri, 21 Apr 2023 13:59:38 +0000
Dorian ROSSE <dorianbrice@xxxxxxxxxx> wrote: First, the translation is much better. I was going to suggest one of https://deepl.com/translator or https://translate.google.com but it reads like you found a better one. I think there was a failure in our communication. The commands you ran below need to be done after the installed system is mounted. Otherwise, they only give information about the live system that you are booted into. I will tell you how to do that below, after some interspersed comments. > i paste below the inside from /etc/fstab : > > vartmp /var/tmp tmpfs defaults 0 0 This is from the live system. > > i attach in attachment /usr/sbin/blkid because the file is > misunderstood by the pen USB, > > now i paste below the happening of your advice df : > > [liveuser@localhost-live ~]$ df > Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur > devtmpfs 4096 0 4096 0% /dev > tmpfs 8117308 3356 8113952 1% /dev/shm > tmpfs 3246924 9824 3237100 1% /run > /dev/sdb1 7664800 2038132 5626668 27% > /run/initramfs/live /dev/mapper/live-rw 7712908 6192208 > 1504316 81% / tmpfs 8117312 16 8117296 > 1% /tmp vartmp 8117308 0 8117308 0% > /var/tmp tmpfs 1623460 132 1623328 1% > /run/user/1000 The above seems to be from the live system. What I need is the result from the installed system. It is a positive thing that it shows your installed system, so the information we are looking for will be available once you mount this partition. /dev/sdb1 7664800 2038132 5626668 27% If the above is all you have installed, there is no need to run df again. If you do run it on the installed system, you should only get the above line, I think. It might show the EFI partition, since that is separate, and a different filesystem, usually fat32. > below you will read the happening of your list from > /boot/loader/entries : > > [liveuser@localhost-live ~]$ sudo ls -n /boot/loader/entries > total 8 > -rw-r--r--. 1 0 0 442 13 avril 17:49 > f6fe47dfbe174a2b98acdafe136e1959-0-rescue.conf -rw-r--r--. 1 0 0 362 > 13 avril 17:47 > f6fe47dfbe174a2b98acdafe136e1959-6.2.9-300.fc38.x86_64.conf Again, this is from the live system, so does not help with troubleshooting. The installed system will look similar. > > so the list in boot below : > > [liveuser@localhost-live ~]$ sudo ls -n /boot > total 53880 > -rw-r--r--. 1 0 0 255900 29 mars 20:00 config-6.2.9-300.fc38.x86_64 > drwx------. 4 0 0 4096 13 avril 17:47 efi > drwx------. 3 0 0 4096 21 avril 09:33 grub2 > -rw-------. 1 0 0 32251854 13 avril 17:52 > initramfs-6.2.9-300.fc38.x86_64.img drwxr-xr-x. 3 0 0 4096 13 > avril 17:46 loader lrwxrwxrwx. 1 0 0 45 13 avril 17:47 > symvers-6.2.9-300.fc38.x86_64.gz -> > /lib/modules/6.2.9-300.fc38.x86_64/symvers.gz -rw-------. 1 0 0 > 8429627 29 mars 20:00 System.map-6.2.9-300.fc38.x86_64 -rwxr-xr-x. 1 > 0 0 14215976 29 mars 20:00 vmlinuz-6.2.9-300.fc38.x86_64 Again, this is from the live system, so does not help with troubleshooting. The installed system will look similar. > /etc/default/grub is unfound by the pen USB : > > [liveuser@localhost-live ~]$ sudo cat /etc/default/grub > cat: /etc/default/grub: Aucun fichier ou dossier de ce type > [liveuser@localhost-live ~]$ less /etc/default/grub > /etc/default/grub: Aucun fichier ou dossier de ce type Again, this is from the live system, so does not help with troubleshooting. The live USB doesn't use grub, it seems. It should look something like: $ cat /etc/default/grub GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=false GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true And the blkid output was binary and didn't look like it was valid when I examined it. I presume that it was like that because it was also from the live system. Output from blkid should look like this: /dev/sda4: LABEL="root1" UUID="fb6b3e13-20d8-445f-b25a-c8a05a4c842f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6d8baf7c-14e7-4496-926a-8882715415ba" with a line for every partition on the installed system. Probably only one on your system, but maybe one for the EFI partition. Here are some better instructions. When the live system is running do an ls /mnt Is there a directory called sysimage in the output? Yes, next step. No, create a directory under mnt. mkdir /mnt/sysimage Mount the installed system on the new directory. mount /dev/sdb1 /mnt/sysimage If there is an error from this command, there is no point in going further. Stop, and send the error you got. You can try looking in man mount to see if you can fix the error yourself. If the command finished successfully, you can do an ls /mnt/sysimage This should give you a listing of your installed system root partition, /dev/sdb1 7664800 2038132 5626668 27% $ ls / afs bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var If it does, then next step. Doesn't, no point in continuing. Post the output of the command here. Make the installed system the root system, so you will be in it as if it was running, sort of. You will be able to edit and examine all the files. chroot /mnt/sysimage Run all the commands you ran above in the installed system. They will give the data we need to troubleshoot your system. The command less is handy for looking at files, read only. cat prints the contents of a file. I use vim as an editor, but you probably want to use a simpler editor. Fedora provides one called nano. You use exit to leave the chroot environment. Waiting for your data so we can get you running with your installed system. |
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
