How to destroy Openmediavault in 1 easy step (Solved)

system · 12 March 2013 20:13

While in the Web GUI, click network / interfaces, then select dns, and in the box titled dns server address, type in the gateway address, this will throw the system into an unending loop of trying to save the settings, then once completely satisfied that this could go on forever (25 minutes should be enough time) switch off via the power button, Once shutdown, reboot and viola, you have a completely un-usable Openmediavault NAS that you can no longer log into via the Web GUI or ssh.

So far I haven’t figured out how to reverse this process and return the NAS back into a workable state, this seems to be much more complicated, so if anyone has any suggestions, I would be extremely grateful.

Many thanks

Graeme

SeZo · 12 March 2013 20:51

How about booting with LiveCD then mounting /dev/sda1
Edit /etc/network/interfaces (assuming this is the part that got modified in the WebGui)

system · 12 March 2013 21:00

Hi SeZo

Thanks for your help

Edit /etc/network/interfaces (assuming this is the part that got modified in the WebGui)

I hooked up a monitor and keyboard and the system was booted up and on the command prompt as usual. I looked at /etc/network/interfaces, and all references to wlan0, were changed to bond0, I changed all bond0 references back to wlan0, so the file is now exactly the same as it was when it was last working before i screwed it up,

I’ve since rebooted and there are no error messages showing up during the boot sequence but, I still can’t log in via Web GUI or ssh, I’ve tried pinging ip addresses and hostnames and the won’t work either, so it’s like I have no network or internet connection

Graeme

SeZo · 12 March 2013 21:12

Hmm… The reference to bond0 indicates that OMV modified your network settings to create a single bonded interface by combining 2 or more network interfaces. Unfortunately I do not know how to undo this. But Googling might help

system · 12 March 2013 21:17

I managed to sort it by re adding the wpa-ssid and wpa-psk to the /etc/network/interfaces file, so as you say whatever I done it caused OMV to rewrite the interfaces file,

Can you tell me what the DNS server is and what the address should be

Thanks

Graeme

SeZo · 12 March 2013 21:23

Can you tell me what the DNS server is and what the address should be

The DNS server (as default) should be the same as the gatewy IP address so that name resolving is done by your ISP of course you can set it to be something else too.

system · 12 March 2013 21:28

Thanks for that SeZo,

So really I don’t know what I done wrong then

In vtew of this I think I’ll take you and Marks advice and do a image backup, I burnt a Redo iso this morning so I’ll do that first before I screw it up again

Thanks for your help

Graeme

SeZo · 12 March 2013 21:38

So is it working then?
If you want more DNS servers then look into /etc/resolv.conf
On my server I have:

# Google IPv4 DNS
nameserver 8.8.8.8
nameserver 8.8.4.4

# OpenDns
nameserver 208.67.222.222
nameserver 208.67.220.220

Don’t use this method if you have the resolvconf program installed.

system · 12 March 2013 21:48

So is it working then?

Yes it’s working, I t seems that whatever happened it not only changed wlan0 to bond0 it also wiped the wpa-ssid & wpa-psk settings from /etc/network/interfaces once I re-added them everything kicked back in.

I can’t check my /etc/resolv.conf because I’m in the Redo screen looking for a way to backup to the network, but I’ll check it out when I can and compare it to yours

Thanks again

Graeme

Mark_Greaves_PCNetSp · 12 March 2013 21:53

I’d stick with your routers IP as the nameserver, or local DNS may be broken

system · 12 March 2013 22:01

I'd stick with your routers IP as the nameserver, or local DNS may be broken

To be completely honest Mark I don’t understand nameservers & DNS etc, I’m really way out of my league here, but it’s working again so I’m content with that,

At the moment I’m trying to back up the image so next time i screw up (which is almost guaranteed) I’ll have something to fall back on, I’m using Redo as you suggested and it looks very easy to use although I can’t find a way to navigate to a network share (no .gvfs) and the biggest spare usb drive I have is only 2gb which I suspect is not big enough.

Many thanks

Graeme

Mark_Greaves_PCNetSp · 12 March 2013 22:08

All DNS is … is the domain name server (nameserver) … the thing that converts IP’s (173.194.34.99) to human readable addresses (google.com) and vice versa

The internet (and your LAN) really works with IP’s, but humans can’t remeber those … so you enter google.com and it’s looked up on the domain name server and converted to the associated IP.

Mark_Greaves_PCNetSp · 12 March 2013 22:12

OK, what’s the problem you have now ?

system · 12 March 2013 22:12

All DNS is .. is the domain name server (nameserver) .. the thing that converts IP's (173.194.34.99) to human readable addresses (google.com) and vice versa
The internet (and your LAN) really works with IP’s, but humans can’t remeber those … so you enter google.com and it’s looked up on the domain name server and converted to the associated IP.

Well explained like that it seems simple enough to understand.

You’re an education Mark

Graeme

Mark_Greaves_PCNetSp · 12 March 2013 22:15

system · 12 March 2013 22:15

OK, what's the problem you have now ?

Well I’m trying to backup the OMV image to a network location because I dont have usb drive big enough, but I can’t find a way to navigate to a network location

Graeme

Mark_Greaves_PCNetSp · 12 March 2013 22:22

gimme half an hour or so … I’ll need to create a Redo disk and have a looksee

system · 12 March 2013 22:24

gimme half an hour or so .. I'll need to create a Redo disk and have a looksee

Take all the time you need Mark, I’m off to bed it’s been a long day

Graeme

Mark_Greaves_PCNetSp · 12 March 2013 23:25

I suggest you connect your OMV box to the LAN with an ethernet cable.
(you can do it over wireless but it will take ages)

Boot to the Redo Backup & Recovery LiveCD/LiveUSB

Make sure NetworkManager says you’re connected

Click “Backup”

Choose the source drive from the drop menu … click “Next”

Select the partitions you want to backup … I suggest all of them … click “Next”

Tick “Shared over a network” … then click the “Search Network” button … it will search the LAN for any shares.

Select the network share you want to backup to from the drop list of discovered shares.

If the share requires a username and password, enter them … then click the “Next” button.

Click the “Browse” button … and select a location for the backup … click the “Save here” button.

Click the “Next” button

Give the backup a name … click the “Next” button

The backup should start.

–

system · 13 March 2013 07:04

Thank you Mark

Your instructions are spot on as usual, but when I get to the part where I select the network location then click “Next” I get this message

"Could not access the destination drive. if the device is shared on a network, ensure that the username and password you provided are correct and try again"

I only have one username and one password I have ever used on that system, I’ve tried changing some permissions setting on that particular share, I’ve tried it with no password, the same error keeps popping up.

So I think the best thing for me would be to just get a external drive large enough to hold the image and do it locally, because users, groups, permissions etc is a mystery to me and any attempt to teach me and get me round this issue would most likely be nothing but an exercise in frustration for both of us

Once again many thanks for you help

Graeme