|
dear Stan,
for move the storage also i have use a version of try from a program created by acronis who remove the threat,
sysimage has disappeared since the weekend so i have recreated the part sysimage,
neither chroot and chmod work thus if the SSD is uses encrypted have you a kind for repair that or does i need to use the SSD without encrypting ?
from what i remember sda1 is a windows ten GMAO fortunately i update this system only one time by year because Microsoft is a factory of money the more update live for become the system windows slow in addition i understand there are threats but as i was
say before a lot of update don't maker,
I need an advice because you say fedora use NTFS although i have set up each start of the setup firstly by UEFI secondly by CSM naturally may i force the setup to start each time only by NTFS ?
sda2 has never live anymore from the SSHDD and the advice for the file fstab can't work as i show below this explaining because the root /mnt/sysimage can be readen only by reading :
[liveuser@localhost-live ~]$ cat /mnt/sysimage/etc/fstab > /tmp/install-fstab.txt
cat: /mnt/sysimage/etc/fstab: Aucun fichier ou dossier de ce type
[liveuser@localhost-live ~]$ sudo cat /mnt/sysimage/etc/fstab > /tmp/install-fstab.txt
cat: /mnt/sysimage/etc/fstab: Aucun fichier ou dossier de ce type
[liveuser@localhost-live ~]$ sudo touch /mnt/sysimage/etc/fstab
touch: impossible de faire un touch '/mnt/sysimage/etc/fstab': Aucun fichier ou dossier de ce type
[liveuser@localhost-live ~]$ sudo mkdir /mnt/sysimage/etc/
mkdir: impossible de créer le répertoire « /mnt/sysimage/etc/ »: Système de fichiers accessible en lecture seulement
"ext4 is the older default, btrfs
is the newer one. Did fedora ever run from this drive? It shouldn't
be able to boot. How did you install?" i know few fedora all ext4 part can work even 2 terabyte of storage btrfs can use more of 2 terabyte
of storage ,
from what i remember sda1 is the part windows ten however sda2 has never leaven,
I never understood why you force myself to mount the pen USB this doesn't maker either you help myself
or you stop to help myself,
i ever ask previously but you answer to the step next so how to repair the problem of shell who happen
the bash doesn't live ?
mount dev/sda2 can't work because as i have ever say windows ten is only on dev/sda1,
i need an explaining for the power on of the pen USB thus as i was type previously before the start
of the pen USB with the graphic easy it ask either the first boot or the second boot finaly if you want and if you ask i launch two time the line of command smart who show whole parts for happening if fedora have one part root and one part home, right ?
thanks you in advance to help myself,
have a nice week,
regards.
Dorian ROSSE.
De : stan <upaitag@xxxxxxxx>
Envoyé : mardi 25 avril 2023 21:10 À : 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 Mon, 24 Apr 2023 16:27:28 +0000
Dorian ROSSE <dorianbrice@xxxxxxxxxx> wrote: > 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, How did you move to the new hard drive? It looks like it didn't preserve the existing layout on the old drive if both windows and fedora were working there. > > 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 : Yes, you can display on the screen, but you cannot redirect output to a file. Show the output of ls -nd /mnt/sysimage You want it to look like this: drwxr-xr-x. 2 0 0 4096 May 8 2022 /mnt/sysimage with different date. The says owner is root (0) and the owner has rwx permissions. So, after you have created the directory sysimage, run chmod 755 /mnt/sysimage Then when you create the chroot, root will be able to write things to the file system as it will be read write for root. > > [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 The above is the live system. > 80% / sda > ├─sda1 > │ vfat FAT32 8610-1067 > └─sda2 > ntfs fedora > 62C48A62C48A3875 This is an ntfs filesystem for fedora. fedora will be on ext4 or btrfs, depending on when it was installed. ext4 is the older default, btrfs is the newer one. Did fedora ever run from this drive? It shouldn't be able to boot. How did you install? Can you boot to the windows on this drive? I don't think it exists anymore. > sdb > └─sdb1 > vfat FAT32 FEDORA-WS-L > B099-D599 5,4G This drive is all windows formatted, so there is no fedora that I can see, and if this is the EFI partition it is using the whole disk. I would prefer the output of blkid, because it shows more information about the partitions. I don't think there is anything recoverable on these hard drives. After you have created the /mnt/sysimage directory read write, mount it as follows: mount /dev/sda2/ /mnt/sysimage Then run ls /mnt/sysimage Does it show the root directory of fedora? afs bin boot dev etc home lib lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var If it doesn't, there is no fedora left. If it does, you can run the commands like: cat /mnt/sysimage/etc/fstab > /tmp/install-fstab.txt Try the commands I gave before, but from the data you have provided so far, I think you are going to have to reinstall both windows and fedora, since it looks like both of them are gone. It might be possible to change the filesystem type on the fedora partition with a partition tool, from ntfs to ext4 or btrfs, whichever is correct. If grub is trying to read information written as ext4 or btrfs as ntfs, nothing is going to work. Have you made any changes to the disk information? You can install directly from the live system if fedora and windows are gone. |
_______________________________________________ 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
