Save original firmware for later restoration

[fvdw]

the database is saved on partition 5 in folder /etc
It has one copy in there called back but also one if you used the save database menu option in the root of partition 5.

So this disk gives the correct data using smart commands.
Then if you 5big2 is running with the new disk in slot 1 (sda) the only way to find out what is wrong is putting it (your nwsp2 disk) in slot 2 of your 5big2
(remember slot 1 is the most lefthand slot seen from the back).
If it boots and you have ssh access we are going to explore what is wrong.
It must be something specific with this disk

If it is up and running connect with ssh and please do

Code: Select all

dmesg
fdisk -l
gdisk -l /dev/sda
gdisk -l /dev/sdb

post output before doing anything else

[fvdw]

ps yur wd has a very high loa cycle count

193 Load_Cycle_Count 0x0032 160 160 000 Old_age Always - 122327

This a known problem for WD disks from this series it can cause early failure
http://idle3-tools.sourceforge.net/

I compiled a program that you can run on the nas to change a firmware setting to increase time before disk heads are unloaded
viewtopic.php?f=27&t=1798&hilit=idle3&start=70#p14680

[matzi]

dmesg appended

root@fvdwsl-base:/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdb: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 267350 2147483647+ ee EFI GPT

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 9 72 514080 83 Linux
/dev/sda2 73 136 514080 83 Linux
/dev/sda3 137 200 514080 82 Linux swap
/dev/sda4 201 121601 975153532+ 5 Extended
/dev/sda5 209 312 835380 83 Linux
/dev/sda6 321 328 64260 83 Linux
/dev/sda7 337 400 514080 83 Linux
/dev/sda8 409 121601 973482772+ 83 Linux

root@fvdwsl-base:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************

Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): BBE8B823-3E9D-4893-A5AF-47511D55E102
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 647636 sectors (316.2 MiB)

Number Start (sector) End (sector) Size Code Name
1 128520 1156679 502.0 MiB 8300 Linux filesystem
2 1156680 2184839 502.0 MiB 8300 Linux filesystem
3 2184840 3212999 502.0 MiB 8200 Linux swap
5 3341520 5012279 815.8 MiB 8300 Linux filesystem
6 5140800 5269319 62.8 MiB 8300 Linux filesystem
7 5397840 6425999 502.0 MiB 8300 Linux filesystem
8 6554520 1953520064 928.4 GiB 8300 Linux filesystem

root@fvdwsl-base:/ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 4883781168 sectors, 2.3 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 8881F69B-DDDA-4396-9C1F-A2687B0CD75C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 4883781134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3565 sectors (1.7 MiB)

Number Start (sector) End (sector) Size Code Name
1 2048 1034239 504.0 MiB EF00
2 1034240 2064383 503.0 MiB 0700
3 2064384 3096575 504.0 MiB 8200
4 3096576 3098623 1024.0 KiB 0700
5 3098624 4704255 784.0 MiB 0700
6 4704256 4720639 8.0 MiB 0700
7 4720640 5750783 503.0 MiB 0700
8 5750784 4883779583 2.3 TiB 0700

[matzi]

dmesg is a ascii file, rename

[fvdw]

ok thank you, the WD 2.5 TB disk is in slot 2 (0:2:0:0) and the 1 TB Samsung disk is in slot 1 (0:3:0:0)
the kernel loads the disk ok and it sees all the partitons

Code: Select all

[   17.340316] scsi 0:2:0:0: Direct-Access     ATA      WDC WD25EZRX-00A 80.0 PQ: 0 ANSI: 5
[   17.348766] fvdw1 disk index before get_sd_name = 0
[[   17.353679] device-name= sata_mv
[   17.356893] fvdw2 disk index after get_sd_name = 1
[   17.361691] fvdw3 prefix[0]=s  prefix[1]=d
[   17.365766] fvdw4 diskname = sdb
[   17.369367] sd 0:2:0:0: [sdb] 4883781168 512-byte logical blocks: (2.50 TB/2.27 TiB)
[   17.377638] scsi 0:3:0:0: Direct-Access     ATA      SAMSUNG HD103SI  1AG0 PQ: 0 ANSI: 5
[   17.385763] sd 0:2:0:0: [sdb] 4096-byte physical blocks
[   17.391300] sd 0:2:0:0: [sdb] Write Protect is off
[   17.396073] sd 0:2:0:0: [sdb] Mode Sense: 00 3a 00 00
[   17.396387] fvdw1 disk index before get_sd_name = 1
[   17.401330] device-name= sata_mv
[   17.404543] fvdw2 disk index after get_sd_name = 0
[   17.409311] fvdw3 prefix[0]=s  prefix[1]=d
[   17.413480] sd 0:2:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   17.423328] fvdw4 diskname = sda
[   17.426943] sd 0:3:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[   17.435910] sd 0:3:0:0: [sda] Write Protect is off
[   17.440731] sd 0:3:0:0: [sda] Mode Sense: 00 3a 00 00
[   17.440835] sd 0:3:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   17.464390]  sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8
[   17.472243] sd 0:2:0:0: [sdb] Attached SCSI disk
[   17.497291]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
[   17.505377] sd 0:3:0:0: [sda] Attached SCSI disk

what does the commands give as output

Code: Select all

fdisk -l
and gdisk -l /dev/sda
gdisk -l /dev/sdb
mount

[matzi]

fdisk and fdisk commands are in my last post.
mount gives

root@fvdwsl-base:/ # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=1,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 ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)

[fvdw]

sorry I had to scroll down the window the find fdisk and gdisk

that all looks ok

But sdb8 is not mounted
That means the disk isn't visible in webinterface but also the shared folders on partition 8 of that disk will not be visible
It should have been mounted automatically at boot
We need to find out why it fails to mount

We will try to see if it is mountable at all:

Code: Select all

cd /
mkdir /share/1001
mount /dev/sdb8 /share/1001

If that works then te problem must a setting in de nas database file
Can you put your nas conf database file (nas_conf_db.xml) in a zip file
It is in rw_fs/etc

[fvdw]

I edited above post

[matzi]

Yes sdb8 mount without problems. All files are present.

[fvdw]

the database is missing the info for sdb

it mentions also that it is a single drive system

Code: Select all

      <platform>5big2</platform>
      <drives>SingleDrive</drives>

It should mention MultiDrive
So the script that updtaes the dtabase didn't find sdb at boot, reason to be found.
But first following
Is this the database that is present in /rw_fs/etc ?
(as it should not have the name nas_conf_db_ok.xml but the name nas_conf_db.xml)
It also misses other tags that should be added automatically. So is this really the dtabase used by the nas
PS If you overwrite the database when the nas is running this can give very strange behavior.

You are running 15.2-patched, what patches did you install ?

I just released 15-3 for 5big2
You could upgrade the system disk to 15-3 (take out the nwsp2 disk during the upgrade, just to be sure)
After upgrading switch it off and put the nwsp2 disk in and boot