I have a laptop in which i have to get the data off. The hard drive is a stupid toshiba conector of which i dont have an adaptor. So i need to boot using a live cd,
I have booted off the helix cd, The hard drive is automounted as sda1 . This is not a problem
I can access the files on the drive.
I need to mount a USB stick how do i find out where it is located to mount ? what do i need to type mount ………………
Cheers
If your HDD comes up as SDA then I'd be surprised if your USB drive didn't come up as SDB but go to console and type fdisk -l. If that doesn't work then use dmesg to view info on any inserted devices.
I have a laptop in which i have to get the data off. The hard drive is a stupid toshiba conector of which i dont have an adaptor. So i need to boot using a live cd,
I have booted off the helix cd, The hard drive is automounted as sda1 . This is not a problem
I can access the files on the drive.
I need to mount a USB stick how do i find out where it is located to mount ? what do i need to type mount ………………
Cheers
If the laptop runs Windows, and you can log into it, could you use FTK Imager to acquire a live image?
The hard drive is automounted as sda1
You may be aware of this and if so I apologise for teaching you to suck eggs oops , but…
'sda1' will be the volume on the hard drive, not the hard drive itself. If you want to capture everything in your image (i.e. unallocated clusters etc) you will need to image the device (/dev/sda) rather than the volume (/dev/sda1).
Alternatively, you could image each section seperately using something like 'mmls' from 'sleuthkit' to give you the offsets.
Stu
The hard drive is automounted as sda1
You may be aware of this and if so I apologise for teaching you to suck eggs oops , but…
'sda1' will be the volume on the hard drive, not the hard drive itself. If you want to capture everything in your image (i.e. unallocated clusters etc) you will need to image the device (/dev/sda) rather than the volume (/dev/sda1).
Alternatively, you could image each section seperately using something like 'mmls' from 'sleuthkit' to give you the offsets.
Stu
The windows os is currupt so wont boot. The hard drive has a stupid connector on the end so i can just slip it into one of my working machines so i need to use a live disk to get the data of the partition which is SDA1 .. i can see the directory structure.
All i need is to mount a usb stick to get the data off.
I have attached a picture of my mount -l …. i cant work out which is my usb if any at all.
Any other ideas how i can get the data off ?
i cant work out which is my usb if any at all.
Any other ideas how i can get the data off ?
So your Windows NTFS partition is mounted as /media/sda1.
Plug in your usb drive, then run "fdisk -l" and post the output here. I'm going to guess it will be seen as /dev/sdb, with mountable partitions detected as /dev/sdb1, etc. (as already stated by chrisvaughanuk). "fdisk -l" should tell you of any partitions detected.
i cant work out which is my usb if any at all.
Any other ideas how i can get the data off ?So your Windows NTFS partition is mounted as /media/sda1.
Plug in your usb drive, then run "fdisk -l" and post the output here. I'm going to guess it will be seen as /dev/sdb, with mountable partitions detected as /dev/sdb1, etc. (as already stated by chrisvaughanuk). "fdisk -l" should tell you of any partitions detected.
The picture is with the USB Stick in …… this is my problem
The picture is with the USB Stick in …… this is my problem
Okay, I got that, but the picture is showing the output of the "mount" command. If the usb stick is not mounted it will not show up (even if it is plugged in and detected). You are putting the chicken before the egg.
If the USB stick is not automatically mounted, it will NOT show up in the picture. That's why you want to run "fdisk -l"…to see what partitions are available, THEN mount the USB stick and THEN it will show up in the mount output.
You could do worse than try
mount /dev/sdb1 /media/sdb1
You may need to create the mount point ( e.g. mkdir /media/sdb1 ) and you probably need to specify that it should be read/write, as Helix ( rightly so ) makes a point of only doing things read-only ( as evidenced by the "ro" next to your NTFS partition ). You do that by adding "-o rw" to the command line.
I do apologise for not having actually tested this, the command works on my Fedora system, so that's kind of ok … But I'm not so sure how it will do on Helix …
P.S. If you boot with the thumb drive in, it will create the directories for you, and mount the drive, but it will be read only - in that case you would need to type
umount /dev/sdb1
mount -o rw /dev/sdb1 /media/sdb1