Segmentation fault

[Valery Sch]

I'v installed Alt-F on DNS-320L.

Did not notice immediately, or after some of my actions there was an error.

When runing a fdisk in ssh session, I get

info about partitions on /dev/sda and

Segmentation fault

No info about /dev/sdbsdb

Both disks have GPT parts.

 I tried to delete all packages and reflash Alt-F.

The error did not disappear

When I run fdisk under debian chroot, all is ok.

Is this a  bug, or a consequence of my wrong actions?

[João Cardoso]

On Wednesday, 1 August 2018 17:28:08 UTC+1, Valery Sch wrote:

I'v installed Alt-F on DNS-320L.

Did not notice immediately, or after some of my actions there was an error.

When runing a fdisk in ssh session, I get

info about partitions on /dev/sda and

Segmentation fault

No info about /dev/sdbsdb

You have to supply more details, such as the actual commands used and its output:

[root@DNS-325]# fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes

255 heads, 63 sectors/track, 121601 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System

/dev/sda1               1          66      530113+ 82 Linux swap

/dev/sda2             131      121601   975715807+ da Unknown

/dev/sda4              67         130      514080  83 Linux

Partition table entries are not in disk order

[root@DNS-325]# 

[Valery Sch]

среда, 1 августа 2018 г., 19:56:44 UTC+2 пользователь João Cardoso написал:

.....

You have to supply more details, such as the actual commands used and its output:

[root@DNS-325]# fdisk -l /dev/sda

...

Sorry, in the wrong place answered.

Of course I ran

fdisk -l

and got Segmentation fault

Found valid GPT with protective MBR; using GPT

Disk /dev/sda: 3907029168 sectors, 3726M
Logical sector size: 512
Disk identifier (GUID): a9860f1d-bf3a-4923-a4ff-09be68ddfcda
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134

   Device  Start (sector)    End (sector)  Size (sectors)   Code  Name
/dev/sda1            2048         1050623         1048576   8200  Linux swap
/dev/sda2         3147776      3904929899      3901782124   0700  Linux/Windows data
/dev/sda3      3904931840      3907029134         2097295   0700  Linux/Windows data
/dev/sda4         1050624         3147775         2097152   0700  Linux/Windows data
Segmentation fault

 

[Hooligan99]

 I also appear to have this issue. DNS-320L-Ax. All the drives were set up fresh (i.e. not imported from anything).

Bay	Dev.	Model	Capacity	Power Status	Temp	Health
left	sda	ST3000DM007-1WY10G	3.0TB	--	33°C/91°F	passed
right	sdb	WDC WD15EADS-00P8B0	1.5TB	active or idle	41°C/105°F	passed
usb	sdc	USB Flash Disk	15.7GB	--	--	--

[root@FileSRV02]# fdisk -l
fdisk: device has more than 2^32 sectors, can't use all of them

Found valid GPT with protective MBR; using GPT

Disk /dev/sda: 4294967295 sectors, 4095M
Logical sector size: 512
Disk identifier (GUID): ae70d2c2-6197-4053-9780-bcae8cfe37c6

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 5860533134

   Device  Start (sector)    End (sector)  Size (sectors)   Code  Name

/dev/sda1              64         1156311         1156248   8200
/dev/sda2         1156312      5860531311      5859375000   8300
Segmentation fault

[root@FileSRV02]# sfdisk -uS -l

Disk /dev/sda: 97451 cylinders, 255 heads, 63 sectors/track
Warning: The partition table looks like it was made
  for C/H/S=*/256/63 (instead of 97451/255/63).
For this listing I'll assume that geometry.
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sda1             1         - 4294967295  ee  Intel EFI GUID Partition Table
/dev/sda2             0         -          0   0  Empty
/dev/sda3             0         -          0   0  Empty
/dev/sda4             0         -          0   0  Empty

Disk /dev/sdb: 182401 cylinders, 255 heads, 63 sectors/track
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sdb1            64   1060607    1060544  82  Linux swap
/dev/sdb2       1060608 2930272063 2929211456  83  Linux
/dev/sdb3             0         -          0   0  Empty
/dev/sdb4             0         -          0   0  Empty

Disk /dev/sdc: 15000 cylinders, 64 heads, 32 sectors/track
Warning: The partition table looks like it was made
  for C/H/S=*/255/63 (instead of 15000/64/32).
For this listing I'll assume that geometry.
Units = sectors of 512 bytes, counting from 0

   Device Boot    Start       End   #sectors  Id  System
/dev/sdc1   *        63  30719999   30719937  83  Linux
/dev/sdc2             0         -          0   0  Empty
/dev/sdc3             0         -          0   0  Empty
/dev/sdc4             0         -          0   0  Empty
[root@FileSRV02]#

[Valery Sch]

четверг, 2 августа 2018 г., 13:32:03 UTC+2 пользователь Hooligan99 написал:

 I also appear to have this issue. DNS-320L-Ax. All the drives were set up fresh (i.e. not imported from anything).

[root@FileSRV02]# sfdisk -uS -l

--

Thanks

sfdisk works fine too on my box.
I was only interested is the bug only on my box, or so it should be

Is it possible Segmentation fault will pop out on other programs?

Typically, segmentation errors depend on the used libraries.

And further.
fdisk in debian chroot works as it should

In debian fdisk is full-fledged program, but in main system it is a part of busybox.

[João Cardoso]

I can reproduce the issue only on a GPT partitioned disk and when not specifying the device; otherwise it works ok.

It probably comes from my patches to busybox fdisk, in order to support GPT, package/busybox/busybox-1.20.2-fdisk_gpt.c.patch in the sources.

OK, no segfault:

[root@DNS-320L]# fdisk -l /dev/sda

Found valid GPT with protective MBR; using GPT

Disk /dev/sda: 156301488 sectors,  149M

Logical sector size: 512

Disk identifier (GUID): 6c22118f-64bf-444c-b539-82045ac95ce7

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 156301454

   Device  Start (sector)    End (sector)  Size (sectors)   Code  Name

/dev/sda1              64         1048639         1048576   8200  Linux swap

/dev/sda2         1048640        40111135        39062496   8300  Linux filesystem

/dev/sda3        40111136        79173631        39062496   8300  Linux filesystem

/dev/sda4        79173632       155345503        76171872   8e00  Linux LVM

Now generate a segfault:

[root@DNS-320L]# fdisk -l

Found valid GPT with protective MBR; using GPT

Disk /dev/sda: 156301488 sectors,  149M

Logical sector size: 512

Disk identifier (GUID): 6c22118f-64bf-444c-b539-82045ac95ce7

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 156301454

   Device  Start (sector)    End (sector)  Size (sectors)   Code  Name

/dev/sda1              64         1048639         1048576   8200  Linux swap

/dev/sda2         1048640        40111135        39062496   8300  Linux filesystem

/dev/sda3        40111136        79173631        39062496   8300  Linux filesystem

/dev/sda4        79173632       155345503        76171872   8e00  Linux LVM

Segmentation fault

Valery, this is the reason why it is important to fully report the command used. I would ignore your report as I couldn't reproduce it if Holligan hadn't confirm it.

I will file in a bug report for this

Thanks

[Valery Sch]

четверг, 2 августа 2018 г., 17:11:21 UTC+2 пользователь João Cardoso написал:

I can reproduce the issue only on a GPT partitioned disk and when not specifying the device; otherwise it works ok.

It probably comes from my patches to busybox fdisk, in order to support GPT, package/busybox/busybox-1.20.2-fdisk_gpt.c.patch in the sources.

...

Valery, this is the reason why it is important to fully report the command used. I would ignore your report as I couldn't reproduce it if Holligan hadn't confirm it.

I will file in a bug report for this

Thanks

--

Well. Thanks.
I've calmed down.
Since I was manipulating whith libs, I suspected that the error
could have arisen because of my wrong actions.

One of them:

I'v compiled the truecrypt-7.1a  under Debian chroot and moved it along with some libraries to the main system.

For its operability, I added a number of links to libraries in /lib and /opt/lib.