Bugs item #2969376, was opened at 2010-03-12 08:18
Message generated for change (Comment added) made by carrier
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2969376&group_id=55685
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: oncer oncer surname (oncer82)
Assigned to: Nobody/Anonymous (nobody)
Summary: initializing TSK directly from Physical Drive
Initial Comment:
I am initializing TSK directly from Physical device.
Everything works fine under Windows. I use string like "\\.\PHYSICALDRIVE0" for initializing.
But, i unable to initialize TSK properly under Linux ("/dev/sda1").
I use "tsk_img_open_sing" first, and than "tsk_vs_open" to get list of Partitions on a Hard Drive.
"tsk_vs_open" fails under Linux.
Actually, is this normal initializing TSK directly from Physical device?
----------------------------------------------------------------------
>Comment By: Brian Carrier (carrier)
Date: 2010-03-18 09:40
Message:
If you are processing 'sda1", then you should use tsk_fs_open because the 1
partition should contain a file system. If you want to process the volume,
then you should be opening "/dev/sda".
----------------------------------------------------------------------
Comment By: oncer oncer surname (oncer82)
Date: 2010-03-12 09:36
Message:
Fails at case when first partition is NTFS and second is some Linux
specific (this does not have matter).
Fails on "tsk_vs_dos_open" function when loading primary table
"dos_load_prim_table".
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=477889&aid=2969376&group_id=55685
|
