What does this mean in syslog?

[pras1011]

This comes up as a warning:

 

Mar 3 09:17:22 Unraid kernel: REISERFS warning (device md4): super-2030 reiserfs_fill_super: This file system claims to use 1 bitmap blocks in its super block, but requires 89408. Clearing to zero.

[JorgeB]

Check filesystem on disk4

[pras1011]

how?

 

Maintenance mode and then click check?

[JorgeB]

https://lime-technology.com/wiki/Check_Disk_Filesystems

[pras1011]

Thanks. I have started a check.

[pras1011]

reiserfsck 3.6.27

Will read-only check consistency of the filesystem on /dev/md4
Will put log info to 'stdout'
###########
reiserfsck --check started at Sat Mar  3 09:50:16 2018
###########
Replaying journal: 
Replaying journal: Done.
Reiserfs journal '/dev/md4' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..  finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
	Leaves 1914354
	Internal nodes 11417
	Directories 25
	Other files 308
	Data block pointers 1937249787 (0 of them are zero)
	Safe links 0
###########
reiserfsck finished at Sat Mar  3 12:28:38 2018
###########

 

So now what do I have to do?

[JorgeB]

Covert to xfs, reiser is dead.

[pras1011]

Taking a guess: That error occurred when I replaced the 8tb drive with a precleared 12tb drive. Drive md3 had the same error log. I think this error is about preclear starting at position one and resier didn’t like it.


Sent from my iPhone using Tapatalk

[JorgeB]

Not likely, preclear doesn't write nothing except zeros to where the partition (filesystem) is going going to be.

[trurl]

16 minutes ago, pras1011 said:

Taking a guess: That error occurred when I replaced the 8tb drive with a precleared 12tb drive. Drive md3 had the same error log. I think this error is about preclear starting at position one and resier didn’t like it.


Sent from my iPhone using Tapatalk

Are you talking about this?

 

-a      = start partition on sector 63. (default when on unRAID 4.X)

-A     = start partition on sector 64. (not compatible with unRAID 4.6 and prior)
            On unRAID 4.7 and subsequent, the -a or -A default is set based on the value
            set on the Settings page in the unRAID web-management console.
            Both of these (-a and -A) are completely ignored on disks > 2.2TB as they 
            use a GPT partition that will always start on a 4k boundary.

[pras1011]

Yes. I was talking about that. Wrong guess then! But I saw that preclear started at position 1.

 

I am currently checking MD3. Apart from switching to xfs, I assume that there is nothing else I can do?

 

 

Sent from my iPhone using Tapatalk

 

 

[JorgeB]

2 minutes ago, pras1011 said:

Apart from switching to xfs, I assume that there is nothing else I can do?

IMO you should still switch to xfs, not because of that error, that was a just warning (and corrected) and if no corruption was detected all should be fine now.

[trurl]

1 hour ago, pras1011 said:

switching to xfs

I assume you know that changing the filesystem on a disk will format it?

[pras1011]

Yes.


Sent from my iPhone using Tapatalk