Missing Disk-B???

[Watchman1974]

Hi

Originally all disks were part of the raid5 except for the 3tb one

So there is an issue as only two disks are detected like raid members (C and D)

So need to deepen their status. Please to post

Code: Select all

cat /proc/mdstat
mdadm --examine /dev/sd[abcde]8

How do I do this?

[Jocko]

Hi

So if you are a mac user, open a terminal session and run

Code: Select all

ssh root@nas-ip

(nas-ip is the address ip of your NAS)

and for windows user, you have to install a ssh client like putty (https://www.putty.org/)and then use as host name: nas-ip with port 22 and connection type: ssh

login is root and pwd either giveit2me (default) or your custom password

[Watchman1974]

Hi

So if you are a mac user, open a terminal session and run

Code: Select all

ssh root@nas-ip

(nas-ip is the address ip of your NAS)

and for windows user, you have to install a ssh client like putty (https://www.putty.org/)and then use as host name: nas-ip with port 22 and connection type: ssh

login is root and pwd either giveit2me (default) or your custom password

Thanks...will do that asap. Right now the nas has been stuck for two days redoing the initialize and formatting of the drive.

Setup task reset.sh is now running
Found disk: sdb(Z4Z52BM7)
Delete the partiton table on sdb: OK
Create a new partiton gpt table on sdb:
=>Creating gpt partition table succeeded
Format partition sdb8 with file system ext4:
=>mke2fs 1.43.4 (31-Jan-2017)
Creating filesystem with 487653137 4k blocks and 121913344 inodes
Filesystem UUID: e5b7aa53-2305-4cd4-ab6b-d769de7f05b4
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Allocating group tables: done
Writing inode tables: 550/14882 <---it's been like this for two days..creeping up about 15 a day at this rate.

[Jocko]

Hi

Indeed it is not the expected behaviour (usually this setup job is complete after 20min on a 2TB). So another issue...

Can you reboot the nas (Do not use the button to restart the nas) but the power switch. The setup job should restart

[Watchman1974]

Hi

Originally all disks were part of the raid5 except for the 3tb one

So there is an issue as only two disks are detected like raid members (C and D)

So need to deepen their status. Please to post

Code: Select all

cat /proc/mdstat
mdadm --examine /dev/sd[abcde]8

Is this what you were needing?

root@Lacie:/ # mdadm --examine /dev/sda8
mdadm: No md superblock detected on /dev/sda8.
root@Lacie:/ # mdadm --examine /dev/sdb8
mdadm: No md superblock detected on /dev/sdb8.
root@Lacie:/ # mdadm --examine /dev/sdc8
/dev/sdc8:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x1
Array UUID : 5c92d2fa:eed1ee2a:b4060628:08c23b0a
Name : fvdwsl-base.local:0
Creation Time : Sun Dec 13 07:08:46 2020
Raid Level : raid5
Raid Devices : 4

Avail Dev Size : 3900453200 (1859.88 GiB 1997.03 GB)
Array Size : 5850679296 (5579.64 GiB 5991.10 GB)
Used Dev Size : 3900452864 (1859.88 GiB 1997.03 GB)
Super Offset : 3900453464 sectors
Unused Space : before=0 sectors, after=584 sectors
State : clean
Device UUID : a138b08f:6cdd100d:06afa739:b3ed2b70

Internal Bitmap : -16 sectors from superblock
Update Time : Sun Mar 21 05:45:36 2021
Bad Block Log : 512 entries available at offset -8 sectors
Checksum : 2afa235c - correct
Events : 49368

Layout : left-symmetric
Chunk Size : 512K

Device Role : Active device 2
Array State : A.AA ('A' == active, '.' == missing, 'R' == replacing)
root@Lacie:/ # mdadm --examine /dev/sdd8
/dev/sdd8:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x1
Array UUID : 5c92d2fa:eed1ee2a:b4060628:08c23b0a
Name : fvdwsl-base.local:0
Creation Time : Sun Dec 13 07:08:46 2020
Raid Level : raid5
Raid Devices : 4

Avail Dev Size : 3900453200 (1859.88 GiB 1997.03 GB)
Array Size : 5850679296 (5579.64 GiB 5991.10 GB)
Used Dev Size : 3900452864 (1859.88 GiB 1997.03 GB)
Super Offset : 3900453464 sectors
Unused Space : before=0 sectors, after=584 sectors
State : clean
Device UUID : 6183e541:110637f0:d8adfd04:71257510

Internal Bitmap : -16 sectors from superblock
Update Time : Sun Mar 21 05:45:36 2021
Bad Block Log : 512 entries available at offset -8 sectors
Checksum : 2bf4cd52 - correct
Events : 49368

Layout : left-symmetric
Chunk Size : 512K

Device Role : Active device 3
Array State : A.AA ('A' == active, '.' == missing, 'R' == replacing)
root@Lacie:/ # mdadm --examine /dev/sde8
mdadm: No md superblock detected on /dev/sde8.

[Jocko]

Hi

Yes it is the expected outpout.

But first about sdb, did you abort the setup task or restart it after rebooting the nas ?

Now about raid. sdc8 and asdd8 are raid members of a raid built with only 4 devices (and not 5). Now with only 2 raid members you can not restore the raid even without redundancy. So that means you are lost your data on the raid. So the best way now is to build a new raid.

But I'd rather to check sdb first. Can you post

Code: Select all

tune2fs -l /dev/sdb8

and check its fs

Code: Select all

e2fsck -n /dev/sdb8

[Watchman1974]

Hi

Yes it is the expected outpout.

But first about sdb, did you abort the setup task or restart it after rebooting the nas ?

Now about raid. sdc8 and asdd8 are raid members of a raid built with only 4 devices (and not 5). Now with only 2 raid members you can not restore the raid even without redundancy. So that means you are lost your data on the raid. So the best way now is to build a new raid.

But I'd rather to check sdb first. Can you post

Code: Select all

tune2fs -l /dev/sdb8

and check its fs

Code: Select all

e2fsck -n /dev/sdb8

root@Lacie:/ # tune2fs -l /dev/sdb8
tune2fs 1.43.4 (31-Jan-2017)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 6c62e53b-d792-4910-9711-dff31f98831a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: unsigned_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 121913344
Block count: 487653137
Reserved block count: 4876531
Free blocks: 479722163
Free inodes: 121913333
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 907
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Thu Mar 25 05:14:14 2021
Last mount time: Thu Mar 25 05:30:59 2021
Last write time: Thu Mar 25 05:30:59 2021
Mount count: 1
Maximum mount count: -1
Last checked: Thu Mar 25 05:14:14 2021
Check interval: 0 (<none>)
Lifetime writes: 30 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: ad20a6ec-126c-4592-8e03-08e7b9a42b51
Journal backup: inode blocks


------------------------------------------------------------

root@Lacie:/ # e2fsck -n /dev/sdb8
e2fsck 1.43.4 (31-Jan-2017)
Warning! /dev/sdb8 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sdb8: clean, 11/121913344 files, 7930974/487653137 blocks

[Jocko]

So sdb8 fs seems to be clean(and also mounted) :thumbup

Now I confirm you have no choice about your raid. You have to rebuild it

That means initialize again disk C and D and after build a new raid

[Watchman1974]

So sdb8 fs seems to be clean(and also mounted) :thumbup

Now I confirm you have no choice about your raid. You have to rebuild it

That means initialize again disk C and D and after build a new raid

Well I wasn't able to save any of my data which were lots of movies and personal pictures but at least I have full use of the NAS again. Thanks for the help