Siduction Forum
Siduction Forum => Software - Support => Topic started by: hypper on 2014/09/02, 14:03:15
-
Hi,
gparted under KDE crashes before drives are shown. no errors are prompted in the terminal.
Any suggestions?
I started gparted from the terminal via sux.
btw, what does this mean:
sux
Passwort:
bash: Kann die Prozessgruppe des Terminals nicht setzen (-1).: Unpassender IOCTL (I/O-Control) für das Gerät
bash: Keine Job Steuerung in dieser Shell.
apt-cache policy gparted
gparted:
Installiert: 0.19.0-1+b1
Installationskandidat: 0.19.0-1+b1
Cheers
Mathias
-
I bet: You start it a second time, and it will not crash. This is how it "works" here. Don't know why.
Ahm, if I recall correctly, sux is broken, use kdesu/gksu instead, depending on your DE.
-
Right, sux is broken and will most probably never be fixed. There is suxterm, which works still.
greetz
devil
-
thanks. gparted starts now without problems.
but, when i am trying to format a 4 TB WD Elements external drive gparted still crashes while scanning the drive. the drive is formatted with ntfs and i can use it out of the box. but i want to format it with ext4.
i know, i can use fdisk (or maybe not since fdisk can only write partitions up to 2 TB), but i've never had any problems with gparted so far.
any suggestions what might be the problem and/or how can i format the 4 TB partition?
-
any suggestions what might be the problem and/or how can i format the 4 TB partition?
Yes, here are 2:
(1) Use a bootable Parted Magic live cd/usb stick, or
(2) Use mkfs.ext4 at the command line. ;)
-
hi,
(1) maybe i try parted magic, but since it is based on gparted it might also crash
i tried to check the partition table with parted
parted /dev/sdc
GNU Parted 3.2
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (3.2)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Command History:
print
Error: SEGV_MAPERR (Address not mapped to object)
Speicherzugriffsfehler
then i tried
file -s /dev/sdc
/dev/sdc: DOS/MBR boot sector
now i am not sure, if i can just run
(2) mkfs.ext4
since i thought i have to use the GUID Partition Table (GPT) for partitions larger than 2TB. On the other hand, i dont know how the drive has been formatted with ntfs to 4TB and dos/mbr.
-
Error: SEGV_MAPERR (Address not mapped to object)
Strange -- I googled that error and the first page of hits were all from 2006 - 2009. It seems they were trying to overcome the hard-coded 512 byte sector size. But I didn't see a recent hit. I haven't yet worked with a hdd >2GB, so I dunno. I would still try the Parted Magic Live stick, although he now charges a small fee for the ISO download. I have relied on that for years to work with hard drives.
-
here is the output of fdisk -l
Note: sector size is 4096 (not 512)
Disk /dev/sdb: 4000.8 GB, 4000752599040 bytes
255 heads, 63 sectors/track, 60799 cylinders, total 976746240 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xdb4bf07b
Device Boot Start End Blocks Id System
/dev/sdb1 256 976746239 3906983936 7 HPFS/NTFS/exFAT
it is a 4k sector size drive.
-
it is a 4k sector size drive.
Correct -- those are common now -- I have 2 hdds with 4096-byte sectors. But current (G)Parted should not have any problem with them just because of the sector size. There must be something else in your case.
-
Hello hypper,
you need GPT partitioning for disks > 2TB and fdisk isn't capable. Use gdisk instead.
GPT uses a protective pseudo MBR that claims "disk full, no free space left" to prevent use of old tools like fdisk.
I still can't explain why gparted segfaults with your disk. It should™ work -- at least in theory.
In my KDE system i can start gparted directly from the menu - and policykit will ask for root rights.
I attached a screenshot.
greetings
musca