Read Only Shares

[dasoul]

I have been having issues writing new files to my smb shares.  All of my disk show green in unraid.  So I have been assuming this was some permissions issue because I use the Active Directory integrated option and I had to prevously remove the unraid system from the domain and readd it.  But now I really want to write new files to the system. 

 

In the logs I see entries like this.  These are older entries but there are entries dated for today that have the exact same messages and disk/device:
 

Quote

Jun  4 02:21:40 UNRAID kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 60241 does not match to the expected one 2
Jun  4 02:21:40 UNRAID kernel: REISERFS error (device md6): vs-5150 search_by_key: invalid format found in block 171915940. Fsck?

I went to run the fsck command with the --rebuild-tree option and the message dissuaded me from letting it continue so I cancelled the reiserfsck run.
 

Quote

************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** *************************************************************

I have extra disks I can install into the system but wanted to check for guidance just to make sure I go about this the right way.  BTW my diagnostics are attached.  Any help would be greatly appreciated.  Thanks!

unraid-diagnostics-20220101-1259.zip

[Squid]

Did you run reiserfsck with --check first and did it tell you to run --rebuild-tree?  or did you simply run --rebuild-tree (iirc the first thing --check usually says to do is run with --fix-fixable)

[dasoul]

6 hours ago, Squid said:

Did you run reiserfsck with --check first and did it tell you to run --rebuild-tree?  or did you simply run --rebuild-tree (iirc the first thing --check usually says to do is run with --fix-fixable)

I just clicked the button that ran the reiserfsck without options.  I dont know what options it used by default.  But the check came back with some errors specifically about the rebuild-tree option.  So I researched that option and put it in to run it as options and saw the other message.

 

Thanks!

[Squid]

You pretty much have to run it.  And begin to think about converting from ReiserFS to XFS.  Reiser hasn't had any updates in years upon years and never will again and eventually may cease to work on future kernel versions.

[dasoul]

On 1/1/2022 at 9:03 PM, Squid said:

You pretty much have to run it.  And begin to think about converting from ReiserFS to XFS.  Reiser hasn't had any updates in years upon years and never will again and eventually may cease to work on future kernel versions.

Thanks.  It completed and now I can write to my shares.  I appreciate it!  Now to figure out how to get everything over to XFS.  I do have alot of new drives to put in the system.  Is it still recommended to preclear drives before putting them into the array?  Is that a thing with XFS?

[itimpi]

22 minutes ago, dasoul said:

Is it still recommended to preclear drives before putting them into the array? 

This is purely a user choice and has been for some time.  It all depends on whether you want the extra confidence in drive health the pre-clear gives and thus think the time it takes is a good trade-off.

[Squid]

27 minutes ago, dasoul said:

Is it still recommended to preclear drives before putting them into the array?

Personally, I can't be bothered.  But I also never use a shucked drive where I'm voiding the warranty by pulling it.  The real reason for pre-clear being introduced wasn't to gain confidence in the drive (although that is a side-benefit) but because on versions of the OS 1.x -> 5.x when adding a new drive to the system you couldn't use the shares at all until the OS cleared the drive -> hence the need for pre-clearing.  Versions 6.x will allow you to use the system while the drive is being cleared.

 

Vast majority of drive "issues" are purely cabling problems.  Actual defective drives etc are rather rare.  But it is a personal preference related to your own comfort level.