Author Topic: Unrecognized NAS but no unrecognized devices.  (Read 594 times)

jph

  • Newbie
  • *
  • Posts: 14
    • View Profile
Unrecognized NAS but no unrecognized devices.
« on: March 01, 2012, 09:48:07 pm »
I have attached a NAS on eth1 (internal) but the device is not recognized.  There are no unrecognized devices in WebAdmin Advanced> Configuration > Unknown Devices.

________________
Result of ifconfig -a:

eth0      Link encap:Ethernet  HWaddr bc:ae:c5:9a:1a:7a 
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::beae:c5ff:fe9a:1a7a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16760 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12198 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20814810 (20.8 MB)  TX bytes:904542 (904.5 KB)
          Interrupt:210 Base address:0x6000

eth1      Link encap:Ethernet  HWaddr 00:0a:cd:1e:64:6c 
          inet addr:192.168.80.1  Bcast:192.168.80.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:211 Base address:0xa000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:5707 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5707 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1222111 (1.2 MB)  TX bytes:1222111 (1.2 MB)

pan0      Link encap:Ethernet  HWaddr de:b5:96:6e:d2:a1 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

_______________________
result of dmesg | grep eth1:

[   15.534728] eth1: Identified chip type is 'RTL8168D/8111D'.
[   17.332139] udev: renamed network interface eth1 to eth0
[   17.382097] udev: renamed network interface eth0_rename to eth1
[   30.370848] r8168: eth1: link down
[   30.371212] ADDRCONF(NETDEV_UP): eth1: link is not ready
[  968.810670] r8168: eth1: link down
[  968.811330] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1286.070497] r8168: eth1: link up
[ 1286.071095] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 1286.808195] r8168: eth1: link up
[ 1315.034173] r8168: eth1: link down
[ 1315.809017] r8168: eth1: link down
[ 1317.347774] r8168: eth1: link up
[ 1317.808191] r8168: eth1: link up
[ 1390.934504] r8168: eth1: link down
[ 1390.935402] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1391.932527] r8168: eth1: link down
[ 1393.381991] r8168: eth1: link up
[ 1393.382317] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 1393.932516] r8168: eth1: link up
[ 1515.453913] r8168: eth1: link down
[ 1515.454503] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 1516.452528] r8168: eth1: link down
[ 1517.999381] r8168: eth1: link up
[ 1517.999708] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 1518.452521] r8168: eth1: link up

Ther does'nt appear to be dhcp service on eth1?  Any ideas?


jph

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: Unrecognized NAS but no unrecognized devices.
« Reply #1 on: March 02, 2012, 12:32:31 am »
Enabled DHCP server on internal network in WebAdmin (http://wiki.linuxmce.org/index.php/Network_Settings).  Verified that DHCP leases were issued in WebAdmin/Advanced/Network/DHCP Leases.

 Can see the storage device as a samba share from Kunbutu desktop but still not detected by lmce.

 No unknown devices in WebAdmin/Advanced/Configuration/Unknown Devices.

jph

  • Newbie
  • *
  • Posts: 14
    • View Profile
Re: Unrecognized NAS but no unrecognized devices.
« Reply #2 on: March 02, 2012, 02:32:27 am »
In case this happens to anyone with the same luck as me:

I connected to the drive from my windows network.  The web admin page for the NAS showed zero disks.  During storage, gravity managed to un-seat the SATA from the connector mounted on the case.  The drives are pushed onto the connector from the rear of the chasis.

The drives were re-seated on the connectors and the system was re-started.

The NAS was immediately detected and automatically configured.

/jph