I am facing an issue with Gparted currently. When I start it, it just shows loading, but will never finish.
After killing the process and starting via terminal it shows:
Unit \xe2\x97\x8f.service does not exist, proceeding anyway.
Unit \xe2\x97\x8f.service does not exist, proceeding anyway.
Unit \xe2\x97\x8f.service does not exist, proceeding anyway.
Unit \xe2\x97\x8f.service does not exist, proceeding anyway.
Unit \xe2\x97\x8f.service does not exist, proceeding anyway.
Unit \xe2\x97\x8f.service does not exist, proceeding anyway.
GParted 1.1.0
configuration --enable-libparted-dmraid --enable-online-resize
libparted 3.3
And then stucks
A little background:
I am currently playing with a lot of distributons to decide which one I would like to use instead of Windows. I have installed Manjaro, EndeavorOS, Ubuntu and Debian on 2 partitions over and over, to play with them.
I concluded with Manjaro and Debian for a longer test and because they seemed to be the most promising ones. But because I âdeletedâ my first Manjaro install for Ubuntu I needed to reinstall it.
in the old install Gparted worked totally fine, but in the new install it doesnât. I am basically on a fresh install, besides the system update, so I have no idea, why this is happening.
and post some more information so we can see whatâs really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin liesâŚ
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information⌠(Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
The output to sudo parted --list and sudo blkid would be appreciated as well.
Would a complete nuke initialisation of your entire HDD be an option as a solution?
P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment youâre using, which CPU/GPU you have, âŚ
unfortunately sudo parted --list doesnât do a lot. While writing this comment the output was
ď î° ď ~ î° sudo parted --list î˛ â
Modell: ATA OCZ-AGILITY3 (scsi)
Festplatte /dev/sda: 60,0GB
SektorgrĂśĂe (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags:
Nummer Anfang Ende GrĂśĂe Dateisystem Name Flags
1 1049kB 29,7GB 29,7GB ext4 boot, esp
2 29,7GB 60,0GB 30,4GB ext4 debian boot, esp
Warnung: Fehler beim Abgleich oder SchlieĂen von /dev/sdb1:
Eingabe-/Ausgabefehler
Wiederholen/Retry/Ignorieren/Ignore?
Which is only the content of the SSD (connected via eSATA)I am currently using to test the distributions.
sda1 & sda2
(I guess it suffers a similar problem like gparted, that there seems to be an issue to access the drives at all)
The HDD currently consists of the Windows 10 OS partititon (sdb1), the Swap partition (sdb2) and an unused ext4 partition (that isnât shown at all in the inxi output).
Also I needed to add the swap partition manually in the fstab, because it wasnât recognised automatically.
Currently I have the feeling, that the issue might be a hardware one and that the HDD might be faulty. So now I am checking how to move the Windows OS partition to my 2nd HDD drive (that contains mainly my data files) and would have still enough space to contain the Windows OS part.
This was the midterm plan either way, but I was just wandering why Manjaro did recognise the drive in the first try without issue (and Debian still does). Mainly to understand and get better at Linux.
Of course nuking is always an option (as long as I can preserve the current Windows installation, or at least made a backup of my userdata (due to tax programms, etcâŚ))
Maybe I will try to make a fresh installation, or start one more time with the live DVD to check if gparted works there.
Yeah, I will spend some time to update my profile.
first of all thank you very much for your help. I really appreciate it.
Today I tried a fresh install and noticed following.
From the live DVD, gParted works without any issue. All drives are recognised without any delay.
After the installation is finished and the system is rebooted, all packages updated (but even without the update), gparted runs into the same problem as before and stucks at âAlle Laufwerke werden abgefragtâ â All drives are scanned/queried
After I installed smartctl the output is following
ď î° ď ~ î° sudo smartctl --all -d ata -T permissive /dev/sdb î˛ â
[sudo] password for brotsalami:
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.9.16-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: Input/output error
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: [No Information Found]
Local Time is: Tue Feb 9 09:35:27 2021 CET
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
ď î° ď ~ î° sudo smartctl --all -d sat -T permissive /dev/sdb î˛ 6 â î˛ 6s ď
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.9.16-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error aborted command
=== START OF INFORMATION SECTION ===
Device Model: [No Information Found]
Serial Number: [No Information Found]
Firmware Version: [No Information Found]
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: [No Information Found]
Local Time is: Tue Feb 9 09:35:36 2021 CET
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
ď î° ď ~ î°
I needed to add -d ata/-d sat and -T permissive as arguments, as otherwise it showed even less.
I will reboot now and execute the same on the Debian system, to check if it works there. Hang on a minute.
I think I fixed it. I went into my BIOS and checked the settings of the HDDs there.
I noticed that one of the settings was set to IDE, instead of AHCI, so I changed that.
After the reboot, now GParted works as expected.
So thank you very much. It was just a normal âdaUâ
As you know german you should understand.
Iâve marked this answer as the solution to your question as it is by far the best answer youâll get.
However, if you disagree with my choice, please feel free to take any other answer as the solution to your question or even remove the solution altogether: You are in control! (If you disagree with my choice, just send me a personal message and explain why I shouldnât have done this or or if you agree)
P.S. In the future, please donât forget to come back and click the 3 dots below the answer to mark a solution like this below the answer that helped you most:
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the âsolvedâ status.