Raid5 Faile: can not change to fd00

[Draftmancorp]

on what partition do you get this output ?

sda8

[Jocko]

:pound Sorry it is the expected behaviour because it is a raid member now. So abort the command.
You may run instead of

Code: Select all

e2fsck -n /dev/md0

[Draftmancorp]

Code: Select all

Deleted inode 116208 has zero dtime.  Fix? no

^C/dev/sda8: e2fsck canceled.

/dev/sda8: ********** WARNING: Filesystem still has errors **********

root@Norman_Nas:/ # e2fsck -n /dev/md0
e2fsck 1.43.4 (31-Jan-2017)
Warning!  /dev/md0 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
5big2: clean, 15/243781632 files, 15641116/1950234624 blocks
root@Norman_Nas:/ #


[Jocko]

So I think fvdw-sl is now restored on your nas ;)

[Draftmancorp]

So I think fvdw-sl is now restored on your nas ;)

Great news.
i repeated the fsck for the first 7 sda, anything to notice?

Code: Select all

login as: root
root@192.168.1.189's password:
root@Norman_Nas:/ # e2fsck -n /dev/sda1
e2fsck 1.43.4 (31-Jan-2017)
Warning!  /dev/sda1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda1: clean, 6777/128520 files, 214063/514080 blocks
root@Norman_Nas:/ # e2fsck -n /dev/sda2
e2fsck 1.43.4 (31-Jan-2017)
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda2 has been mounted 151 times without being checked, 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/sda2: 5919/64000 files (6.7% non-contiguous), 44759/64000 blocks
root@Norman_Nas:/ # e2fsck -n /dev/sda3
e2fsck 1.43.4 (31-Jan-2017)
Warning!  /dev/sda3 is mounted.
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/sda3

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/sda3 contains a swap file system
root@Norman_Nas:/ # e2fsck -n /dev/sda4
e2fsck 1.43.4 (31-Jan-2017)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda4
Could this be a zero-length partition?
root@Norman_Nas:/ # e2fsck -n /dev/sda5
e2fsck 1.43.4 (31-Jan-2017)
Warning!  /dev/sda5 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda5 has been mounted 589 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 29937 has zero dtime.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (200558, counted=200553).
Fix? no

Inode bitmap differences:  -29937
Fix? no

Free inodes count wrong (52192, counted=52184).
Fix? no


/dev/sda5: ********** WARNING: Filesystem still has errors **********

/dev/sda5: 112/52304 files (6.3% non-contiguous), 8287/208845 blocks
root@Norman_Nas:/ # e2fsck -n /dev/sda6
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/sda6

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/sda6 contains `u-boot legacy uImage, linux-4.14.133-kirkwood-fvdw, Linux/ARM, OS Kernel Image (Not compressed), 4776264 bytes, Wed Jul 17 14:55:42 2019, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0xDC570891, Data CRC: 0x5C8C0EF0' data
root@Norman_Nas:/ # e2fsck -n /dev/sda7
e2fsck 1.43.4 (31-Jan-2017)
Warning!  /dev/sda7 is in use.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda7 has been mounted 596 times without being checked, 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/sda7: 4942/64000 files (0.1% non-contiguous), 42722/64000 blocks
root@Norman_Nas:/ #


[Draftmancorp]

ok, so i'm worried about that phrase.... "filesystem has still error..." can i run a checkdisk or some repair command that can to run all night or next 48H to repair that? or... is it nothing to take seriously?

[Draftmancorp]

So I think fvdw-sl is now restored on your nas ;)

yes, sems yes, i'm in the web interface and see all correctly, like the RAID5 configured on. :applause

Immagine 2022-01-20 204216.jpg

[Jocko]

:thumbup
For today is enough and maybe soon for another fw issue ;)

[Draftmancorp]

:thumbup
For today is enough and maybe soon for another fw issue ;)

yeah, really.
very thanks jocko.

Can i run the Check and repair filesystem on the nas now? and leave it alone for a long time.

[Jocko]

I'd rather you wait the resync job on your raid is complete