Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have several old 3.5in floppy disks that I would like to backup. My attempts to create an image of the disks have failed. I tried using the UNIX utility dd_rescue, but when the kernel tries to open (/dev/fd0) I get a kernel error,
floppy0: probe failed...
I would like an image because some of the floppies are using the LIF file system format. Does anyone have any ideas as to what I should do?
HP now Agilent made some tools that could read and write to files on LIF formatted disk. I could use these tools to copy and convert the files to the local disk but not without possibly losing some data in the process. In other words, converting from LIF to some other format back to LIF will lose some information.
I just want to backup the raw bytes on the disk and not be concerned with the type of file system.
I think you'll find the best resource here.
Also, if you're going to use raw dd, LIF format has 77 cylinders vs 80 for a normal floppy.
dd if=/dev/floppy0 of=animage.bin conv=noerror
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have a problem using dd command, assume that I am writing 20MB file to 100MB partition. After the write I am not able to access the rest of 80MB.
dd if=temp_file of=/dev/sdb1
Is there a way I can specify dd to adjust to the file system that I am writing into?
All I am interested is know if there is a way to use the 80MB space without disturbing the initial 20MB.
By using the dd command the way you do, you overwrite the file-system data, including the important meta-data about the file-system. If the temp_file contains a file-system for a 20MB partition then that's what you will get.
If you want a 100MB partition, you need to create a 100MB disk-image to write to the disk.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have run bitbake core-image-minimal-dev properly configured for a genericx86 machine. BitBake generates a bootia32.efi, a bzImage--<stuff>.bin, an .hddimg, an .iso, a .rootfs.ext3, a .rootfs.ext4, a .rootfs.tar.bz2, and a core-image-initramfs-<stuff>.rootfs.cpio.gz. I'm interested in a method of how to dd one or more of these onto the hard disk of my target machine and boot from that hard disk.
dd if=path/to/imagefile/imagename.hddimg of=/dev/usbdevicename
You'll find the correct usb device name e.g. by plugging in the usb disk and looking at dmesg|tail output -- do not guess as mistakes will be fatal to your hard disk. A practical example from my build machine:
sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-sato-intel-corei7-64.hddimg \
of=/dev/sdb \
bs=4096
Note that you probably want to use intel-corei7-64 as the machine unless you know that genericx86 is correct for your hardware: despite the name former is the common Intel BSP for anything that's not ancient (that includes big Cores, Xeons, Atoms ...).
How to boot the image depends on your target device: you may need to go to BIOS settings to select "boot from USB".
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I was editing a file in nano and, when I saved it, I got a disk is full error. However, when I opened the file again, all it's content was gone, including everything that was there before the disk was filled. How can I recover the file's content? My partition type is EXT4. I've already tried recovering it using debugfs with no success.
Thanks in advance.
I've managed to get my file back by dumping an image of the SD card then grepping the strings output of the block file for "signatures" I remembered of the file. After getting the line number, I just cropped the output and saved it to a file.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I have a Lumix camera which, like most new cameras, record video in AVCHD format. The files get segmented into 2 or 4 GiB segments because of the limitations of the filesystem used on the memory card.
When I transfer the files to my linux computer to edit them I naturally want to have each video in a single file, which is no problem at all for linux's filesystems. So, how can I losslessly join these segments, maintaining a/v-sync?
(With Avidemux 2.6.8 I can append these segments, but it leads to nasty distortions at the cut point.)
The solution, which seems to work with my files at least, turned out to be very simple:
ffmpeg -i "concat:00000.MTS|00001.MTS|00002.MTS" -c copy output.mts
One still has to figure out which of the files belong together, though.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have a CD‑R that I have burned some data onto. I know that the consumed storage space cannot be recovered, but is there some way to delete the data so it can't be (easily) recovered from the disk? Not just deleting filesystem entries, but actually burning out the data? My understanding of the way CD‑ROMs works is that the data is physically recorded by etching the bit pattern into a substrate layer in a way that changes the reflective properties of that layer, so one could erase the data by etching the remaining unetched bits. Could this be done, and if so, is there an existing program for accomplishing this?
CD-R is a one time use device. Once the session is closed, there is no way to append or otherwise alter the data image on the disk (to my knowledge).
With a CD-RW, this would be possible my using some type of "format" command.
Unfortunately, the only way to dispose of the data on a CD-R disk is to destroy the media itself.