Creating Filesystems with Openmediavault (Solved)

[Mark Greaves (PCNetSpec)]

Yup .. you knew there would be .. c'mon admit it ..

Code: [Select]

cat /proc/cpuinfo

[Emegra]

AMD Athelon
1211.964 MHz
256Kb cache

[Mark Greaves (PCNetSpec)]

Hmm .. not the most powerful CPU, but peppermint seems quite happy on celeron 900's (so I guess it would be fine .. but it's your call.

Which would you rather try ..

Working out what's going on in OMV
or
doing this through peppermint ?

[Emegra]

Which would you rather try ..

Working out what's going on in OMV
or
doing this through peppermint ?

Personally OMV only because I have some idea of what I'm getting into and what I can expect from it due to it's similarity to freenas, however if you're saying that peppermint can do a better job I'm happy to be guided by you, Also I don't want to brass you off with this wireless thing. But as this purely experimental and I'm in this to learn so I'll take your advice.


Many thanks

Graeme

[Mark Greaves (PCNetSpec)]

OK, are there any clues to the samba and nfs errors/warnings in syslog ?

Code: [Select]

nano /var/log/syslog

?

and what's the output from:

Code: [Select]

dpkg -l | grep nfs

do me a favour, run:

Code: [Select]

nano /etc/network/interfaces

and make it read:-

Code: [Select]

# The loopback network interface
auto lo

# The primary network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 192.168.2.150
    netmask 255.255.255.0
    gateway 192.168.2.1
#    dns-nameservers 192.168.2.1

SAVE the file .. and see if you still get the samba and NFS errors, and the boot problems.

--

[Emegra]

Hi Mark

I think this will test your patience further, but mysteriously the samba and NFS errors are gone, I don't know why but they were definitely there prior to shutting down the NAS last night and when I booted it up this morning they're gone, So as it stands now the NAS will boot up with no errors and I can log into the Web GUI on 192.168.2.150 & 192.168.2.151 ONLY if the ethernet is connected ( ssh only with 192.168.2.150), so presumably it's connecting to both ip addresses via ethernet in spite of 192.168.2.151 being assigned to wlan0.

I'm not sure if the outputs you asked for in your previous post are relevent now but I've posted them anyway, I didn't edit the /etc/network/interfaces file as you suggested due to the changes in circumstances but I've posted a copy of the file at the bottom of this post

Code: [Select]

nano /var/log/syslog 

GNU nano 2.2.4                                      File: /var/log/syslog                                                                                   

Mar  8 20:20:38 openmediavault kernel: imklog 4.6.4, log source = /proc/kmsg started.
Mar  8 20:20:38 openmediavault rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="954" x-info="http://http://www.rsyslog.com"] (re)start
Mar  8 20:20:38 openmediavault kernel: [    0.000000] Initializing cgroup subsys cpuset
Mar  8 20:20:38 openmediavault kernel: [    0.000000] Initializing cgroup subsys cpu
Mar  8 20:20:38 openmediavault kernel: [    0.000000] Linux version 2.6.32-5-686 (Debian 2.6.32-38) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4)$
Mar  8 20:20:38 openmediavault kernel: [    0.000000] KERNEL supported cpus:
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   Intel GenuineIntel
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   AMD AuthenticAMD
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   NSC Geode by NSC
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   Cyrix CyrixInstead
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   Centaur CentaurHauls
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   Transmeta GenuineTMx86
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   Transmeta TransmetaCPU
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   UMC UMC UMC UMC
Mar  8 20:20:38 openmediavault kernel: [    0.000000] BIOS-provided physical RAM map:
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 00000000000000 00 - 000000000009fc 00 (usable)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 000000000009fc 00 - 00000000000a00 00 (reserved)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 00000000000f00 00 - 00000000001000 00 (reserved)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 00000000001000 00 - 000000005fff00 00 (usable)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 000000005fff00 00 - 000000005fff30 00 (ACPI NVS)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 000000005fff30 00 - 00000000600000 00 (ACPI data)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 00000000fec000 00 - 00000000fec010 00 (reserved)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 00000000fee000 00 - 00000000fee010 00 (reserved)
Mar  8 20:20:38 openmediavault kernel: [    0.000000]  BIOS-e820: 00000000ffff00 00 - 00000001000000 00 (reserved)
Mar  8 20:20:38 openmediavault kernel: [    0.000000] DMI 2.3 present.
Mar  8 20:20:38 openmediavault kernel: [    0.000000] last_pfn = 0x5fff0 max_arch_pfn = 0x100000
Mar  8 20:20:38 openmediavault kernel: [    0.000000] MTRR default type: uncachable
Mar  8 20:20:38 openmediavault kernel: [    0.000000] MTRR fixed ranges enabled:
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   00000-9FFFF write-back
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   A0000-BFFFF uncachable
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   C0000-C7FFF write-protect
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   C8000-FFFFF uncachable
Mar  8 20:20:38 openmediavault kernel: [    0.000000] MTRR variable ranges enabled:
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   0 base 000000000 mask FC0000000 write-back
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   1 base 040000000 mask FE0000000 write-back
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   2 disabled
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   3 disabled
Mar  8 20:20:38 openmediavault kernel: [    0.000000]   4 disabled

dpkg -l | grep nfs

root@openmediavault:~# dpkg -l | grep nfs
ii  libnfsidmap2                       0.23-2                       An nfs idmapping library
ii  nfs-common                         1:1.2.2-4                    NFS support files common to client and server
ii  nfs-kernel-server                  1:1.2.2-4                    support for NFS kernel server
root@openmediavault:~#

# The loopback network interface
auto lo
iface lo inet loopback

# eth0 network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
    address 192.168.2.150
    gateway 192.168.2.1
    netmask 255.255.255.0
    mtu 1500

# wlan0 network interface
auto wlan0
iface wlan0 inet static
    address 192.168.2.151
    gateway 192.168.2.1
    netmask 255.255.255.0
    mtu 1500

[Emegra]

Hi again

I spent some on it this morning and I've got it working wirelessly at last by following you and SeZo's instructions from the thread in General Discussions (pages 9 & 10) the last time we reached this point (before starting over and re-installing etc),

 so now I can log in to the web GUI on wlan0 / 192.168.2.151 minus the ethernet cable, the only problem now is I cant connect via ssh, when I try I get this error

Code: [Select]

graeme@Linux3 ~ $ ssh root@192.168.2.151
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
57:11:1d:e1:87:a1:cf:b8:22:de:7b:17:ef:42:0a:76.
Please contact your system administrator.
Add correct host key in /home/graeme/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/graeme/.ssh/known_hosts:1
  remove with: ssh-keygen -f "/home/graeme/.ssh/known_hosts" -R 192.168.2.151
RSA host key for 192.168.2.151 has changed and you have requested strict checking.
Host key verification failed.

EDIT

Spoke too soon now it refuses to log into the Web GUI after reboot unless I reinput

Code: [Select]

ifdown eth0 

into the NAS terminal, disappointing to say the least but we must be close


Many Thanks

Graeme

[Mark Greaves (PCNetSpec)]

Do what it's telling you to remove the key .. the next time you attempt to ssh in it should ask you to accept the key again (as if this is the first time you've connected).

On the Peppermint box run:

Code: [Select]

ssh-keygen -f "/home/graeme/.ssh/known_hosts" -R 192.168.2.151

ssh should now work ?

Then on the NAS

Code: [Select]

nano /etc/network/interfaces

and comment out the lines that are autostarting the eth0 interface .. ie:-

# auto eth0
# allow-hotplug eth0

[Emegra]

Code: [Select]

ssh-keygen -f "/home/graeme/.ssh/known_hosts" -R 192.168.2.151
fopen: No such file or directory

[Mark Greaves (PCNetSpec)]

on peppermint, what's the output from:

Code: [Select]

ls -a /home/graeme/.ssh

or just try:

Code: [Select]

ssh-keygen -R 192.168.2.151

then see if you can ssh in.

[Emegra]

Sorry Mark I put the ssh-keygen command into the NAS instead of the PC, ssh is working fine now I've rebooted and I can log straight into the Web GUI

So it looks like you've done it again thank you so much I really appreciate the effort and patience you put into this

Just one question regarding ssh,   I have a laptop running peppermint 3 will I have to add that to the known_hosts list to access the NAS via ssh,






Graeme

[Mark Greaves (PCNetSpec)]

Just one question regarding ssh,   I have a laptop running peppermint 3 will I have to add that to the known_hosts list to access the NAS via ssh,

no .. each PC that you connect to the NAS with using ssh will store the ssh key from the NAS locally .. this is just to make sure you're connecting to the correct ssh server, ie. you're not being redirected to a different server that could intercept your passwords etc. (man in the middle attack).

[EDIT]

there may still be 1 problem though.

[Mark Greaves (PCNetSpec)]

am I right in assuming the NAS can:-

Code: [Select]

ping -c 5 173.194.34.71

but it cannot

Code: [Select]

ping -c 5 google.com

?

[Emegra]

No it's pinging both ok no problem

[Mark Greaves (PCNetSpec)]

GREAT ... all sorted then.