Hi,

 

Have a problem, hoping to get some help. In 'fix common' problems plug-in I see a message:

"Unable to write to disk5   -  Drive mounted read-only or completely full..."

I also see i/o occurred error messages on the console at times for /dev/md5, which still happen after the disk replacement.

 

I replaced the disk (disk 5) which turned out to be (I thought) /dev/md5 with a new disk, it rebuilt... and now I still see the same message.... I wonder if I replaced the wrong disk? if /dev/md5 wasn't actually disk 5?

 

When I tried to add a share I get a message "Share test has been deleted."

 

attached are my diags.

 

THANK YOU!

unraid-nas-diagnostics-20170208-0907.zip

You need to check file system on disk5 (md5):

 

https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later

So the actual old disk hardware is probably is fine?, it's the file system that needs to be checked? I went through that before replacing the disk, but didn't run the repair portion.... the process wanted me to run a -rebuild, not a fix-fixable. I figured replacing the disk would avoid having to run the repair... I guess I was wrong.... I saw i/o errors on /dev/md5 in the logs, thought it was hardware.

 

Is this also why I can't add a share?, it keeps deleting my shares.

 

I'll run through the disk check process now on the new disk I guess.

 

Thank you!

Reuben

The current problem is file system corruption, you can post the old disk SMART report.

 

Replacing a disk won't fix the file system but the old disk could be bad and have file system issues.

Hi,

 

I ran the rebuild an the below is what I received, yet still disk5 /dev/md5 is coming up as read-only... This is a totally different new, bigger disk... 4tb replacing the old 1tb...

 

root@UNRAID-NAS:~# reiserfsck --rebuild-tree /dev/md5

reiserfsck 3.6.25

 

*************************************************************

** 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.                **

*************************************************************

 

Will rebuild the filesystem (/dev/md5) tree

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

Filesystem seems mounted read-only. Skipping journal replay.

###########

reiserfsck --rebuild-tree started at Wed Feb  8 10:49:04 2017

###########

 

Pass 0:

####### Pass 0 #######

Loading on-disk bitmap .. ok, 219397368 blocks marked used

Skipping 38019 blocks (super block, journal, bitmaps) 219359349 blocks will be read

0%....20%....40%....60%....80%....100%                      left 0, 37356 /sec

16793 directory entries were hashed with "r5" hash.

        "r5" hash is selected

Flushing..finished

        Read blocks (but not data blocks) 219359349

                Leaves among those 217279

                Objectids found 16795

 

Pass 1 (will try to insert 217279 leaves):

####### Pass 1 #######

Looking for allocable blocks .. finished

0%....20%....40%....60%....80%....100%                          left 0, 84 /sec

Flushing..finished

        217279 leaves read

                217279 inserted

####### Pass 2 #######

Flushing..finished

Pass 3 (semantic):

####### Pass 3 #########

... MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]/aerofgt.flvvpf-10680: The file [9 16] has the wrong block count in the StatData (6360) - corrected to (1880)

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 17] ("tektagtjb.flv") in directory [4 9] points to nowhere - is removed

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 18] ("drmario.flv") in directory [4 9] points to nowhere - is removed

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 19] ("hijngi.flv") in directory [4 9] points to nowhere - is removed

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 20] ("viostorm.flv") in directory [4 9] points to nowhere - is removed

... AME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]/hanaawas.flvvpf-10680: The file [9 22] has the wrong block count in the StatData (4408) - corrected to (2328)

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 23] ("raveracw.flv") in directory [4 9] points to nowhere - is removed

... MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]/samsho2.flvvpf-10680: The file [9 53] has the wrong block count in the StatData (8712) - corrected to (1144)

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 54] ("attila.flv") in directory [4 9] points to nowhere - is removed

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 55] ("alpine.flv") in directory [4 9] points to nowhere - is removed

... AME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]/megablst.flvvpf-10680: The file [9 58] has the wrong block count in the StatData (4624) - corrected to (2200)

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 59] ("chameleo.flv") in directory [4 9] points to nowhere - is removed

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]rebuild_semantic_pass: The entry [9 60] ("burglarx.flv") in directory [4 9] points to nowhere - is removed

... rspin/MAME/MAME [Videos][FLV][240p][MAME .144][EM 20111210][HyperSpin 1.0]vpf-10650: The directory [4 9] has the wrong size in the StatData (158048) - corrected to (157760)

/MAME/ARCADE_C_Drive.v2ivpf-10680: The file [2 5] has the wrong block count in the StatData (718822912) - corrected to (718818176)                                                                                        rebuild_semantic_pass: The entry [4 7] ("ARCADE_C_Drive003.v2i") in directory [2 4] points to nowhere - is removed

/MAMErebuild_semantic_pass: The entry [4 6] ("ARCADE.sv2i") in directory [2 4] points to nowhere - is removed

/MAMEvpf-10650: The directory [2 4] has the wrong size in the StatData (376) - corrected to (304)                                                                                                                                      rebuild_semantic_pass: The entry [2 16795] ("1035382439.tmp") in directory [1 2] points to nowhere - is removed

vpf-10650: The directory [1 2] has the wrong size in the StatData (168) - corrected to (136)

Flushing..finished

        Files found: 16669

        Directories found: 114

        Names pointing to nowhere (removed): 12

Pass 3a (looking for lost dir/files):

####### Pass 3a (lost+found pass) #########

Looking for lost directories:

Flushing..finishede 1, 0 /sec

Pass 4 - finished done 205560, 79 /sec

        Deleted unreachable items 76569

Flushing..finished

 

The partition is mounted ro. It is better to umount and mount it again.

 

Syncing..finished

###########

reiserfsck finished at Wed Feb  8 13:33:32 2017

###########

 

 

I ran it but wasn't in maintenance mode! So running it again (now in maintenance mode) and it doesn't look good the test is showing a lot of errors (like below).. I have this data somewhere else, how may I just start clean with this particular disk?

 

Thank you!

 

...

bad_item: vpf-10570: block 97631264: The item header (0) has not cleaned flags.   

...

If you have the data probably best.

Thank you, so what is the best way to do this? Delete all the data from the drive? How to start over, eliminating the file system corruption...?

Format the disk, click on it on the main page, change file system to xfs,  start the array and you'll have the option to format it.

 

Can't see why but if you want to keep it reiserfs do the same thing again and change fs  back to reiserfs and format again.

Thank you, I was able to solve this with the rebuild -tree option...

You mentioning formatting as xfs, there is an advantage to that fs? Can I format it with xfs right from inside the UNRAID?

 

Thank you again,

Reuben

http://lime-technology.com/forum/index.php?topic=37490.0