driller3000

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 : /

Cool - will read and go from there. Thanks again.

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.

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?

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

Thanks Johnnie - will do. Cheers Ed

Hi Again, So now server just randomly became unavailable. Added kb and monitor again - and unRAID had rebooted for some random reason - but of course given issues above - could not reboot unRAID by itself. So override boot again to force it boot off the flash drive and the server is back up again. Q: Does this - combined with the initial problems noted above sound like a failing MB to you? Or something else? Thanks again. Cheers Ed

Thanks again Johnnie I have tried to find these settings just now as best I can and have enabled them - but seemingly no joy.... Anyhoo.....will try again tomorrow - I have my unRAID server back and am so stoked about this!! - but I have been banging my head against this for a little while now - so will instead enjoy a movie from unRAID with a beer and give it another crack tomorrow. And again - I appreciate your help : )

Thanks for the quick reply. As far as I could tell with the MB I have (ie. Gigabyte Technology Co., Ltd. - H61MA-D3V) I have to choose UEFI to get the USB selected - and as you say this doesn't work for unRAID - so again it would not boot. I did however set the Boot Override to the correct USB drive (which was listed as some weird no. "8.07" in the drive list) and !! It booted to unRAID - happy day. : ) (Note: I did have another drama with my main windows machine not being able to see unRAID - DNS server issue - but a restart of said windows machine fixed this.) So it works...however when I reboot it still fails to choose the flash drive and so it fails to boot unRAID again. So Boot Override to the rescue again - however I don't want to have plug a kb and monitor in and Boot Override every time I reboot or power-down unRAID. So.......new question that I would appreciate some assistance with please: 1. Does anyone know how I can make this MB not "demand" UEFI (perhaps the fw update has forced this?) - so that it will see the same old flash drive as it has quite happily done for 4 years now - until this latest issue. 2. And/or avoid having to manually intervene and have to Boot Override every time my server is rebooted /powered down? Thanks in advance. Cheers Ed

Hi There, As per title. Was installing a new HDD - but unRAID server wouldn't power on after I installed the HDD (it was a squeeze so I did wonder if I borked something) - so I removed the new HDD - still wouldn't power up - so I took the server to a local computer shop. They diagnosed it as corrupt MB FW so they reflashed it. So now the system powers up - I can access Bios etc - I can see all HDD's and the raid card - boot option is set to UEFI USB (which I believe is correct?) - but it now wont boot from the USB flash drive - and this USB has been sweet for 2 years or so now. I had backed up the flash drive before heading to the computer shop - so I wondered if the USB had been corrupted somehow - so I reformatted the USB - and copied the unRAID backup across - made it bootable - but unRAID still wont boot. So I will hit up Lime to see if we can reinstall unRAID to a new USB and see if this is the issue. But do you my fellow unRAID'rs - have any other thoughts / options? Thanks in advance. Regards Ed