Segmentation fault

Using PhotoRec to recover lost data
Message
Author
hawkeyenl
Posts: 3
Joined: 11 Apr 2015, 20:35

Segmentation fault

#1 Post by hawkeyenl » 11 Apr 2015, 20:43

Hi,

I'm running photorec 7.0-WIP on my Synology DS211+. However, shortly after starting, it stops with a message 'segmentation fault (core dumped)'. Any thoughts on why this is happening?

Sponsored links

User avatar
cgrenier
Site Admin
Posts: 3626
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Segmentation fault

#2 Post by cgrenier » 11 Apr 2015, 22:07

Run "gdb photorec" (replace photorec by the exact filename) and type "run".
It may tell you what the problem is: kernel too old, mismatching architecture...

hawkeyenl
Posts: 3
Joined: 11 Apr 2015, 20:35

Re: Segmentation fault

#3 Post by hawkeyenl » 11 Apr 2015, 22:20

I'm affraid my NAS doesn't understand this command : 'gdb: not found'

User avatar
cgrenier
Site Admin
Posts: 3626
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Segmentation fault

#4 Post by cgrenier » 12 Apr 2015, 11:05

Try "dmesg" in this case

hawkeyenl
Posts: 3
Joined: 11 Apr 2015, 20:35

Re: Segmentation fault

#5 Post by hawkeyenl » 12 Apr 2015, 14:45

I've got photorec running on my laptop at the moment. I've connected 1 of the 2 RAID1 disks to my laptop via SATA-to-USB, and it's currently collecting photos. It's gonna take about 6 days (2tb over USB), but at least it's running so I don't want to disturb it for now. After this has finished I'll try to run extdelete, but I want this to finish first.

balance
Posts: 4
Joined: 01 Aug 2017, 16:45

Re: Segmentation fault

#6 Post by balance » 01 Aug 2017, 17:08

Hi,

I don't want to open a new topic since I have the same issue hear. When i am trying to run photorec I am getting

Code: Select all

Segmentation fault
error
I also run

Code: Select all

dmesg photorec
as you suggested above. This gives me bunch of information but I am not sure what can I do with this to make photorec runninng.
Here is the lines which i have in red:

Code: Select all

[    5.048843] brd: module loaded
[    5.051890] Loading iSCSI transport class v2.0-870.
[    5.059408] ahci ahci.0: can't get clock

Code: Select all

[   24.133803] st-pinctrl 922f080.pin-controller-rear: maps: function i2c5 group i2c5-default num 3
[   24.142646] st-i2c 9845000.i2c: No ID specified in DT alias

Code: Select all

[   25.458038] md: invalid raid superblock magic on sda5
[   25.463082] md: sda5 does not have a valid v0.90 superblock, not importing!
[   25.505617] md: invalid raid superblock magic on sdb5
[   25.510668] md: sdb5 does not have a valid v0.90 superblock, not importing!
[   25.517623] md: Scanned 6 and added 4 devices.

Code: Select all

20395] st-pinctrl 920f080.pin-controller-front0: maps: function tsin0 group tsin0_serial num 6
[   53.829654] stm_demod_get_pdata: No syscfg phandle specified
[   53.835423] demod_config_pdata: demod config not set properly
[   53.841315] st-pinctrl 920f080.pin-controller-front0: maps: function tsin4 group tsin4_serial_alt3 num 6
[   53.851010] stm_demod_get_pdata: ts mapping control syscfg update ok
[   53.857486] demod_config_pdata: demod config not set properly
[   53.863410] st-pinctrl 920f080.pin-controller-front0: maps: function tsin3 group tsin3_serial num 6
[   53.872653] stm_demod_get_pdata: No syscfg phandle specified
[   53.878470] demod_config_pdata: demod config not set properly
[   53.884664] stm_lnb_get_pdata: lnb config not properly set
[   53.890365] stm_lnb_get_pdata: lnb config not properly set

Code: Select all

[   54.925336]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_HDMI
[   54.932472]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_REF_HDMIPHY
[   54.939867]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_TMDS_HDMI
[   54.947088]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_MAIN_DISP
[   54.954763]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_MAIN_DISP
[   54.962361]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_TMDS_HDMI
[   54.969610]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_HDMI
[   54.976887]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_REF_HDMIPHY
[   55.002115]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_HDMI
[   55.009252]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_REF_HDMIPHY
[   55.016647]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_TMDS_HDMI
[   55.023869]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_MAIN_DISP

Code: Select all

[   56.107150] stmvout_probe_media_outputs: Display 0: 4 output Plug added
[   56.237983]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_HDMI
[   56.245122]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_REF_HDMIPHY
[   56.252514]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_TMDS_HDMI
[   56.259732]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_MAIN_DISP

Code: Select all

   62.137097] demod_config_pdata: demod config not set properly
[   62.142890] demod_config_pdata: demod config not set properly
[   62.148714] demod_config_pdata: demod config not set properly
[   62.154701] stm_dvb_get_lnb_pdata: lnb config not properly set
[   62.160589] stm_dvb_get_lnb_pdata: lnb config not properly set
[   62.166621] stm_dvb_diseqc_attach() Invalid demod object, cannot attach diseqc
[   62.173887] stm_dvb_diseqc_attach() Invalid demod object, cannot attach diseqc

Code: Select all

[   62.701210] compo_capture_subdev_init(): created disabled links to video plane
[   62.708557] compo_capture_subdev_init(): created disabled links to gfx plane
[   62.709969] loop: module loaded
[   62.718829] compo_capture_subdev_init(): created disabled links to output

Code: Select all

[   63.029782] h264encoder 8c85000.h264encoder: (StreamId:0x0) Unable to soft-reset hva => reset platform

Code: Select all

[   63.757966]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_HDMI
[   63.765104]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_REF_HDMIPHY
[   63.772494]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_TMDS_HDMI
[   63.779703]  stm-ios: vibe_os_clk_disable: Clock already disable CLK_PIX_MAIN_DISP
I will appreciate any help.

User avatar
cgrenier
Site Admin
Posts: 3626
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Segmentation fault

#7 Post by cgrenier » 03 Aug 2017, 07:18

Do you have the same problem when using latest 7.1-WIP ?
Are you using the version compatible with the CPU of your computer and/or NAS ?

balance
Posts: 4
Joined: 01 Aug 2017, 16:45

Re: Segmentation fault

#8 Post by balance » 04 Aug 2017, 23:10

I am using 7.1 now.
Anyway, I did what previous user did - connected one of my disk to my pc trough usb.
Here is the other question:
files I am trying to recover are NEF - nikon raw files. In your wiki http://www.cgsecurity.org/wiki/File_For ... Multimedia you have this format listed, but when I go to file formats in photorec I cannot find this.
nef.JPG
nef.JPG (61.81 KiB) Viewed 138 times
I don't want to recover tons of other files since i now for sure i need only nef one.

balance
Posts: 4
Joined: 01 Aug 2017, 16:45

Re: Segmentation fault

#9 Post by balance » 07 Aug 2017, 04:09

ok, I am running it through the command line
gui one is always gets stuck on 1%
is there a way to specify which type of files you want to recover with command line in windows?
also, I though it supposed to work for deleted files only, but i see pics which i never deleted in my rec folders?
i just don't have 3 tb in my pc to recover all stuff.

User avatar
cgrenier
Site Admin
Posts: 3626
Joined: 18 Feb 2012, 15:08
Location: Le Perreux Sur Marne, France
Contact:

Re: Segmentation fault

#10 Post by cgrenier » 08 Aug 2017, 09:43

In FileOpts, you can select the file family you want to recover (ie. TIFF pour .nef).
By default, PhotoRec only recover deleted files when a partition (FAT, exFAT, NTFS, ext2/3/4) is selected but if the disk has been defragmented in the past, there may be deleted copies of the files.

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests