Jump to content

Meph

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Meph

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Found some forum posts about the same issue i had... turned out i had a logfile growing out of control. over 18GB ... i have now cleaned that file... everything sorted
  2. Thank you! I had the same issue here.. Did not know how this docker stuff does work. But I searched the same error message you had on google and found this article.. My docker image size were already at 20. Set it to 25 now and it started up! What is stored in that image file? and how do i access that data? hmmm i can see that my dockers (plex and resilio sync) writes to /mnt/user/appdata/ folder.. But that isnt the image file, is it?
  3. @Frank1940 Yes, I agree.. I would never use this disk with those many errors.. It's in the pile marked as "Defective" and is going to the recycling center next time im going there.. One thing is strange though. The report for this disc tried to upload as usual to the developer of the plugin, but upload failed. I tried like 3-4 times.. All other reports (like 10-15 reports) have reported just fine. This is the only report where the preclear plugin did not run to the end.
  4. Squid is the leader so far with 75027 hours for a Seagate Barracuda Green 2TB (5900rpm) SATA 3 (6Gb/s) disk! Thats 8.5 years in runtime!!! wow
  5. What is the oldest disk you are running/have seen in working condition in relation to S.M.A.R.T attribute number 9 = Power_On_Hours? I have a 300GB Seagate Barracuda 7200rpm (SATA) disk here with power on hours = 57711 .. Thats over 6,5 years in runtime! This disk has been running in a file server in a RAID5 setup (4disks) for quite some time. It has now been decommissioned by me.....
  6. Ok, this is the infamous Seagate 3TB disk.. I bought 4 of them and now 3 of them has failed... But they are old now.... 1 of the disks still tests fault free... But i will keep an eye on it.. Changed from QNAP to unRAID also because it offers more security in case QNAP hardware fail or the RAID5...
  7. Just of curiosity.. How could SMART report this disk as PASSED??? It failed the post-read verification and the disk does not look healthy at all.... Also the google forms failed to upload this report.. I let it sit for 5 minutes before i reloaded the webpage to get it to respond and then clicked dismiss. The next report that were ok were possible to upload fine in 2 secs.
  8. I can confirm this change works! This should be a setting that is made in unRAID when it is installed. Because default: allocation roundup size = 1048576 creates problems in shares when trying to copy files and reports wrong size used in Windows. I tried to copy 800GB of data to my unRAID server but got the message that the data would not fit even though i had 2TB free.. This made me find this thread... The correct setting should be: allocation roundup size = 4096 Setting this was a little unclear cause another guy talked about changing in a file on the USB... Here is the correct way to change it (It's often not explained in this forum i have noticed): In the unRAID web GUI (v6.3.5) click Settings -> SMB (under Network Services) then you add "allocation roundup size = 4096" (without the " ") in the text box "Samba extra configuration".. After that im not 100% sure if the settings will take effect or if you have to stop and then start the array.. I ended up with rebooting unraid after that it is working correctly! Finally! Maybe someone could report this as a bug (or change request)? Or I will when i get the time in a few weeks or so... Below you can see the that the allocation size has changed.. Size on disk: now shows 4KiB instead of 1MiB!
  9. Could it be the version and FW of the hard disks creating this problem maybe? Since the problem is not occurring for the other disks... Instead of trying a next release on my production stuff i will put in another disk of the same brand and see if that creates the same SMART problem, then i will install unRAID on another server and try the next release there to see if that fixes the issue. It will take me a month to fix this though... This issue is not that serious though, but it is annoying.. I can still access the SMART information and that is important to be able to catch errors happening... But i cannot run any SMART self-tests though.. witch might be a problem...
  10. Ok this is strange... Explains why.. BUT.. From the beginning when i installed unRAID i was able to access the SMART test. Because i did ran a test on all disks.. So it has been working but is not working since i used the green button in [Main] window to spin the disks down since they were not going to be used for a while. After i did that the problem started with accessing the SMART buttons...
  11. Another thing that is strange.. The other "working disks" (where I can start a SMART self test) they have the status: [active/idle] .. But the two disks that SMART test is unavailable have the status [idle] .... What is the difference between [active/idle] and [idle]? [Parity Disk] root@Tower:~# hdparm -C /dev/sdg /dev/sdg: drive state is: active/idle [Disk 1] root@Tower:~# hdparm -C /dev/sde /dev/sde: drive state is: active/idle [Disk 2] root@Tower:~# hdparm -C /dev/sdf /dev/sdf: drive state is: active/idle [Disk 3] root@Tower:~# hdparm -C /dev/sdd /dev/sdd: drive state is: active/idle [Disk 4] root@Tower:~# hdparm -C /dev/sdb /dev/sdb: drive state is: idle [Disk 5] root@Tower:~# hdparm -C /dev/sdc /dev/sdc: drive state is: idle
  12. Yes it does. Drives changes from idle -> standby when checking with hdparm -C root@Tower:~# hdparm -C /dev/sdb /dev/sdb: drive state is: standby root@Tower:~# hdparm -C /dev/sdc /dev/sdc: drive state is: standby But in the web interface of unRAID i cannot see any difference.. Except when i click a disk on mainpage to see the SMART attributes and the "Spin Up" button. The SMART attribues takes 2 seconds to load (probably because the disk have to spin up again)...
  13. root@Tower:~# hdparm -C /dev/sdb /dev/sdb: drive state is: idle root@Tower:~# hdparm -C /dev/sdc /dev/sdc: drive state is: idle
  14. Nope, that does not work. I have both tried the "Spin Up" button and also the grey button on main page.. The button on the main page goes green but i still see the message "Unavailable - disk must be spun up" and the SMART tests are unavailable...
  15. It's a copy/paste of the main page.. hold on, ill make a screenshot and also attach diagnostics.. give me a minute or two