Jump to content

Max

Members
  • Posts

    262
  • Joined

  • Last visited

Posts posted by Max

  1. 3 minutes ago, JorgeB said:

    Not much more I can help then, you can try the mailing list or IRC like mentioned in the FAQ.

    wouldn't just formating my disk 2 and then rebuilding it with parity, would work and should i try those check btrfs check repair option.

  2. 25 minutes ago, Max said:

    @JorgeB should i try this now.

    btrfs restore -v /dev/sdc1 /mnt/disk2/restore

    and i think i will have switch disk2 with disk1 in this command, right ?

    okay so that command gives me this error

    root@Unraid:~# btrfs restore -v /dev/sdc1 /mnt/disk1/restore
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    Ignoring transid failure
    WARNING: could not setup extent tree, skipping it
    Couldn't setup device tree
    Could not open root, trying backup super
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    Ignoring transid failure
    WARNING: could not setup extent tree, skipping it
    Couldn't setup device tree
    Could not open root, trying backup super
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    parent transid verify failed on 592523722752 wanted 183547 found 16228
    Ignoring transid failure
    WARNING: could not setup extent tree, skipping it
    Couldn't setup device tree
    Could not open root, trying backup super

     

    even trying -vi option ends up with same error.

  3. 6 minutes ago, JorgeB said:

    Yep, you can't do that with a btrfs filesystem and then rebuild, or always mount them in read-only mode if doing it without parity, if not the trans id of the rebuilt disk won't match, and this error is fatal, best bet it to try the btrfs restore option here.

    i ended up with this error.

    root@Unraid:~# mkdir /x
    root@Unraid:~# mount -o usebackuproot,ro /dev/sdc1 /x
    mount: /x: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.

    what should i do ??

  4. 6 hours ago, trurl said:

    It was showing as mounted in those first diagnostics you posted at the top of this thread. Maybe we should have assigned parity disks also when looking for your flash backup. We'll see what happens and what can be done after rebuild finishes.

    okay rebuild just finished but still disk 2 is showing up as unmountable : not mounted.

    here is the diagnostics after its done rebuilding

    unraid-diagnostics-20201219-1453.zip

  5. 4 minutes ago, trurl said:

    That looks OK so far. How does it look on the Main page?  Under Array Devices you should see mostly Writes to disk2 and mostly Reads from all other disks and no Errors on any disks. What does it look like under Array Operation?

    so far 0 errors and everything looks fine except disk 2 is currently showing unmountable : not mounted, not sure whether it was showing up as unmountable the last time it was data rebuilding or not.

    7 minutes ago, trurl said:

     I would expect 4TB rebuild to take less than 12 hours.

    around 7 hours

  6. 4 minutes ago, trurl said:

    If you booted up with config/super.dat from your backup, then you should have exactly the same disk assignments you had when the backup was made. 

    my super.dat is named super.dat.CA_BACKUP could that be the issue.

     

    6 minutes ago, trurl said:

    Is anything else working like you expect?

    i have not started my array yet so  can't about vm or dockers but plugins are showing up fine

  7. 1 minute ago, trurl said:

    Do you mean you found your flash backup? Did you copy the config folder from that backup to your flash drive? The config folder has all of your configuration, including your disk assignments.

    yes i found my flash backup and i copied everything from it not just config folder.

  8. 30 minutes ago, trurl said:

    Prepare a new install, assign your disks just as they were but don't assign any disk to any parity slot. That will be enough to get to your files and find the flash backup. Hopefully disk2 will mount without needing rebuild.

    okay so after restoring my flash both disk 1 and disk 2 are coming as they should but pairty drive is still showing up as unassigned. so i guess i will have recreate the parity. right ?

    or is their a way around it??

  9. Just now, trurl said:

    Yes but take diagnostics with array started.

    okay but the problem is my unraid usb decided to die on me in a middle of this😭 and stupid old me never tried backing it up.

    and now when i tried running chkdsk afterconnecting it to my laptop it reported that its filesystem is raw so it can't be fixed.

    Sooo????

  10. 6 minutes ago, trurl said:

    Check connections, SATA and power, both ends, including splitters. Make sure connections sit square without any tension on cables that might disturb them, and don't bundle cables.

     

    Then post new diagnostics.

    so first shutdown the server then check all cables splitters etc and then start the server and take diagnostics before reenabling disk 2. right ?

  11. so guys almost a week back from now my disk 2 was showing showing disk read errors during parity run, so i requested for help over here, so after looking at my diagnostics @JorgeB suggested that its most likely is a cable issue so i should replace my cable. so i did and since then its been working fine until yesterday when suddenly disk 2 started showing read errors again and it got disabled. after which i follishly ended up rebooting my server without even first collecting diagnostic data. so i just reseated cables and reenabled my disk 2 after it was working fine until now.

    now again its showing disk read errors and it got disabled.

    so here diagnostic data after my disk 2 got disabled again. PLEASE HELP !!!!

    Edit : forgot to mention that currently its not showing any smartdata but im pretty it will come back just like last time it did after reboot.

    unraid-diagnostics-20201219-0158.zip

  12. 12 minutes ago, b3rs3rk said:

    Okay, I’m on it now. Try starting your VM and then pasting me the result of:

     

     

    
    nvidia-smi -L
     

     

     

    Then shutdown the VM and run that command again and paste me this second result.

     

    My guess is when you pass the GPU through nvidia-smi can no longer see it. Then GPUID 1 becomes zero.

    yup you are right, this is with vm is running.

    root@Unraid:~# nvidia-smi -L
    GPU 0: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad)

    no gtx 1070ti.

    root@Unraid:~# nvidia-smi -L
    GPU 0: GeForce GTX 1070 Ti (UUID: GPU-b3281921-cd4e-952e-a85c-853c365a663b)
    GPU 1: GeForce GTX 750 (UUID: GPU-4daa28f9-2851-49be-7240-d485e0fa6aad)

    and this here when vm is shut nvidia-smi can see both my gou again.

    i see, so this why gpu stats goes blank when i select gpu 1 and start my vm cause now there is no gpu 1 .😅

  13. 5 hours ago, b3rs3rk said:

    I'm happy to help as this seems like a bug, but I'm afraid I don't understand your post.

    yeah i had felling that it was getting a little confusing.

    okay i try my best to explain it.

    you see here i have to nvidia GPU's, 0 is gtx 1070 ti which im using for my vm and 1 is gtx 750 for plex hardware transcoding. (i only want to see the stats for gpu 1 i.e. gtx 750)

    https://imgur.com/a/mGddMgH

    Now if i select gpu 1 i.e. gtx 750 from the dropdown list of unit ID for dashboard option it will keep posting stats until vm starts, the moment i start the vm all info on dashboard page will go blank and it will only resume posting when i shutdown my vm.

    Now if i click on this default button (while vm is still running) on gpu stats's page it will shows stats for gpu 1 i.e. gtx 750 but now when i shutdown my vm it will switch back to gpu 0 i.e. gtx 1070 ti cause under unit id for option it has switched back to gpu 0 cause we selected default option earlier, so cause 0 should be default it is now set gpu 0 i.e.e gtx 1070 ti. 

    https://imgur.com/a/YzY4YmW

    so as long as its set to gpu 0 it will keep posting stats, now ofcourse it wil switch between gpu's whenever vm starts or stops but now atleast its always posting gpu stats.

    So basically its like this if its set it to gpu 0 it will always show gpu stats, it won't go blank but if i set it to gpu 1 it wont shows stats when the vm's are running.

    • Like 1
  14. 22 minutes ago, Max said:

    i was experiencing empty stats issue and this fixed it for me. even though it was detecting both my gpu's but as soon as i started  my vm it used to stop posting stats for my second gpu which is being used by plex. luckily this fixed it for me.

    looks like i spoke too soon it looks like everytime i run my vm it stop posting gpu stats and it only working once i click on default. but then when vm is shutdown it switch to gpu 0 which was being used by vm cause i clicked on default.

    so it looks like it will keep posting if i dont maually select gpu 1, here it will keep posting and switch to gpu 1 whenever i run my vm and then switch back to gpu 0 when vm is no longer running but i mainly wanna see stats for gpu 1 as this the gpu that is being used by plex and gpu 0 is for my vm's but this way i wont be able to see stats for gpu1 when vms are not running i will only be able to see stats for it when vm are running and if i do maually select gpu 1 in gpu stats plugin settings then it will stop posting as soons vm start to run and then start posting once again when vm is shutdown.

    a really weird glitch i guess if am not the only one with this issue.

  15. On 3/15/2020 at 3:56 PM, SuberSeb said:

    I fixed that. For some reason plugin don't detect my GPU. I just pressed "Default" button and all works.

    i was experiencing empty stats issue and this fixed it for me. even though it was detecting both my gpu's but as soon as i started  my vm it used to stop posting stats for my second gpu which is being used by plex. luckily this fixed it for me.

×
×
  • Create New...