How Do I Edit An IMG File?

[cmcigas]

Hello everyone, not sure if this is the right forum to ask but I thought Id give it a shot. I have an .IMG file that I am going to use for my Dell R610 server. The IMG file is located here for references https://download.xpenology.fr/.

With this IMG file, one of the drivers in it for my R610 is located in the wrong folder.

The people who made this OS dont want to give out how to fix the issue Im guessing so they keep coming back to that website.

I was hoping to see if anyone could tell me how to edit the file. Whenever I mount it to a USB stick it just shows up as note pad pages and I cant view anything else.

Alls I need to do is move one file within the IMG to another folder. Can anyone help?

 

[USAFRet]

You can't edit that.
A .IMG is just a raw disk image, in binary form.
https://en.wikipedia.org/wiki/IMG_%28file_format%29

The only thing you can really do is extract that out to a disk, change what you want, and create a new .IMG file. It is not directly editable.

 

[torbendalum]

You need some sort of way to mount the image file to read it. I just tested with windows 10, witch can mount the iso version but not the img version. many linux distros also has built in image mounting. else you can use https://www.daemon-tools.cc/products/dtlite for mounting the image in any windows version.

 

[cmcigas]

You can't edit that.
A .IMG is just a raw disk image, in binary form.
https://en.wikipedia.org/wiki/IMG_%28file_format%29

The only thing you can really do is extract that out to a disk, change what you want, and create a new .IMG file. It is not directly editable.

Ok thanks for your help. Is there an easy way to do this or should I just google it and figure it out?

Sorry but I have no idea how to do what you said.

 

[cmcigas]

You need some sort of way to mount the image file to read it. I just tested with windows 10, witch can mount the iso version but not the img version. many linux distros also has built in image mounting. else you can use https://www.daemon-tools.cc/products/dtlite for mounting the image in any windows version.

ill definitley try this out tonight thank you so much

 

[martinch]

If the .img file is not compressed, then you could be able to just rename it to a .iso file and mount that using Windows 8/10's in-built tools. You can then just copy the files out, and use a tool like ImgBurn to re-make an iso/img file out of the final folder.

http://askubuntu.com/questions/388037/how-to-create-an-ubuntu-img-file-from-iso-on-ubuntu

P.S. A Linux VM or live disc is really handy for this kind of thing ...

 

[cmcigas]

You need some sort of way to mount the image file to read it. I just tested with windows 10, witch can mount the iso version but not the img version. many linux distros also has built in image mounting. else you can use https://www.daemon-tools.cc/products/dtlite for mounting the image in any windows version.

I downloaded the tool and was still unable to mount the IMG file. Says I need to format the disc. The ISO file mounts but I am still unable to open them up, they only open into Notepad documents.

Honestly I am not sure if I am even doing it right. I have never done anything like this before. Any more help would be greatly appreciated thank you

 

[USAFRet]

Question:
What is this server to be used for?

 

[USAFRet]

A mounted ISO file would appear as a drive. You don't 'open it' with an application.

 

[cmcigas]

A mounted ISO file would appear as a drive. You don't 'open it' with an application.

I wanted to put an open version of Synology's DSM Software since I love using. I was able to grab a server from my job and since the software is really easy to use. There are versions out there that work properly but the latest version doesnt have the correct driver in the correct folder for my NIC.

I was going to put Ubuntu on the R610 if this didnt work.

Sorry, but I am really bad at software side of things. I only work on the hardware portion of servers.

 

[USAFRet]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

 

[cmcigas]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

 

[USAFRet]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

If it is an uncompressed IMG, you might be able to just rename it .ISO, and Win 10 should mount it natively.
Make your changes, and save that changed thing back into a new ISO.

 

[Alabalcho]

From the web page you referred, there is a description of what each file is:

pat: Synology DSM setup file
img: burn it to an usb drive
iso: burn it to cd/dvd
wmdk: use it for VMware

So - IMG file is intended to be "burned" to an USB drive (in similar way as ISO can be burned to CD/DVD drive). So, get a spare USB key, use "Win32 Disk Imager" (free utility) to burn it onto an USB drive, and boot off that USB (if your server supports USB booting).

Edit: Out of curiosity, I downloaded one of these IMG files, they open pretty well with WinImage, and there is nothing special inside - SysLinux boot media, with most of the capacity taken by 22mb zImage kernel file. There are no folders, and apart from SysLinux.cfg nothing else could be edited. This is the content of the image:

Directory of C:\Temp\XPEnoboot_DS3615xs_5.2-5644.1
2015-11-07 14:48 22,638,848 zimage
2015-11-07 14:48 116,684 ldlinux.c32
2015-11-07 14:48 24,124 libutil.c32
2015-11-07 14:48 26,336 menu.c32
2015-11-07 14:48 759 syslinux.cfg
2015-11-07 14:48 61,952 ldlinux.sys
6 File(s) 22,868,703 bytes

And an important note: The first message in the forum says "Do not use 5644"!

 

[cmcigas]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

If it is an uncompressed IMG, you might be able to just rename it .ISO, and Win 10 should mount it natively.
Make your changes, and save that changed thing back into a new ISO.

I renamed it but error message said it wasnt valid. So I downloaded the ISO from the same site. I was able to mount it but like what Alabalcho said it just comes up with kernel files and the boot media. No folders. This is a bootloader though. So maybe thats why? Sorry about that.

The config files come up as I can open them in notepad.

 

[cmcigas]

From the web page you referred, there is a description of what each file is:

pat: Synology DSM setup file
img: burn it to an usb drive
iso: burn it to cd/dvd
wmdk: use it for VMware

So - IMG file is intended to be "burned" to an USB drive (in similar way as ISO can be burned to CD/DVD drive). So, get a spare USB key, use "Win32 Disk Imager" (free utility) to burn it onto an USB drive, and boot off that USB (if your server supports USB booting).

Edit: Out of curiosity, I downloaded one of these IMG files, they open pretty well with WinImage, and there is nothing special inside - SysLinux boot media, with most of the capacity taken by 22mb zImage kernel file. There are no folders, and apart from SysLinux.cfg nothing else could be edited. This is the content of the image:

Directory of C:\Temp\XPEnoboot_DS3615xs_5.2-5644.1
2015-11-07 14:48 22,638,848 zimage
2015-11-07 14:48 116,684 ldlinux.c32
2015-11-07 14:48 24,124 libutil.c32
2015-11-07 14:48 26,336 menu.c32
2015-11-07 14:48 759 syslinux.cfg
2015-11-07 14:48 61,952 ldlinux.sys
6 File(s) 22,868,703 bytes

And an important note: The first message in the forum says "Do not use 5644"!

Yeah I understand that I shouldnt use 5644 but I just wanted to try and see since this is my first time using that software when it seems only people that have set up before hand have the issues. If not Ill just try it in a different bootloader.

Im guessing this is the issue. When I do boot to USB, the server cant get any further without login info. But its not supposed to get any further. I am supposed to be able to find the Server through an IP on a working PC but since the drivers for the NIC are in the wrong folder I am unable to boot to change the files.

EDIT: per below, this is one of the guys who puts out the software. Just not sure how to get to those folders.

I made a mistake and put the missing firmware in /lib/firmware/bnx2x/ instead of /lib/firmware/bnx2/ 🙁
You have to move the file bnx2-mips-09-6.2.1b.fw from bnx2x to bnx2 folder.
This will be fix the next repack/release

 

[USAFRet]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

If it is an uncompressed IMG, you might be able to just rename it .ISO, and Win 10 should mount it natively.
Make your changes, and save that changed thing back into a new ISO.

I renamed it but error message said it wasnt valid. So I downloaded the ISO from the same site. I was able to mount it but like what Alabalcho said it just comes up with kernel files and the boot media. No folders. This is a bootloader though. So maybe thats why? Sorry about that.

The config files come up as I can open them in notepad.

OK, so I downloaded the ISO, and mounted it with PowerISO.
isolinux.

THis is what that ISO consists of:

Yes, config files, and it is apparently a bootable image.
So you burn that image to a USB or DVD
Boot from that. It might install to your server drive.
The file inside that ISO, "zImage", is the actual installation thing. If the contents of THAT are bad, that is the fault of whoever created that ISO. You can't 'fix that' directly in that ISO or IMG file.

After you get it installed, then you fix the driver issue.

 

[cmcigas]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

If it is an uncompressed IMG, you might be able to just rename it .ISO, and Win 10 should mount it natively.
Make your changes, and save that changed thing back into a new ISO.

I renamed it but error message said it wasnt valid. So I downloaded the ISO from the same site. I was able to mount it but like what Alabalcho said it just comes up with kernel files and the boot media. No folders. This is a bootloader though. So maybe thats why? Sorry about that.

The config files come up as I can open them in notepad.

OK, so I downloaded the ISO, and mounted it with PowerISO.
isolinux.

THis is what that ISO consists of:

Yes, config files, and it is apparently a bootable image.
So you burn that image to a USB or DVD
Boot from that. It might install to your server drive.
The file inside that ISO, "zImage", is the actual installation thing. If the contents of THAT are bad, that is the fault of whoever created that ISO. You can't 'fix that' directly in that ISO or IMG file.

After you get it installed, then you fix the driver issue.

The only thing is I cant install it on that server. Since the PAT file is what installs on the drives I cant go into the ISO on the server. I am supposed to be able to find the server as a "Synology" server on a working PC after that ISO is booted to the server, but since the NIC drives are in the wrong location I am unable to do so.

 

[USAFRet]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

If it is an uncompressed IMG, you might be able to just rename it .ISO, and Win 10 should mount it natively.
Make your changes, and save that changed thing back into a new ISO.

I renamed it but error message said it wasnt valid. So I downloaded the ISO from the same site. I was able to mount it but like what Alabalcho said it just comes up with kernel files and the boot media. No folders. This is a bootloader though. So maybe thats why? Sorry about that.

The config files come up as I can open them in notepad.

OK, so I downloaded the ISO, and mounted it with PowerISO.
isolinux.

THis is what that ISO consists of:

Yes, config files, and it is apparently a bootable image.
So you burn that image to a USB or DVD
Boot from that. It might install to your server drive.
The file inside that ISO, "zImage", is the actual installation thing. If the contents of THAT are bad, that is the fault of whoever created that ISO. You can't 'fix that' directly in that ISO or IMG file.

After you get it installed, then you fix the driver issue.

The only thing is I cant install it on that server. Since the PAT file is what installs on the drives I cant go into the ISO on the server. I am supposed to be able to find the server as a "Synology" server on a working PC after that ISO is booted to the server, but since the NIC drives are in the wrong location I am unable to do so.

An incorrect NIC configuration should not impact the overall installation.
You don't 'go into' the ISO...you boot from install media created from that ISO. DVD or USB.

 

[cmcigas]

So...mount that IMG to a drive.
Fix what needs to be fixed
Create a new IMG of the correct configuration.

You'll need an actual OS in place to do this.

i do have W10 installed on my home PC. Ill have to download something to create a virtual drive correct? then just mount an ISO through there then create an IMG file?

If it is an uncompressed IMG, you might be able to just rename it .ISO, and Win 10 should mount it natively.
Make your changes, and save that changed thing back into a new ISO.

I renamed it but error message said it wasnt valid. So I downloaded the ISO from the same site. I was able to mount it but like what Alabalcho said it just comes up with kernel files and the boot media. No folders. This is a bootloader though. So maybe thats why? Sorry about that.

The config files come up as I can open them in notepad.

OK, so I downloaded the ISO, and mounted it with PowerISO.
isolinux.

THis is what that ISO consists of:

Yes, config files, and it is apparently a bootable image.
So you burn that image to a USB or DVD
Boot from that. It might install to your server drive.
The file inside that ISO, "zImage", is the actual installation thing. If the contents of THAT are bad, that is the fault of whoever created that ISO. You can't 'fix that' directly in that ISO or IMG file.

After you get it installed, then you fix the driver issue.

The only thing is I cant install it on that server. Since the PAT file is what installs on the drives I cant go into the ISO on the server. I am supposed to be able to find the server as a "Synology" server on a working PC after that ISO is booted to the server, but since the NIC drives are in the wrong location I am unable to do so.

An incorrect NIC configuration should not impact the overall installation.
You don't 'go into' the ISO...you boot from install media created from that ISO. DVD or USB.

Sorry I have no idea about any of this but when I boot to the USB, the server boots up and asks for credentials to log in. It cant boost past that and I cant do anything on the server except input credentials. But since I cant see the server on my PC the Synology assistant cant create credentials or install the PAT file which would allow me to actually have a working synology server.

When I boot to the USB I have 3 options, the first is to boot, the second is to install or upgrade and the third is to debug. Then it goes through some stuff to allow the synology assistant to see it. And thats it. To see more what I am talking about heres a youtube video of what the install process looks like, at the end (1:43) you can see the the DiskStation Login prompt, and thats all.

https://youtu.be/hCHba6RDkA0?t=74

EDIT: Thanks for your help with this I really appreciate it

 

[USAFRet]

Then you have much larger issues.

The Synology is a NAS box,right?

What does the Dell server have to do with it? The Synology is its own OS and device, connected to your LAN.

 

[cmcigas]

Then you have much larger issues.

The Synology is a NAS box,right?

What does the Dell server have to do with it? The Synology is its own OS and device, connected to your LAN.

Yeah I do have a Synology NAS that I use for photos and stuff but I want to use my Dell with it too. Plex, wordpress. Its just more powerful the the Synology. I am pretty much using a jailbroken (for a lack of a better word) version of their software to install on the Dell, since I dont have any skills with linux or other software, plus the synology software is free.

 

[USAFRet]

Well...getting the Synology OS to work on a Dell server is a whole different thing.

IF you have created a bootable DVD or USB, and IF your Dell server can boot from a DVD or USB, and IF it does not properly boot and or install from that...

...then you (or whoever created it) needs to do a WHOLE lot more work.

 

[cmcigas]

Well...getting the Synology OS to work on a Dell server is a whole different thing.

IF you have created a bootable DVD or USB, and IF your Dell server can boot from a DVD or USB, and IF it does not properly boot and or install from that...

...then you (or whoever created it) needs to do a WHOLE lot more work.

Yeah I did create a bootable USB and yeah the Dell server can. Actually the broken OS is working on a lot of HP servers and other Dell servers from what it seems and inlcuding some other NAS company products too. Its just that one driver stopping me from having the server up. Its just they messed up while adding in this one driver since it hasnt been in yet.

 

[USAFRet]

My suggestion: Fall back to a different Linux to get that Dell server up and running.
The people you downloaded that ISO from says it works. Apparently it doesn't work with your hardware.

Do something different.