Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
01-20-2010, 06:47 AM
|
#1
|
Member
Registered: Sep 2003
Posts: 210
Rep:
|
mkisofs error
Hope it will be allright to ask this question here even though mkisofs is loaded on windows. I am trying to make isos of my second hard drive.
I am changing to the d drive and running this comand.
Code:
mkisofs \
-b cdboot/msboot.img -no-emul-boot -boot-load-seg 1984 -boot-load-size 4 \
-iso-level 2 -J -l -D -N -joliet-long -relaxed-filenames \
-V "WXHEOM_EN" \
-o ../WXHEOM_EN.iso .
Here is the error I get.
no such host or network path.non-existant or inaccessible: \/filename.ext
does that for each file then exits.
got the directions from here.
http://www.g-loaded.eu/2007/04/25/ho...-with-mkisofs/
|
|
|
01-20-2010, 07:09 AM
|
#2
|
LQ Newbie
Registered: Feb 2009
Location: Poland
Distribution: My own, Fedora, OpenSuse
Posts: 21
Rep:
|
Remove backslashes ???
What about removing backslashes?
Code:
$ mkdir cdboot
$ touch cdboot/msboot.img
(...)
$ mkisofs -b cdboot/msboot.img -no-emul-boot -boot-load-seg 1984 -boot-load-size 4 -iso-level 2 -J -l -D -N -joliet-long -relaxed-filenames -V "WINSP" -o ../winsp.iso .
(...)
$ ll ../winsp.iso
-rw-rw-r-- 1 madyogi madyogi 376832 Jan 20 13:04 ../winsp.iso
Works for me fine. Try harder next time...
Last edited by madyogi; 01-20-2010 at 07:13 AM.
|
|
|
01-20-2010, 11:13 PM
|
#3
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
thanks. I will try that.
|
|
|
01-21-2010, 01:41 AM
|
#4
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
Did not work for me. I could not get it to write the output to a file but did take screen captures of it. The first is from running the command exactly like it is in your post the second is from removing commands until it started trying to build an iso.
|
|
|
01-22-2010, 02:36 PM
|
#5
|
LQ Newbie
Registered: Feb 2009
Location: Poland
Distribution: My own, Fedora, OpenSuse
Posts: 21
Rep:
|
:|
Have you considered using Linux for this?
I'm asking because:
1. The quote you've posted first is taken directly from Linux shell.
2. This forum is for Linux too.
3. The mentioned URI clearly points it is about creating a Windows bootable CDs under Linux (at least the part with quoted 'mkisofs').
4. There is no mkisofs.exe for Win...XP (SP3) after a clean install... No idea where did you get it from.
5. And with all the respect - You made my jaw hit the ground...
|
|
|
01-22-2010, 04:24 PM
|
#6
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
Quote:
Originally Posted by madyogi
4. There is no mkisofs.exe for Win...XP (SP3) after a clean install... No idea where did you get it from.
|
Not sure what you mean here. There is a mkisofs-win32 that runs on winxp3. all I need to do is run it on c drive and turn anything on d drive into a 650mb iso with disc spanning when there is more than one disk.
and yes I know that this is linux. I think I mentioned the fact on my first post but I have posted everywhere I can find. Nobody knows anything about mkisofs.
and yes I bought a pack of 50 discs and burned every single flavor of linux I could find and out of that I got about four full install linux versions and two live cds. sax and wolverine or something like that none would write to ntfs. I know that linux users do not admit it but there is know beginner friendly version of linux. ubuntu is probly the easiest but it is not a good system. It is riddled with more problems then windows 97 was.
I do not see what the problem is someone either knows the answer and will tell me or not. From everything I can find out the linux commands are supposed to work with the windows version. and there are windows programs that use mkisofs and will build a iso file but none of them I have found does disk spanning. noe of the windows programs I have found does disk spanning either unless they compress it or change the files to where you need the origanal program to open it. I need exactly like it is on d drive.
|
|
|
01-22-2010, 04:37 PM
|
#7
|
LQ Newbie
Registered: Nov 2002
Location: Canada
Distribution: Fedora
Posts: 5
Rep:
|
Forgive me, because I'm not going to answer your question but rather question your premise... but what is it you're trying to accomplish? If the goal is to create a backup of your hard drive, then converting it to an ISO image may be the wrong answer. There's a loss of information. Sure, your files will be there intact, but the metadata is lost... which might make recovery a nightmare, even though you (in a literal sense) have your data.
Where I'm going with this is that a tool which would preserve metadata might also help with the CD/DVD spanning issue and hence simplify your task. Under *nix, you'd do something like a tar cvf tarfile.tar tree-or-file (and you can both compress AS you're doing it or after depending on your version of tar, compression program, etc.) (Mind you, my tar example wouldn't do the spanning... but you can then carve the file into pieces. Whatever.)
For what it's worth, here's how I invoke mkisofs when I'm burning things:
mkisofs -l -allow-leading-dots -v -R -r -J -V "Volume Name" -o /path/output.iso .
That final "." is of course the top of the tree I'm turning into an iso. (So I'm usually in the correct directory when I run it, and my output path might be ~/output.iso to put it in my home directory.)
Good luck,
Adam
|
|
|
01-22-2010, 06:16 PM
|
#8
|
Member
Registered: Jan 2010
Distribution: Arch, Gentoo, FreeBSD
Posts: 64
Rep:
|
For making isos of windows software discs, I put this in my .bashrc: alias mkwiniso="mkisofs -v -iso-level 3 -J -joliet-long -D", but that's not for hard drive backups by any means, for that, as PithyThought said, you'd want to use something like tar and dd.
http://gnuwin32.sourceforge.net/packages/gtar.htm
http://www.chrysocome.net/dd
EDIT: and yes, those are links to windows versions of the software.
Last edited by slightlystoopid; 01-22-2010 at 06:18 PM.
Reason: Clarification
|
|
|
01-22-2010, 06:45 PM
|
#9
|
LQ Newbie
Registered: Feb 2009
Location: Poland
Distribution: My own, Fedora, OpenSuse
Posts: 21
Rep:
|
Well, on one of disc partitions I have Windows XP installed. Have searched entire drive and there is nothing that looks like "mkisofs*".
Using somebody's else application (like "mkisofs-win32", you've mentioned) with parameters specific to Linux will never work for you (well, only if the application is 100% compatible to the Linux one).
And yes, as PithyThought said - you will lose all the meta-data if you backup the disk (specially NTFS formatted) using ISO images.
Just wondering – are you trying to get a "block by block", exact copy of selected drive?
You mentioned the "C" drive – you will never do it under Windows, since Windows locks opened files and your copy will always contain errors (missing files mostly).
If I made a right guess here, then using "dd" is much better solution for you. But again – this is a Linux program. Download, burn and boot some Linux Live CD distribution (even a tiny one). Mount the partition to write at (like "/dev/hda2" – guessing it's your drive "D:" ) and copy image of "/dev/hda1" ( drive "C:" ) there. Note that the drive you write at can't be NTFS formatted since Linux distributions don't like this file system very much. Try using FAT32 (VFAT). The file system of partition you're backing up doesn't matter at all in this case.
$ mount /dev/hda2 /mnt
$ dd if=/dev/hda1 of=/mnt/hda1.img bs=4096
$ umount /dev/hda2
This will produce a single file as big as entire partition. Note that, depending how big the source partition is, it can take even few hours to build the backup image.
The "dd" also supports spanning with COUNT and SEEK parameters. See:
$ man dd
P.S. Sorry for the grammar and language, it's quite late at my location.
P.S. 2 Be very careful with "dd", in wrong hands it can do more harm than good...
|
|
|
01-23-2010, 09:19 AM
|
#10
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
Quote:
Originally Posted by PithyThought
Forgive me, because I'm not going to answer your question but rather question your premise... but what is it you're trying to accomplish? If the goal is to create a backup of your hard drive, then converting it to an ISO image may be the wrong answer. There's a loss of information. Sure, your files will be there intact, but the metadata is lost... which might make recovery a nightmare, even though you (in a literal sense) have your data.
Where I'm going with this is that a tool which would preserve metadata might also help with the CD/DVD spanning issue and hence simplify your task. Under *nix, you'd do something like a tar cvf tarfile.tar tree-or-file (and you can both compress AS you're doing it or after depending on your version of tar, compression program, etc.) (Mind you, my tar example wouldn't do the spanning... but you can then carve the file into pieces. Whatever.)
For what it's worth, here's how I invoke mkisofs when I'm burning things:
mkisofs -l -allow-leading-dots -v -R -r -J -V "Volume Name" -o /path/output.iso .
That final "." is of course the top of the tree I'm turning into an iso. (So I'm usually in the correct directory when I run it, and my output path might be ~/output.iso to put it in my home directory.)
Good luck,
Adam
|
Never really thought about meta-data. Will not know how much of an issue that is untill I get some of these disk built. But if it is not an issue using nero I am assuming it is not an issue with mkisofs. the problem using nero I am trying to overcome is program files directotory Is larger then the cd and I am hoping the disc spanning will over come that. Is there a way to tell mkisofs what size to build the iso. I will have to check my notes but that command a lot like one I was able to build a 3.something GB copy of my files. not good for a cd.
|
|
|
01-23-2010, 09:49 AM
|
#11
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
Quote:
Originally Posted by slightlystoopid
For making isos of windows software discs, I put this in my .bashrc: alias mkwiniso="mkisofs -v -iso-level 3 -J -joliet-long -D", but that's not for hard drive backups by any means, for that, as PithyThought said, you'd want to use something like tar and dd.
http://gnuwin32.sourceforge.net/packages/gtar.htm
http://www.chrysocome.net/dd
EDIT: and yes, those are links to windows versions of the software.
|
Just a thought but have you ever tested those under windows. as I am finding out with mkisofs porting something to windows does not mean it works and will it do diskspanning. The problem with tar is the same as with windows zip programs. I need the program to read the disk. by burning a cd using an iso file of the drive in a pinch I can even use dos to look and work with the files. cab files would maybe work but to break everything into sized cab files takes to long. I will down load the tar and dd programs and play with them and see if they will work.
|
|
|
01-23-2010, 10:37 AM
|
#12
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
Quote:
Just wondering – are you trying to get a "block by block", exact copy of selected drive?
You mentioned the "C" drive – you will never do it under Windows, since Windows locks opened files and your copy will always contain errors (missing files mostly).
|
not block by block I think? but the dir tree is important. I agree even though winxp claims volume shadow copy or whatever overcomes that I have never got it to work. but I built a type livedisk. sort of a changed version of the ram disk used on the setup disk to take c drive offline and use xcopy to move files from one disk to another.
It surprised me how easy that was. Not sure what you mean by block by block but if I have a 20 gig hd I am only interested in the files not the hdd format. I started out trying to use linux but out of the 5 comps I have here no single os would load on all of them. As for as live cds sax seemed to work the best. but it did not have mkisofs on it and allthough it read ntfs would not write to it.
|
|
|
01-24-2010, 05:44 AM
|
#13
|
LQ Newbie
Registered: Feb 2009
Location: Poland
Distribution: My own, Fedora, OpenSuse
Posts: 21
Rep:
|
If you care about the file system only, then why don't you use something that is shipped with NT itself since it saw the market - "ntbackup.exe" tool. (This is a translation of XP menus made in my language version.)
"Start -> Programs -> Accessories -> System Tools -> Backup tool"
It will produce BKF files of entire/selected parts of the file system, you will be able to store them later on a different drive/file. The good thing is, it supports a commandline so you can work with it even from batch scripts.
I guess it doesn't support spanning so you have to worry about each single image or produce a large one and then span it. Hey, it's free of extra costs.
What about this: http://www.7-zip.org
If you are looking for "one click" solution then maybe something from deep down of my memory, that sounds like "Norton Ghost" will help you. Don't know if the tool still exists, changed it's name or became a part of a different toolkit...
|
|
|
01-24-2010, 08:41 AM
|
#14
|
Member
Registered: Sep 2003
Posts: 210
Original Poster
Rep:
|
Quote:
Originally Posted by madyogi
If you care about the file system only, then why don't you use something that is shipped with NT itself since it saw the market - "ntbackup.exe" tool. (This is a translation of XP menus made in my language version.)
"Start -> Programs -> Accessories -> System Tools -> Backup tool"
It will produce BKF files of entire/selected parts of the file system, you will be able to store them later on a different drive/file. The good thing is, it supports a commandline so you can work with it even from batch scripts.
|
You know ntbackup was my first choice but I have winxp home and it is not on any of my install disks. I have a retail edition-full install,retail upgrade install,and two generic oem editions and none of them have backup on them in any form. Do not know, maybe that is a winxp pro thing.
Maybe if I could get an old version of ghost but the new version is for preparing hdds for new systems. I do not want a 20 gig image of a 20 gig hdd.
One of the earlier posts got me thinking though. tar and dd or some combination of linux tools may work. there are windows tools that view tar. the windows version of tar did not do anything but give errors and there is really no good info on it but If I remember right unrar will extract tar files and on this comp sax will run from a live cd so I may be able to get something that works and then take it from comp to comp as for as linux flavors go. going to have to do some research.
|
|
|
All times are GMT -5. The time now is 06:59 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|