General NAS-Central Forums

Welcome to the NAS community
It is currently Wed Feb 21, 2018 3:21 am

All times are UTC




Post new topic Reply to topic  [ 18 posts ]  Go to page 1, 2  Next
Author Message
PostPosted: Fri Feb 26, 2016 10:56 am 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
Hallo to all

Since 10 days I have a Lenovo G70-80 laptop with windows 10 Home edition installed.
When I try to connect to my shares on the Medion P89660 NAS the connections got lost and I have to connect them again.
Trying to connect with the webbrowser to the GUI, I can logon. But choosing one of the menu options ie System / administration - settings this causes the NAS in a idle situation. I get a response on a ping but that's about all. I can not get a connection with Putty or the webbrowser or make a network connection to a share.
The only thing I can do is power off / on. Which I don't like to do at all.

Any tips that I can do.

Regards
McMelloW


Top
 Profile  
 
PostPosted: Sat Feb 27, 2016 11:32 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6169
There is a known bug in Samba on most PLX820 based NASses, which causes troubles with modern Samba clients. (link). However, afaik that doesn't affect the web or ssh interface.

The work-around mentioned in the bug report is implemented in the 'Medion tweaks' section of the Tweaks package.


Top
 Profile  
 
PostPosted: Sat Feb 27, 2016 1:32 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
Thanks, I will switch on the Medion tweak and update you on the results

McMelloW


Top
 Profile  
 
PostPosted: Mon Feb 05, 2018 11:15 am 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
Cannot reach this NAS anymore at all. On my router, it is still there. Also with the Advanced IP Scanner I can see it. But no connection is possible, nor with the webbrouwser, nor with Putty and SSH. This was a very bad buy. :-(

So, in order to save as much as possible of this hardware. Is there a way to boot with an USB stick and connect to it this way?

Or can I put another Linux on it with OMV or FreeNAS on it and still use this hardware. I don't know or this possible with this hardware / firmware combination? Haven't found any tips or answers yet.


Top
 Profile  
 
PostPosted: Mon Feb 05, 2018 8:22 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6169
mcmellow wrote:
Cannot reach this NAS anymore at all. On my router, it is still there. Also with the Advanced IP Scanner I can see it. But no connection is possible, nor with the webbrouwser, nor with Putty and SSH.

Does Advanced IP Scanner say anything about open ports? And what is the error when connecting over http or ssh?

Quote:
So, in order to save as much as possible of this hardware. Is there a way to boot with an USB stick and connect to it this way?

No. The SoC can boot from harddisk or flashrom, but not from USB.

Quote:
Or can I put another Linux on it with OMV or FreeNAS on it and still use this hardware.

It is possible to install OpenWRT/LEDE on this box. It might also be possible to install Debian. The latter should allow you to install OMV, but I don't think that will give a good user experience. The box just doesn't have enough juice.


Top
 Profile  
 
PostPosted: Tue Feb 06, 2018 12:21 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
The Advanced Port Scanner shows thes ports: 25, 110, 119, 143, 465, 563, 587, 993, 995
Try to open the backdoor
Code:
http://host/r36807,/adv,/cgi-bin/remote_help-cgi?type=backdoor

results in connection refused. Although it should be open anyway. Is there another trick to open port 22 and ssh?

Putty and the browser both results in a connection refused on this IP address. Medion seeker does not find a NAS in my network.


Top
 Profile  
 
PostPosted: Tue Feb 06, 2018 3:34 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6169
mcmellow wrote:
The Advanced Port Scanner shows thes ports: 25, 110, 119, 143, 465, 563, 587, 993, 995
Are you sure that is your NAS? That are smtp, pop, imap, imaps, pops. Looks more like a mailserver.
Quote:
Is there another trick to open port 22 and ssh?
An FFP-stick might. Depending on what is actually wrong. (It runs a telnet server)
Quote:
Medion seeker does not find a NAS in my network.
A firewall can heavily disturb the seeker.


Top
 Profile  
 
PostPosted: Tue Feb 06, 2018 5:52 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
Mijzelf wrote:
Are you sure that is your NAS? That are smtp, pop, imap, imaps, pops. Looks more like a mailserver.
Yes checked it again, when on and when off.
Quote:
An FFP-stick might. Depending on what is actually wrong. (It runs a telnet server)
Might try this for a start.
By the end of the week I can use a HD-case with SATA to USB. Perhaps I can connect it to a Raspberry and look on the HD and find out something more. Anything particularly where I can look for.


Top
 Profile  
 
PostPosted: Tue Feb 06, 2018 8:22 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
Booted with an FFP-stick
After the boot Advanced Port Scanner discovered the following information
Code:
DIMWL-NAS
Besturingssysteem:
IP:              192.168.xxx.xxx
MAC:      00:11:41:00:00:00
NetBIOS:
Gebruiker:
Type:

Service      Details
FTP              Pure-FTPd
Gedeelde map   SMI-USB-DISK-11001
Gedeelde map   geneadata
Gedeelde map   admin
Gedeelde map   music
Gedeelde map   photo
Gedeelde map   video
Gedeelde map   public
Port 25    (TCP)
Port 110    (TCP)
Port 119    (TCP)
Port 139    (TCP) Samba smbd 3.X workgroup: WORKGROUP
Port 143    (TCP)
Port 465    (TCP)
Port 563    (TCP)
Port 587    (TCP)
Port 631    (TCP) CUPS 1.1
Port 993    (TCP)
Port 995    (TCP)

The server name, IP and Mac are the correct ones. I am not able to connect with telnet port 23; or FTP via the browser. Still connection refused


Top
 Profile  
 
PostPosted: Wed Feb 07, 2018 4:09 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6169
mcmellow wrote:
Booted with an FFP-stick
The stick is not initialized properly. Maybe the timing bug. Else the share SMI-USB-DISK-11001 wouldn't have been there. It would have been 2 shares, with other names. (ffpboot and ffproot, or something like that).
Quote:
Although it should be open anyway.
Why?

Now I see that the samba shares are available, including a custom 'geneadata', which means that the firmware is running normally, except for the webserver.

Did you install any 3th party packages, which might be able to bring down the webinterface?


Top
 Profile  
 
PostPosted: Wed Feb 07, 2018 8:49 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
Mijzelf wrote:
Why?
I did the "backdoor trick" via the browser. Then I changed something, I don't remember what, in order to use ssh via Putty. I did used this for a great number of times. But it does not work any more.
Quote:
Now I see that the samba shares are available, including a custom 'geneadata', which means that the firmware is running normally, except for the webserver.

Did you install any 3th party packages, which might be able to bring down the webinterface?
Installed the MetaRepository and some of the packages of it.


Top
 Profile  
 
PostPosted: Thu Feb 08, 2018 7:19 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6169
mcmellow wrote:
Mijzelf wrote:
Why?
I did the "backdoor trick" via the browser. Then I changed something, I don't remember what, in order to use ssh via Putty. I did used this for a great number of times. But it does not work any more.

I think you installed the dropbear package.
Quote:
Quote:
Now I see that the samba shares are available, including a custom 'geneadata', which means that the firmware is running normally, except for the webserver.

Did you install any 3th party packages, which might be able to bring down the webinterface?
Installed the MetaRepository and some of the packages of it.
AFAIK all 3th party packages are safe. Some ZyXEL packages are not, like OwnCloud, which will bring the webinterface down. But in that case dropbear should still work.
Are the shares normally accessible? If not, maybe you have a disk problem.


Top
 Profile  
 
PostPosted: Thu Feb 08, 2018 8:43 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
I can see the shares in the port scanner. But I can not reach them. Connection refused. I am afraid it is a disk problem. So I have to wait until the disk case with sata to usb arrives and see or I can reach the disk in that way.


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 6:55 pm 
Offline

Joined: Mon Aug 11, 2014 6:06 pm
Posts: 17
mcmellow wrote:
So I have to wait until the disk case with sata to usb arrives and see or I can reach the disk in that way.

I was able to connect the Medion NAS harddisk to my Raspberry Pi and mount the disks.
fdisk -l gives the following output on the harddisk
Code:
Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x146f79bb

Device     Boot   Start        End    Sectors  Size Id Type
/dev/sda1            63    1028159    1028097  502M 83 Linux
/dev/sda2       1028160 3907024064 3905995905  1.8T  9 AIX bootable

I am able to mount /dev/sda1 and /dev/sda2 and copied all user-data to another disk via the Raspberry Pi. :)
This the result for e2fsck /dev/sda1
Code:
root@mcmellow-pi:~# e2fsck /dev/sda1
e2fsck 1.43.4 (31-Jan-2017)
/dev/sda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda1: 103/128520 files (1.9% non-contiguous), 370003/514048 blocks

And this the result for e2fsck /dev/sda2
Code:
root@mcmellow-pi:~# e2fsck /dev/sda2
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sda2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/sda2 contains a xfs file system

Is it possible to repair this second partition again?
Or just recreate it and format it again?
Put something total new on it to improve the NAS?


Top
 Profile  
 
PostPosted: Thu Feb 15, 2018 8:16 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6169
It's an xfs filesystem, so e2fsck is not the right tool for the job. Try xfs_repair. (Maybe you'll have to install xfs-tools).


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 18 posts ]  Go to page 1, 2  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 9 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group