October 27, 201411 yr I just added a New harddrive, but it won't Connect With the rest of my drives even though its added to the array I need permission to transfer files from and to the drive, which it seems I dont have on my Windows computer. First it says to low memory and asks me to Close programs, before I get the permission error from Windows. Partition 1 size: 3907018532 KB (K=1024) Partition format: GPT: 4K-aligned File sytem type: reiserfs SMB Security Settings Export: Yes Security: Public Why won't it Accept files, when all my settings are correct?
December 30, 201411 yr I'm refreshing this thread since I seem to have the same problem. The new drive show up just fine after installation, but won't accept files that I try to transfer. With MC I get the following message: Cannot create target file "filename.mkv" Read-only file system (30) I've also tried a Telnet session (as described in the manual), without succes. This is driving me crazy, so I'm very grateful for your support!
December 30, 201411 yr I'm refreshing this thread since I seem to have the same problem. The new drive show up just fine after installation, but won't accept files that I try to transfer. With MC I get the following message: Cannot create target file "filename.mkv" Read-only file system (30) I've also tried a Telnet session (as described in the manual), without succes. The read-only file system message indicates that the file system on that particular disk is probably corrupt. You should put the array into maintenance mode and then run reiserfsck --check /dev/md? *where ? corresponds to the disk number) from a telnet/console session. This will check the file system and recommend recovery action if a problem is found. I would suggest that you check back before taking any suggested recovery action as taking an inappropriate one can lead to losing any data that is on the disk in question (although in practise there is a good chance the recommendation will be to proceed with the suggested action).
December 30, 201411 yr @itimpi: thank you very (!) much for helping me out here. The relevant disk is disk7. In maintenance mode I ran reiserfsck --check /dev/md7 was that correct? The check is still running now (checking internal tree). Take care!
December 30, 201411 yr Yes - that is correct. The command can take some time to run (depending on disk size) so make sure if you are using telnet that you do not close the telnet window.
December 30, 201411 yr I guess you are right, this is (the last part of) the output: ....Trans replayed: mountid 2423, transid 72094, desc 506, len 61, commit 568, next trans offset 551 Trans replayed: mountid 2423, transid 72095, desc 569, len 111, commit 681, next trans offset 664 Trans replayed: mountid 2423, transid 72096, desc 682, len 50, commit 733, next trans offset 716 Trans replayed: mountid 2423, transid 72097, desc 734, len 52, commit 787, next trans offset 770 Replaying journal: Done. Reiserfs journal '/dev/md7' in blocks [18..8211]: 52 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Checking Semantic tree: finished 1 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Tue Dec 30 09:30:56 2014 ########### root@Server:/# By the way, I'm not concerned about the data on disk7. Again, many thanks!
December 30, 201411 yr Rerun reiserfsck with --fix-fixable instead of --check and the issue should be resolved. The --fix-fixable option is safe as long as a disk is not physically failing and any existing data should be intact
December 30, 201411 yr Running it now. Any idea what may have caused this? Will report back when done and checked whether it now works.
December 30, 201411 yr Running it now. Any idea what may have caused this? Difficult to say. Most likely cause is a power interruption at an inopportune moment causing a write to be incomplete.
December 30, 201411 yr It's working fine now, just great! For sake of completeness, output below. Thanks for your kind help, Happy New year. ########### reiserfsck --fix-fixable started at Tue Dec 30 10:09:44 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/md7' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will be fixed later. Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 62897 Internal nodes 377 Directories 8 Other files 117 Data block pointers 63644465 (0 of them are zero) Safe links 0 ########### reiserfsck finished at Tue Dec 30 10:24:10 2014 ###########
December 30, 201411 yr Great. It sometimes amazes me how good reiserfsck is at recovering from problems with the file system. Hopefully in v6 the tools for XFS (the new default for file systems) will be as good.
December 31, 201411 yr I probably should open a new thread... As a next step (following the swap disable) I'm trying to replace another drive. I did the steps as per the manual, but after powering up the unit, I am not able to reach the webGUI, nor can I reach the drives with Finder (Mac). I can telnet to the unit It seems the unRAID is not starting the array? Is this normal? Again many thanks. Edit: I just opened a new thread http://lime-technology.com/forum/index.php?topic=37394.0
Archived
This topic is now archived and is closed to further replies.