Max

Members
  • Posts

    262
  • Joined

  • Last visited

Everything posted by Max

  1. when i try to copy paste a file i get this error although i do end up with a copy of that file in my external hardrive. Cannot chown target file "/mnt/disks/Elements/RARBG.txt" Operation not permitted (1) and when i try to copy a folder im getting this error again, it makes a folder in external hdd with same name but without its content. Cannot chown target directory
  2. @JorgeB hey another thing that i just noticed is that just now i created a new share and i set it specifically write to disk 1 and their in that share i was able to write data to disk1 but if did the same thing to my older share and tried to write to it, i get error stating that my disk is write protected.
  3. Do I really need to use those, cause I still can normally browse/read any data of off it. I just can't right now. Can't just attach a external HDD and copy all my data through unassigned devices. And again we still don't know if it's my ram or not cause we thought replacing might fix this but I'm still getting those errors. Thing is ddr3 is bit more on expensive over here now. I paid like 70 USD for 8 gig stick and I will have to get one more to use my vm and I really don't wanna spend another 70 bucks on 4-5 year old system which I'm already planning on upgrading for a part that might be faulty.
  4. Okay I have replaced my ram and I'm still getting that same error while writing to disk 1. Disk1 is still goes forced read only mode. What should I do next ?
  5. okay i stopped my array and i wont use it again and replace my ram first thing in the morning and then what would i need to do make my disk1 writeable again or its like if its ram then it will disk1 will become writeable again ??
  6. okay okay i will get new rams tommorow but meanwhile i thought of replacing those corrupt files on disk as they were only two but now i can't write to disk1. syslog shows this error Mar 17 00:02:04 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:04 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:04 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:05 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:05 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:07 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:07 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:07 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:07 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:07 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:09 Unraid kernel: btrfs_validate_metadata_buffer: 3 callbacks suppressed Mar 17 00:02:09 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:09 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:09 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:09 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:09 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:09 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:10 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:10 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:10 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:10 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: btrfs_validate_metadata_buffer: 21 callbacks suppressed Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:15 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:16 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:17 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:17 Unraid kernel: BTRFS error (device md1): bad tree block start, want 210731008 have 0 Mar 17 00:02:20 Unraid kernel: BTRFS: error (device md1) in btrfs_finish_ordered_io:2736: errno=-5 IO failure Mar 17 00:02:20 Unraid kernel: BTRFS info (device md1): forced readonly what can i do to fix this.
  7. okay thanks for all the help mate and i should definetly replace my ram right ??
  8. Can scrub help me fixxing this @JorgeB
  9. @JorgeB disk1 Error summary: csum=311 Corrected: 0 Uncorrectable: 0 Unverified: 0 disk2 Error summary: verify=27 csum=26789 Corrected: 0 Uncorrectable: 0 Unverified: 0
  10. @JorgeB sorry for disturbing you again and again but the wierdest thing just happened with me just a minute ago memtest86 finished without any error, so after that i checked and realized that my kingston hyperx ram does support xmp profiling so im running it on stock clock which is 1866 and then i booted unraid to try your data recovery suggestions but now all those files which were unreadable earlier, are now working fine. so as i dont want to corrupt my data (specially if its not corrupt already) i immediately stopped the array. so what should i do now ?? could i use my server normally thinking it was just fluck and it wont happen again or i should just stop thinking about using my server without new rams.??
  11. @JorgeB what should if memtest can't find any errors, cause now out of 4 it has already passed 2 without any error although now it is showing a note that ram may be vulnerable to high frequency row hammer bit flips, so this be relevant here.
  12. @JorgeBdoesn't parity helps with data restoration or parity does work that way or its cause both my disks are showing data corruption so my one parity drive cant help me. and what should be my next step if memtest can't find any errors cause so far it is showing zero errors. and one more thing when i tried to launch memtest from unraid boot menu, it just rebooted my system so i downloaded passmark's memtest86 v9.0, i hope its good enough.
  13. guys im thinking suddenly today my files became somehow corrupt cause at first plex was showing errors, at first i thought maybe their something wrong with plex so then i tried watching them directly through file explorer and it failed then i tried copying those files which somehow now are unplayable and it failed to even copy those media files. file explorer is saying some unexpected network error occured when i try to copy them. so what should i do, should trying running parity, please help and just to make it clear not all my files are showing this strange problem some of them are still working fine. unraid-diagnostics-20210315-2105.zip
  14. spin down delay is set to 15 minutes earlier when it was working, which was before rc1 it was set 1 hour but when i updated to rc1 and noticed spin down isn't working anymore i tried it with 15 minutes and turned all dockers down to make sure its not one of docker which is actually causing this. which u know obviously didn't help cause if it did i wont be here😅. so yeah now all my disks are set 15 minutes. yeah i know and i have set it scan library only when a change is detected, so in way we can say that is constantly keeps looking for a change but i dont know how this works, exactly. But im 100% sure this is not the problem cause then my disks wouldn't spin down before i moved to rc1 too, plus ever since i posted OG post my disk are all spun down (which i did myself using web gui) and plex (no one is actually watching anything) is still running actually all my dockers are running. And i already told u that turning all dockers down doesn't help. and thiss too.
  15. ohh i didn't even knew it was set to that but the only time i could remember when i fideled with those settings was probably when i first added cache drive which was way back so i think that couldn't hav affected but i dont know for sure. so i will change it and see if it makes any difference. yeah they could but the only dockers that could cause that are qbittorrent and plex. so in my cause they aren't a problem as qbit is set cache only share and i can make sure no one is using plex and even if i shut down all my dockers, my disks still dont spin down on their own. Plus i have a disk under unassigned drives which don't use for anything even that disk doesn't spin down.
  16. Guys ever since i updated to rc1 my disk are not spinning down, if i spin them down myself then it works and they stay down until i try to access any data off of those drives, so looks spin down and spin up is working its just spin down isn't working on its own. at first i thought maybe it is some bug with rc1 and it will get fixed after an update cause it was working great before but even after updating to rc2 them haven't spin down not even once own their own. So if anyone knows why this could be happening or how maybe how can i fix this then please help. unraid-diagnostics-20210125-1402.zip
  17. fixed it by updating to rc2 from rc1 but disk temps are not showing up now. unraid-diagnostics-20201220-0030.zip
  18. One problem doesn't go away completely and another comes knocking at my door. Now VM is behaving strange suddenly it has decided that from now it won't need vbios of my GTX 1070 ti it will work without it. But the real problem is now VM is sluggish and if I remove my GPU drivers it's working normally but as soon as I install GPU drivers it starts acting sluggish again.
  19. reaseating flash fixed it. i blame it all on 2020!!!!
  20. no need to apologize u were only trying to help me. but just so u know that would not have been an issue cause my disks are perfectly lined the way the are on unraid main page so that wouldn't have been an issue. i am using usb2 yeah i know that was dumb of me. but lets forget all that as now i have even bigger problem. i was thinking that after a reboot i start by formating my disk and see what all i have lost and start downloading stuff that i have lost but now i cant even access my web gui
  21. well i guess now i will have to source my media files like movies and tv shows again and fortunately i still have copy of all my college projects on my laptop. well thanks for all help. well i guess i just learned parity doesn't equal to backup the hard way. for future safety i guess creating a seperate backup is the only option. right ??
  22. @trurl hey forget about filesystem for a second here, if we get it to emulate again can't we just copy all disk2's data somewhere.
  23. so that means my parity is corrupt. and no i dont have backup.
  24. and why wouldn't just formating my disk 2 on some other machine and then pluging it back as new drive and rebuilding won't work as parity still can be used to recover my data right ? and instead of paying for software can't i just get a new drive and rebuild my data like as if drive 2 has failed