November 3, 20169 yr After I updated the server to 6.3 from 6.2. I found that any files that were created when server was 6.2 cannot be deleted. All are mark read only. The security tab has nothing for users, everyone and nobody If I try to edit to allow I get you do not have permission only owner Then Failed to enumerate objects in container. Access is denied.
November 3, 20169 yr Community Expert After I updated the server to 6.3 from 6.2. I found that any files that were created when server was 6.2 cannot be deleted. All are mark read only. The security tab has nothing for users, everyone and nobody If I try to edit to allow I get you do not have permission only owner Then Failed to enumerate objects in container. Access is denied. That is not at all normal. I wonder if one of your drives has some level of file system corruption and is being marked read-only? If you want any informed advice then you should post your diagnostics file (Tools->Diagnostics).
November 3, 20169 yr Community Expert You had some write errors on disk4, they eventually succeeded since the disk was not disabled. but there is filesystem corruption and is read only, you need to check filesystem on that disk. P.S: parity check is scheduled to run daily, is that on purpose?
November 3, 20169 yr Author I do not know how often you should run parity check. So what is a good setting? Also how do I check filesystem? If I pull the number 4 drive and replace it with a new drive will it restore all the files back that were on the old one? I'm still new to this server. Use it as a media server.
November 3, 20169 yr Community Expert https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later Fallow instructions, but basically you need to start the array in maintenance mode and run reiserfsck on disk4 (md4). Most users schedule a monthly parity check, IMO daily it's overkill.
November 3, 20169 yr Community Expert Just to add that SMART for disk4 looks OK, but there could be an issue, start by checking/replacing cables to rule them out.
November 3, 20169 yr Author reiserfsck(space)(underscore underscore)check(space)/dev/md4 get failed to open device
November 3, 20169 yr reiserfsck(space)(underscore underscore)check(space)/dev/md4 get failed to open device Those aren't underscores, they're hyphens! But actually, --check is the default if you don't specify an action, so you could just type reiserfsck /dev/md4.
November 3, 20169 yr Community Expert Then restart array in normal mode and check if you can write or delete files on disk4.
November 3, 20169 yr Community Expert Probably the write errors caused the read only filesystem, before there was actual corruption, check that disk's cables and keep monitoring it for errors.
Archived
This topic is now archived and is closed to further replies.