leorait

Well then, at least apparently I didn't lose any important files, so for the manual labor of recovering them. Again, thank you all for helping!

That hit right in the bullseye 🎯 I Could only manage to go pick up a couple of new sata cables today, replaced them and did a parity check that ran smoothly in under 6 hours. I Can't thank you enough for the help! I would've easily replaced a disk before thinking in the cable itself! One last question before tagging it as solved, is there any way to automatically manage all the files in the "lost+found" bin? it happened just in the day that i archived all of 2020 files, so theres a loooooot of random named folders and files

Hello there everyone. I'm experiencing my first big batch of problems with my NAS, so i'm here asking for a little bit of help. My system is around 1 year old and it is a basic storage server for my small office with an light VM for basic tasks. The problems started back in mid december with the big thunderstorm season, after a powersurge fried my ups and led to some unclean shutdowns of the machine in the following weeks. After an unclean shutdown due to a power outtage in 01/06, i booted up the machine and the system wouldnt find one of the disks. This problem was easily solved by switching the hard drive power cable, resulting in the system finding the drive and starting the array normally. I Got a new UPS the next day, and the machine ran smoothly for a couple days, but then out of nowhere in the midle of a work day we lost acess to the files in the NAS, the array was stopped at the system tab with the same disk labelled "unmountable: no file system" This filesystem check with the -L flag fixed that granting me acess to the files in the array, and i though the system was running just fine, with the exception that a lot of files and folders were randomly scrapped into an "lost+found" folder wich are stil to be salvaged. The scheduled parity check started a couple days after. The parity check usualy takes 6~8 hours, but when i got to check up the machine on the next day the system prediction was around 28 days, and i could hear the hard drive bay of the case making some noises. In the log i could see that the noises where in sync with the "ATA bus error" messages, afraid this could physically dammage the disk i end the parity check, and for the last 4 days we've been using the NAS normaly and i don't know how to proceed. How do i know this one drive should or not be replaced? What is the reason behind this problem with the parity check? What can i do with the best interest of not losing any data? Attached to this post there is an Syslog right after the attempted parity check and an overall diagnostics. Thanks in advance! syslog.txt drv-0-diagnostics-20210121-1743.zip

As time pass by, i'm getting used to the ideia that i am no longer the tech nerd i once was. Just last week i could't pay a bill via my bank app, and as i furiously got to my Manager, she just said "have you allowed the app to use the camera on android?" and at that moment i felt like a good 96 year old boomer, but i digress. The thing is, today i run a small architecture office and properly managing files from the 2 years that we're running its getting pretty tricky, so i decided to turn one of our old desktops into a NAS with the ability to set a VM for light photoshop and autocad work. As economy colapses here in Brazil, this will be a very tight budget build, hence, i'm here to log my build and ask for assistence to the community once i figure out how much i'll be screwing it up. The PC configuration righ now it is: Core i7 4770 16gb DDR3 Motherboard ASUS h97-plus Samsung EVO SSD 240gb 500W power suply. The parts i got to complete this build: 3x Ironwolf NAS HDD 4tb AMD 6670 graphics card (got it for free) Last year was a pretty itense year here in the office, and the total data production here including all the media was around 1.5tb, so i'm hoping that setting one hd for parity we can get at least 4 years of run time before adding more storage. The cpu is a hyper threaded 4 cores, so i'm hopping to set 2 cores for the NAS and 2 for the VM, we use each pc local drives for ongoing work, and would be using the NAS just for plain storage, so i'm hoping the 2 cores will be able to take care of that. The two things that worry me the most are: 1 - this is a basic motherboard, i don't know if it will bottleneck at some moment. 2 - Graphics card is turning 10 years old, i got it just to output video for the VM, since the processes we will run on that are mainly cpu-heavy. Once the drives get delivered i'll start the build and log the aftermath, but if anyone can spot any possible hardware incompatibilities that i'm unaware of i'll be glad to hear it!