|
|||||||||||
|
From: Susan Chan Lee <susan.lee(at)securityassoc.com>
Date: Mon Dec 30 2002 - 05:30:52 EST
Anyway I got it working using the below commands. BUT my question to the forensics guru's is will using the losetup and mke2fs effect the integrity of the dd image, I notice the inodes table gets updated... Is this a problem? I notice when I do a df -h from the source and destination (once mounted) I get different values? [root@fanta /root]# losetup /dev/loop0 hda5.bs1024.dd
[root@fanta /root]# mke2fs /dev/loop0 1024
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
[root@fanta /root]# mount -o ro /dev/loop0 /mnt/boot/
[root@fanta /root]# mount
-----Original Message-----
Hi, I tried the same process as you did. I got first a failure and then, moving to a different machine and repeating the process, success. first machine (failure) - RedHat Linux 7.1 - kernel 2.4.5 (pretty fancy optioned) - fileutils 4.0.36 - mount-2.11b second machine (success) - RedHat Linux 7.2 - kernel 2.4.8 - fileutils 4.1 - mount-2.11g trying mount -o loop image.dd /mountpoint -vv I get:
mount: going to use the loop device /dev/loop3
set_loop(/dev/loop3,ttt/image2.dd,0): success
mount: setup loop device successfully
or too many mounted file systems so loop is no problem, i suppose that either defaults option of mount are a problem or dd. -- Eugen Cocalea || eugen@isratech.ro ex - Network Administrator @ isratech.ro|| Phone: +40 232 219992 Cell: +40 723 605070 On Dec 27, 2002, 1:59pm, Susan Chan Lee wrote:Received on Mon Dec 30 08:59:30 2002 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:42 EDT |
||||||||||
|
|||||||||||