D2 Network 2 esata support

D2 Network 2 esata support

Postby Aled72 » Wed Feb 14, 2018 4:32 pm

disk problem solved. it seems that formatting the disk in linux the partition table was not to liking. anyway now I have installed.
only the problem of the esata disc remains that is not seen.
Do I have to activate something?
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby fvdw » Wed Feb 14, 2018 5:05 pm

It is seen as an external disk and should be visible as shared folder assuming it has a 1 partition on it with fat32 or ext3 or ext4 or ntfs file system
fvdw
Site Admin - expert
 
Posts: 13245
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: D2 Network telnet refused.

Postby Aled72 » Wed Feb 14, 2018 5:09 pm

I see this:
root@BackupNas:/dev # fdisk -l

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 242252 1953514583+ ee EFI GPT

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 242252 1953514583+ ee EFI GPT
root@BackupNas:/dev #

I must format sdb8 in ext4?
I need to see for build the raid
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby Aled72 » Wed Feb 14, 2018 5:35 pm

Another information if i look in web interface where i can initialize disks, i read:
sdb
Unformatted
1863.02 GB At least one partition is currently mounted as an USB share

I format in ext4 with web interface tool but the status don't change.
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby Jocko » Wed Feb 14, 2018 5:52 pm

Hi

a d2nw2 uses the same kernel as a 5big2. I tested with success the esata ports on my 5big2, so it should work on your NAS.

Aled72 wrote:Another information if i look in web interface where i can initialize disks, i read:
sdb
Unformatted
1863.02 GB At least one partition is currently mounted as an USB share

I format in ext4 with web interface tool but the status don't change.
Yes it is the way to initialize an usb so that it be managed as an internal disk.

But if you do not enable the option "Advanced mode" from the usb-disk menu (please to read also its help page), its partition is mounted as an USB share.
Please to note this option is available only if no partition is mounted. So click on the button "Saferemove" to unmount it and then you should be able to enable the advanced mode.

Restart the NAS and your esata disk should be managed as an internal disk
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: D2 Network telnet refused.

Postby Aled72 » Thu Feb 15, 2018 3:38 pm

If I connect the other disk via usb I see the sharing, but in esata I do not see it.
Also in the initialization section, if connected in esata it always indicates it as unformatted. In USB it sees it formatted in ext4.
Is it possible, according to you, to create the raid via shell?
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby Jocko » Thu Feb 15, 2018 4:07 pm

Hi Aled72,

Please to post a screen capture of your usb-disk menu when a disk is plugged in a usb port and in the esata port
Aled72 wrote:Is it possible, according to you, to create the raid via shell?
Yes, but I'd rather you make it via the web-interface.
When you have en "esata disk", post :
- The screen capture of the main disk setup menu
- The screen capture when you click on the related volume name of the esata disk
-
Code: Select all
cat /proc/partitions
mount
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: D2 Network telnet refused.

Postby Aled72 » Fri Feb 16, 2018 2:20 pm

Situation when disks are connected via USB.
Disk setup screen:
download/file.php?mode=view&id=5116
Usb disk screen:
download/file.php?mode=view&id=5117
Test Linear Raid Build:
download/file.php?mode=view&id=5118
Raid Fail with this error:
download/file.php?mode=view&id=5119

I try to change all two disks with other but the result is always the same.

Code: Select all
root@BackupNas:/ # cat /proc/partitions                                     
major minor  #blocks  name                                                   
                                                                             
   1        0       4096 ram0                                               
   1        1       4096 ram1                                               
   1        2       4096 ram2                                               
   1        3       4096 ram3                                               
   1        4       4096 ram4                                               
   1        5       4096 ram5                                               
   1        6       4096 ram6                                               
   1        7       4096 ram7                                               
   1        8       4096 ram8                                               
   1        9       4096 ram9                                               
   1       10       4096 ram10                                               
   1       11       4096 ram11                                               
   1       12       4096 ram12                                               
   1       13       4096 ram13                                               
   1       14       4096 ram14                                               
   1       15       4096 ram15                                               
  31        0        500 mtdblock0                                           
  31        1          4 mtdblock1                                           
   8        0 1953514584 sda                                                 
   8        1     524288 sda1                                               
   8        2     524288 sda2                                               
   8        3     524288 sda3                                               
   8        4       8192 sda4                                               
   8        5     786432 sda5                                               
   8        6       8192 sda6                                               
   8        7     524288 sda7
   8        8 1950612551 sda8
   8       16 1953514584 sdb
   8       17 1953512519 sdb1
Code: Select all
root@BackupNas:/ # mount
/dev/sda1 on / type ext3 (rw,relatime,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sda8 on /share/1000 type ext4 (rw,noatime,nodelalloc,data=ordered)
/dev/sdb1 on /share/2000 type ext4 (rw,noatime,nodelalloc,data=ordered)
/dev/root on /lacie-boot type ext3 (rw,relatime,data=ordered)
root@BackupNas:/ #

Next post I will paste esata screens
You do not have the required permissions to view the files attached to this post.
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby Aled72 » Fri Feb 16, 2018 2:35 pm

esata connection situation

DiskSetupScreen:
The esata disk not present:
download/file.php?mode=view&id=5120

in USB disk screen the disk is not present:
download/file.php?mode=view&id=5121

if I enter in initialize section the screen is this:
download/file.php?mode=view&id=5122

Note: the disk is formatted ext4 but the system don't see it. If I initialize again the screen remain this.

Code: Select all
root@BackupNas:/ # cat /proc/partitions                                     
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
   1        8       4096 ram8
   1        9       4096 ram9
   1       10       4096 ram10
   1       11       4096 ram11
   1       12       4096 ram12
   1       13       4096 ram13
   1       14       4096 ram14
   1       15       4096 ram15
  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0 1953514584 sda
   8        1     524288 sda1
   8        2     524288 sda2
   8        3     524288 sda3
   8        4       8192 sda4
   8        5     786432 sda5
   8        6       8192 sda6
   8        7     524288 sda7
   8        8 1950612551 sda8
   8       16 1953514584 sdb
   8       17 1953512519 sdb1
Code: Select all
root@BackupNas:/ # mount                                                     
/dev/sda1 on / type ext3 (rw,relatime,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime,mode=600)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/sda8 on /share/1000 type ext4 (rw,noatime,nodelalloc,data=ordered)
/dev/root on /lacie-boot type ext3 (rw,relatime,data=ordered)


Many thanks for all help that you give me.
You do not have the required permissions to view the files attached to this post.
Aled72
Donator VIP
Donator VIP
 
Posts: 73
Joined: Sun Feb 04, 2018 3:27 pm

Re: D2 Network telnet refused.

Postby Jocko » Fri Feb 16, 2018 3:23 pm

First, I discourage strongly to use a linear device or a raid0 for storing backup as soon as you will get an issue with one disk, you lose all your backup !
So you should use a raid1.

Currently, you have an issue if you have sdb plugged in an usb port (id issue but I think understand why) and in the other case (esata port) you have at least two issues 1/the firmware think the partition is currently mounted as an USB share (which is wrong) 2/nas database is not updated and there is no setup for your esata disk

Point 1/ is a cosmetic bug (I forgot to remove an always true test I added to check the menu). It is just an informative message
Point 2/
aled72 wrote:Note: the disk is formatted ext4 but the system don't see it.
No, the system sees it, disk and its partitions are listed in /proc/partitions. So no issue on the esata port but only a nas database issue.
So do
Code: Select all
 /etc/api/nasapi.php "mrvlGetDisk high all"
/etc/api/nasapi.php "mrvlGetVolume high all"

unplug your disk and do
Code: Select all
echo > /var/log/messages
debugon
plug again your disk, wait around 30'' and do
Code: Select all
debugoff
cat /var/log/messages

Now for usb case, plug your disk in the usb port and post
Code: Select all
 /etc/api/nasapi.php "mrvlGetDisk high all"
/etc/api/nasapi.php "mrvlGetVolume high all"
usb_id -x /block/sdb|tr "\n" " "|awk -F '[ =]' '{print $10"-"$14"_"$2"_"$4}'
(I assume its kernel name is still sdb)
Jocko
Site Admin - expert
 
Posts: 11367
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Next

Return to Lacie D2 network vs2

Who is online

Users browsing this forum: No registered users and 2 guests

cron