• Posts

  • Joined

  • Last visited

  • Days Won


Community Answers

  1. itimpi's post in How do I increase the storage of my pool? was marked as the answer   
    You click on the pool on the Main tab; scroll down to the Balance section; select the Single option from the dropdown and then start the Balance as described here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
  2. itimpi's post in [SOLVED] Help with "Unmountable: Wrong or no file sysem" was marked as the answer   
    That looks as if no major corruption was found.
    You need to run without the -n option if you want anything to be fixed, and if it asks for it add the -L option.
    Restarting in normal mode should mean the drive then mounts OK.   Look to see if you now have a lost+found folder - if not all data should be intact.
  3. itimpi's post in Upgrade from 6.9.2 to 6.10.0, all drives wrong (pool and cache) was marked as the answer   
    it looks like disk have slightly different ways of reporting their serial numbers under 6.10.0 on your system.

    You should be able to:
    Use Tools->New Config and use the option to keep all assignments return to the Main tab and correct all drives to have their new version of the serial numbers tick the “Parity is Already Valid” checkbox start the array and with any luck everything will now come up as normal.
  4. itimpi's post in How long does it take to add a parity disk to the array was marked as the answer   
    Just realised that I did not answer this bit.  In this case the time to rebuild a drive is determined by the size of the drive being rebuilt (at the same 2-3TB per hour estimate as used for the parity build) so if the disks are smaller than the parity drives it does not take as long.
    Another way to look at it is that both processes involve writing to every sector on a drive so how quickly that can be done is the determining factor.
  5. itimpi's post in Please Help - Array device Disk 3 Not Installed, drive now in Unassigned how do I put it back in the array? was marked as the answer   
    I assume the disk that should be disk3 is the one with WSD0QVWE as its serial? My guess would be that you disturbed its connection when adding the drives you now want as Unassigned drives.   It is showing up OK in the SMART reports and it looks OK there.
    Does Unraid show that disk3 is currently being emulated?   If so check that the emulated disk has the content you expect as the process for getting it back into the array involves rebuilding the drive with the contents that are shown as present on the emulated disk3 by stopping the array; assigning the disk as disk3; and restarting the array to rebuild the physical disk3 to match the emulated one.
    if the emulated disk3 does NOT show the expected content then do not rebuild but post back here for advice.
  6. itimpi's post in all unraid domains moved from array disks to cache disk was marked as the answer   
    If the vdisks were in the 'domains' share then this is set with
    shareUseCache="prefer" which meant you WANT the files on the cache, and if mover finds them on the array it should move them to the cache (space permitting).
    You also do not have a Minimum free Space set for the cache, and it is a good idea to have this set to be at last the size of largest file you expect to copy there in normal use at it is not unusual for corruption to occur if is gets completely full.
  7. itimpi's post in 6.10 Cannot connect to running VM was marked as the answer   
    Have you tried clearing cookies/cache in your browser (or using incognito mode).
  8. itimpi's post in [SOLVED] Proper procedure to upgrade Parity HD and Data HD in a 4-bay system was marked as the answer   
    The 2 step procedure is the way to go.  
    At each stage make sure you keep the disk just removed with its contents intact until that stage has successfully completed as that gives you a fallback option if anything happens to go wrong.
  9. itimpi's post in My unraid server has no internet connection. was marked as the answer   
    The syslog suggests you are getting a crash in the driver that handles your NIC.   It might be worth trying the 6.10-rc8 release to see if that has an updated driver/kernel that works OK on your hardware,
  10. itimpi's post in All Dockers Restart Every Morning was marked as the answer   
    You have the CA Backup plugin scheduled to start at 6:00 am every day and that will be what is stopping the containers until the backup is finished.
  11. itimpi's post in Is it possible to use the same usb stick for /isos/ ? was marked as the answer   
    True - that is a limitation you cannot workaround.
    You can do it from the GUI, but you would not be able to use the drop downs for selecting a path - you have to enter it manually.
  12. itimpi's post in Different sized cache disks was marked as the answer   
    It depends on the BTRFS profile they are set to use.   The default is raid1 and that means they are protected, but the usable space is only that of the smaller device.
  13. itimpi's post in How to install Clear An Array Drive script to remove an existing disk from unraid was marked as the answer   
    I think you have to copy/paste it into a new script entry within the User Scripts plugin.
  14. itimpi's post in GPU Statistics not showing AMD GPU was marked as the answer   
    I think you have two conflicting requirements here?    If you have the GP’u isolated so that it can be passed through to a VM then it is not visible at the Unraid level and needs to be controlled from within the VM.
  15. itimpi's post in apcupsd shell scripts overwritten on reboot was marked as the answer   
    After initial boot Unraid runs from RAM so the /etc location is only in RAM and (as you found) not persistent.  If you want to make such a change persistent then you need to apply it every boot.  This is typically done either by adding appropriate entries in the /config/go file on the flash drive or by using the User Scripts plugin.
  16. itimpi's post in XFS formatting outside Unraid for drop in migration was marked as the answer   
    The easiest thing would be to plug the drives into Unraid as Unassigned Devices and use the UD plugin to partition and format them correctly for Unraid (as XFS or BTRFS) drives.   You can then use them on other systems to add files and when you add them to Unraid (as long is there is no current parity drive) then Unraid will accept them and leave their data intact.
  17. itimpi's post in Disk no longer readable was marked as the answer   
    Handling of unmountable disks is covered here in the online documentation that can be accessed via the Manual link at the bottom of the GUI. 
  18. itimpi's post in Plex on Cache & Array??? How to get back to Cache Only? was marked as the answer   
    If the folder really is empty then you can safely delete it. Nod sure why it was created in the first place if it really is empty.
    It should also get removed if you:
    Disable the Docker service (under Settings->Docker) to ensure it is not holding anything open at that location Run mover manually from the Main tab to move any files that might be there to the cache. Re-enable the Docker service.
  19. itimpi's post in Converting disk to vm using qemu-img convert was marked as the answer   
    This will not work as you cannot expose the raw disk over the network.
  20. itimpi's post in Array dead - I killed 2 drives, only had 1 parity - learning/practice opportunity for me was marked as the answer   
    You can use Tools->New Config to reset the array and assign the surviving  array drives as you want them.  When you start the array then these assignments are committed and parity (if you have assigned one) is rebuilt from the remaining drives.   Unraid will recognise the drives that have previously been used by Unraid and will leave their data intact.
    Since each drive in an Unraid array is a free-standing file system they can also be read individually when not part of the array.   Easiest is some sort of Linux system as it will have built in support for the file systems used by Unraid.
  21. itimpi's post in PreClear Failure Suggestions was marked as the answer   
    This disk looks a bit sick going by the SMART information:
    Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Reallocated_Sector_Ct 0 24 Up 24 Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Power_On_Hours 22 67 Up 45 Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Reported_Uncorrect 0 9 Up 9 Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Airflow_Temperature_Cel 28 30 Up 2 Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Current_Pending_Sector 0 8 Up 8 Apr 15 16:02:12 preclear_disk_ZL24A79Y_23305: S.M.A.R.T.: Offline_Uncorrectable 0 8 Up 8
    As this is a new disk then it sounds as if it was damaged in transit and you should RMA it.  For instance on a new drive you would expect Reallocated Sectors and Pending Sectors to be 0.
  22. itimpi's post in Shutdown and later reboot auto working...but was marked as the answer   
    If you are running the script via the User Scripts plugin then including the line
    #noParity=true in the script will achieve this
  23. itimpi's post in Cannot start array or do parity swap after failed data drive was marked as the answer   
    That screenshot shows 2 drives missing or failed but only single parity so Unraid cannot do the parity swap.
  24. itimpi's post in Cache Unmountable: No File System was marked as the answer   
    Those ‘critical medium error’ messages almost certainly mean that the SSD is faulty.
  25. itimpi's post in Indicator on Shares tab of export status was marked as the answer   
    Isn’t that already there?  
    blank = not exported
    italics = exported (hidden)
    normal case = exported