itimpi

Moderators
  • Posts

    14122
  • Joined

  • Last visited

  • Days Won

    33

Community Answers

  1. itimpi's post in Upgraded to 6.10.3 should Parity Check Tuning plugin be uninstalled? was marked as the answer   
    You can if you want but there is no need to as the plugin still functions as it has on earlier releases.   The plugin provides more extensive capabilities than the built-in support but if you do not use any of these extra options then less reason to keep it.
  2. itimpi's post in Files and folders disappeared from directory, yet avalible in CLI was marked as the answer   
    @tTownTom  have you checked the permissions at the Linux level on the share and the files in it?  There have been a number of reports of permissions being wrong for network access and it only showing up after upgrading.
     
    it might be worth posting your system’s diagnostics zip file to your next post in this thread to see if anyone can spot something there.
  3. itimpi's post in Drives stay spun up - Reads & writes occurring from unknown source was marked as the answer   
    You might want to check what is in the system share on disk5?   If it is the docker.img or libvirt.img files then having the docker/VM services enabled will keep the disk spinning.
  4. itimpi's post in jumping or skipping disk assignment order? was marked as the answer   
    Unraid does not mind if you leave gaps in the assigned drives.  Many people find it triggers their OCD, but as long as it does not worry you can leave the gaps in the assignments.   When you start the array only the disk slots that have drives assigned will be shown.
     
    Just in case it is relevant it is worth pointing out that Unraid does not care how/where the drive is connected as drives are identified by their serial number.  There is therefore no reason that the assignments to disk slots have to match the physical layout if that is not convenient.
  5. itimpi's post in No devices can see shares or server - Windows/Android/Ubuntu/MacOS was marked as the answer   
    That setting means it will not be visible or accessible on the network.    You need it set to Yes to see it on the network.
  6. itimpi's post in Root Partition is full - can no longer update unraid was marked as the answer   
    How much RAM do you have on the server?    You need a minimum of 4GB to successfully update via the GUI.   If you have less than that you will need to use the Manual upgrade process as described in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.
  7. itimpi's post in Share connection issue was marked as the answer   
    That will be because when you make that sort of change Unraid restarts Samba so any transfer in progress at the time gets aborted.     There has been discussion about changing this to just tell Samba to reread its configuration file but as far as I know that has not happened and I do not know of any immediate plans to make such a change.
  8. itimpi's post in Possible bug/need advice - two disabled data disks (with two working parity) was marked as the answer   
    You can rebuild each disk in turn if that is more convenient.   After the first rebuild succeeds then the array will be back in a protected state.
  9. itimpi's post in This could be bad: Help with parity + data disk errors was marked as the answer   
    If when you got the original failure once you had described your problem and posted diagnostics so we could confirm there was nothing else obviously wrong we could have given you the steps to get Unraid to accept the original parity disk so that you could then probably get an error-free rebuild of disk3.
     
     In principle it is a good idea to ask for help before letting Unraid do anything you are not sure about.
  10. itimpi's post in Drives running hot and unclean shutdown (SOLVED) was marked as the answer   
    This suggests a hardware issue.   I would carefully check your cooling (especially the CPU fan) in case it is thermally related.   Another possibility since you say you recently added new drives would be that the PSU is overloading trying to handle the additional hardware.
     
    As was mentioned the syslog server should allow a software trigger to be eliminated.
     
    Regarding unclean shutdowns you may find this section of the online documentation to be helpful.
  11. itimpi's post in Disk Error - Should I replace the drive? was marked as the answer   
    That shows the extended test failed, so the disk should be replaced.
  12. itimpi's post in How to restrict access to individual files/directories was marked as the answer   
    In theory one could do clever things by going under the hood and manipulating the underlying Linux file/folder level permissions, but in practice for most purposes file security and share level security end up being the same thing when using Unraid.
  13. itimpi's post in Parity Rebuild Confusement was marked as the answer   
    What are the sizes of your data drive and the parity drive?  Once the parity build has gone past the size of a data drive then that data drive can be spun down as it is no longer needed.
  14. itimpi's post in Mover not moving all files from cache was marked as the answer   
    Mover never moves files between pools, only to/from a designated pool and the array.
     
    you either need to do such a move manually or do it in 2 stages - 1 to get files off old cache onto array and then a second one to get files off the array and onto the new cache drive
  15. itimpi's post in Question regarding disk R/W speed was marked as the answer   
    It is not the time to calculate the parity that is the issue, but the disk rotations involved.    This is described here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
  16. itimpi's post in Opening VM strop unraid since installing LSI HBA card. was marked as the answer   
    Did you redo any hardware pass throughs to the VM after plugging in the LSI card?    It is highly likely that the hardware IDs changed after the LSI card was plugged in.
  17. itimpi's post in XFS filesystem corruption but parity version seems fine - best course of action? was marked as the answer   
    Was the disk disabled (had a red ‘x’ showing on the main tab)?  If it was then the disk would have been emulated and the file system check run against the emulated disk, whereas if not it was against the real disk.   The reason I ask is that the rebuild process simply makes a physical drive correspond to the emulated one (including any file system corruption).   If the drive was NOT disabled then it could be worth running the check again this time against the emulated drive to see what that reports.
     
    Do you have a spare disk available to rebuild to?   This is desirable as it means for the time being you can keep the physical problem drive with its contents intact so you have more recovery options if a rebuild is not completely successful.
  18. itimpi's post in cpu stock at 100% - loosing network while copying datas was marked as the answer   
    I thought from you statement that it had not yet completed.   As was mentioned then an automatic parity check after a rebooot suggest that you did not have a clean shutdown of the array.    The plugin would have informed you if it thought that an unclean shutdown had been detected and that was triggering an automatic check.
     
    You might want to read this section of the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
  19. itimpi's post in Cache not working - can't figure out why was marked as the answer   
    The Share Minimum Free Space value is applied when selecting array drives, not when deciding if the cache pool should be used instead of going straight to the array.   Looking at the diagnostics what you have NOT set is the Minimum Free Space value for the cache pool (it is currently set to,0).   You get to this setting by clicking on the pool on the `main tab.
  20. itimpi's post in Unraid installed directly on hard drive was marked as the answer   
    No.  
     
    Unraid is specifically designed to load into RAM from the USB stick on every boot and subsequently run from RAM and use the USB stick for its licence and storing settings.
  21. itimpi's post in Cant add a drive was marked as the answer   
    This is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
  22. itimpi's post in ata3.00: failed command: READ FPDMA QUEUED was marked as the answer   
    Run without the -n option (and if it asks for it add the -L option).  After that you should be able to restart the array in normal mode and I would expect all the data to be intact.
  23. itimpi's post in (SOLVED) Unassigned Devices no longer shared like before was marked as the answer   
    You might want to check that the SMB security setting under Settings->Unassigned Devices is not now set to No when you probably want the (new) Public option.
  24. itimpi's post in Removing Parity was marked as the answer   
    There is nothing relating to parity on the data drives so removing the parity drive will have no effect on them.
     
    Much more likely the difference is due to the version of Unraid used to format the drives.   Newer Unraid releases use a later XFS version which has a larger overhead when formatting a drive.
  25. itimpi's post in containers & /appdata gone after parity rebuild + reboot was marked as the answer   
    According to your diagnostics there are problems with your cache drive so it is not mounting.    That would explain your symptoms.