February 17, 20188 yr I seem to have a disk that is readonly but I have run the check on it and it said it was fine but still the drive is readonly Here is the output - you can see the check run OK and then I try to create a directory and it says readonly root@Tower:~# reiserfsck --check /dev/md1 reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Sat Feb 17 11:00:15 2018 ########### Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 170253 Internal nodes 1096 Directories 6290 Other files 268870 Data block pointers 154182244 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Sat Feb 17 11:10:18 2018 ########### root@Tower:~# cd /mnt/disk1 root@Tower:/mnt/disk1# cd * root@Tower:/mnt/disk1/Backups# mkdir Test mkdir: cannot create directory ‘Test’: Read-only file system Any ideas how to get this drive back? Thanks
February 17, 20188 yr 12 minutes ago, Blade said: Filesystem seems mounted read-only. Skipping journal replay. Reiserfsck did find that it was mounted read-only. Try removing the --check flag and change it to be --fix-fixable. And don't forget that reiserfsck has to be run with the array started in Maintenance mode Side note, you really should at some point convert your reiser drives over to be xfs. ReiserFS is no longer a recommended filesystem. Edited February 17, 20188 yr by Squid
February 17, 20188 yr Author Thanks Is there a how to for converting the drives or will I lose everything on them?
February 17, 20188 yr Author Here are the results of the fix-fixable Not sure why it is saying it is bad I just put this drive in to replace the old drive - it is only 1 week old root@Tower:~# reiserfsck --fix-fixable /dev/md1 reiserfsck 3.6.27 Will check consistency of the filesystem on /dev/md1 and will fix what can be fixed without --rebuild-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 ########### reiserfsck --fix-fixable started at Sat Feb 17 11:46:33 2018 ########### Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (337379328): (Input/output error). Aborted
February 17, 20188 yr Author When I look at the unraid web page it says the device is disabled contents emulated WTH - drive is brand new
February 17, 20188 yr Not really surprising. Since at least the 14th, the drive has been having continual resetting links (ie: its up and down). (Over 181 hours, you've had 76882 UDMA CRC errors) Yesterday due to this, it kept on getting read errors (which did wind up being rewritten to the drive based upon parity and the other drives), and then today when it tried to do the same thing, the disk failed on the write. You really should reseat all cabling to the drive, check any power splitters, etc. This could also be related to you using a Marvel controller. Marvel's are sometimes notorious for dropping drives, and an LSI based controller is what is recommended. Either way, you're going to have to rebuild the drive (Stop Array, Unassign the drive, start array, stop array, reassign the drive, start array)
February 17, 20188 yr Author Is there a way to just reformat that drive as XFS and start over with it - I am ok to lose the data on it
February 17, 20188 yr You could do a tools - New Config. Reassign all of the drives, and check off that Parity is already valid. This will get the drive back in the array without having to rebuild it. Then stop the array, from the main tab, click on the drive and change it's format to be XFS then when you start the array you'll be prompted if you want to reformat it. But, none of this addresses all of the CRC problems you've had. This is more important, as it directly will affect your ability to rebuild any drive should it require it.
February 17, 20188 yr 6 minutes ago, Blade said: Is there a way to just reformat that drive as XFS and start over with it - I am ok to lose the data on it You can always reformat an array disk. The format is nothing but data to unRAID, and parity will be reflected. The easiest way is to stop the array, and change the filesystem on that drive to RFS or BTRFS. Then start the array. it will appear unformatted, and you can format it to the new FS. Then you can stop the array again, change the filesystem back to XFS, and start the array again. The disk will again show unformatted, and you can format it to XFS. You now have a freshly formatted XFS disk.
February 17, 20188 yr Community Expert Definitely replace that SATA cable and make sure notifications are enable, would've been warned about all those CRC errors.
February 17, 20188 yr Author I did a new config and have it formatted with xfs but it still says device is disabled contents emulated.
February 17, 20188 yr Community Expert A new config would not keep any emulated disk, you likely missed a step.
Archived
This topic is now archived and is closed to further replies.