July 10, 20178 yr Hi There, Hoping someone can please help me with my problem. I am running unRAID 6.3.5 - and starting today I have had intermittent write to server issues from my Win10 machines (x2) ie. I cant in fact write to my unRAID server without getting a 08x8007045D error. (Note: This server is 5 years old and has all the original HW so it may be getting tired?). Issues: I can move and copy files within the server. I can write files from the server to a Win10 machine. I however cant write to the server - from 2 Win10 machines without getting the same 08x8007045D error. (Tested 2 separate Win10 macines to try and eliminate the first one as being the issue) Have rebooted, full power down twice, disk status looks OK. Restarted Win10 machine. Still have the issue. Changes to Server: Installed a larger drive about a week ago i.e. replace old 3 TB with new 8TB - and the server was fine post this change for a week or so. I have attached a log in the hope someone can see something in it which could lead to this error. Thanks in advance! Cheers Ed tower-diagnostics-20170709-2257.zip Edited July 10, 20178 yr by driller3000 Typos
July 10, 20178 yr Errors are related to reiserfs, look into converting to xfs and your troubles will be over.
July 10, 20178 yr Author thanks for the reply re file system. 10 of my 11 disks are reiserfs....should i convert all or is there a troublesome one from the diagnostic that i should start with? Edit: From what I can see its MD5 which cant be written to - which is also the new 8TB - so I am thinking I should target this one? Edited July 10, 20178 yr by driller3000 More info
July 10, 20178 yr Start with that one but you should convert all, xfs has less issues and performes much better.
July 10, 20178 yr RFS disks give trouble as they get full. My guess is that if you have one less than half full, it probably is easier to write to. But this is an old technology, the author is in jail, usage is low, support/testing of even the minute changes it needs from Linux version to version is poor, and it is just bad news.
July 10, 20178 yr Author thanks mate - will be a mission as all my sata ports are in use! so i am thinking i will need to do this? get new 8tb drive to replace an old 3tb drive data rebuild on this new 8tb (which will still be rfs given its a rebuild?) copy data off corrupted rfs md5 to this new 8tb drive reformat md5 to xfs sorted? and possibly moving data on to (and off) this 8tb drive and reformatting now "empty" drives to xfs and then move data back to them? will this work? (hope it makes sense) thanks in advance.
July 10, 20178 yr I'd look to add that 8T drive to the array as an XFS disk and copy the data from as many RFS disks as will fit to it. Then you can reformat those drives as XFS and continue in a similar vein. Getting the 8T formatted as RFS to allow a 3T to be reformatted as XFS seems much less efficient, but you gotta do what you gotta do if you don't have the ability to add another disk to the array. Also see the thread below for the experiences of another user similar to you with a server full of full RFS disks.
July 21, 20178 yr Author Update - And after a freakin long time i have finally: replaced an existing 3TB drive with a new 8TB drive - which the had to have data rebuild of approx 2.8TB. I then had to transfer approx 3TB of data from the old 8TB drive (with the dodge filesystem) - to the new 8TB HDD - to a "Temp" folder as suggested. This took ages as I tried via putty, but this which failed part way through - so I had to do it via network/windows box which was so damn slow : / Reformatted the old dodge 8TB drive from reiserfs to XFS as suggested. Then moved all data from "Temp" folder back to the newly formatted 8TB XFS drive. And ..... I can now write to my server again - Happy days! So............. many thanks for the advice received in the posts above. Cheers Ed PS: Parity Check to come - so hopefully all this moving didn't create a big old mess : /
Archived
This topic is now archived and is closed to further replies.