Jump to content

jsebright

Members
  • Posts

    68
  • Joined

  • Last visited

Posts posted by jsebright

  1. This problem occurred again, then I think I worked out what was going on. The device was "disappearing" when I started a VM, but only a certain one. I had had to fiddle with it a day or so ago as it wouldn't start. Something must have got messed up meaning the VM was trying to take control of the nvme drive.

    I could spot the device in the xml, but am not confident enough to edit it. Just saving the VM settings from the forms view didn't clear the device, but selecting all the possible usb devices and the one pcie device, saving, then clearing them all and saving seems to have sorted it out.

    Thanks for the support - I know a bit more about checking disks now.

     

    • Like 1
  2. 18 minutes ago, itimpi said:

     

     

    You have used the wrong device name in the xfs_repair command.  If using raw device names you need to include the partition number (e.g. /dev/sdh1).  You can only omit the partition number if using the /dev/mdX type device names.   Also note that raw device names will invalidate parity whereas the /dev/mdX type names do not.

     

    Earlier you were talking about a BTRFS format drive while now it is an XFS one you seem to be trying to fix - just checking this is intentional.

     

     

    Ah, thanks. Just cancelled it and rebooted. This is an unassigned drive - not part of the array.  So it looks like /dev/sdh1 is OK for this.

     

    The BTRFS cache issue was the primary error (and still probably is). It's just that @JorgeB spotted another issue to do with this other drive that needs fixing. One problem turns into two...

     

  3. Hi @JorgeB Many thanks for your support on this - really appreciate it.

     

    Have now rebooted (switched off auto start of dockers & vms before doing this). scrubbed the disk again to fix the errors. Will double check the error count and zero them.

     

    Trying to fix the UD URBACKUP disk I get the following: 

    root@Tower:~# xfs_repair /dev/sdh
    Phase 1 - find and verify superblock...
    bad primary superblock - bad magic number !!!
    
    attempting to find secondary superblock...
    .found candidate secondary superblock...
    unable to verify superblock, continuing...
    .found candidate secondary superblock...
    unable to verify superblock, continuing...
    ................................................

    The dots then continue to fill up the window - not sure how long it will take but I'll just leave it running.

    When that's done I can reboot again and will take some diagnostics hoping that it's clean.

     

    It's still unclear why the nvme drive is dropping off. I can try re-seating them but they've been good for quite a few months at least.

  4. 18 hours ago, JorgeB said:

    You can also take a look here since it might take me longer to reply due to weekend:

     

    https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582

     

     

    Checking btrfs dev stats showed lots of errors. 

     

    I ran scrub firstly without the "Repair corrupted blocks" option and it showed the following (whih I first thought was no errors, but presumably is).

     

    UUID:             e8b8d9ec-0ad2-4867-b3cf-87b43a0d9d15
    Scrub started:    Sun Apr 25 07:16:27 2021
    Status:           finished
    Duration:         0:03:07
    Total to scrub:   1.10TiB
    Rate:             6.02GiB/s
    Error summary:    verify=1438 csum=167501
      Corrected:      0
      Uncorrectable:  0
      Unverified:     0

    I then ran it with the "Repair corrupted blocks" option anyway, and it corrected loads of errors. (Seems a bit odd that the first "scrub" didn't highlight that there was something that needed correcting. Then I looked at the line "Error summary:    verify=1438 csum=167501" from the first run).

     

    Finished, but odd that the "verify" number is a bit short of the first scrub run, and the corrected doesn't match the csum (but I don't know if it should).

    UUID:             e8b8d9ec-0ad2-4867-b3cf-87b43a0d9d15
    Scrub started:    Sun Apr 25 07:28:00 2021
    Status:           finished
    Duration:         0:03:07
    Total to scrub:   1.10TiB
    Rate:             6.02GiB/s
    Error summary:    verify=1347 csum=167501
      Corrected:      168848
      Uncorrectable:  0
      Unverified:     0

     

    ran another scrub just to be sure, and this time there's clearly no errors.

    UUID:             e8b8d9ec-0ad2-4867-b3cf-87b43a0d9d15
    Scrub started:    Sun Apr 25 07:39:58 2021
    Status:           finished
    Duration:         0:03:03
    Total to scrub:   1.10TiB
    Rate:             6.15GiB/s
    Error summary:    no errors found

    Set up the script from the FAQ on the main pool and the cache pool so I will get notified of errors.

    Then started some dockers - OK, started some VMS and then I had the error again - repeating every minute, just in case I missed it the first time:

    image.png.5c7d7b15f74d8f8e189adb438f755ac4.png

     

    Not sure what do do now. Can't check cables as there are none - the nvme's are in the motherboard.

    Time to take some extra backups (assuming it's not too late!)

     

  5. Please post after reboot diags to see current pool status.
     
    P.S. you need to run xfs_repair on URBACKUP UD device.
    Thanks, have seen recent errors on that. Thought it was due to backups from locations with intermittent connectivity.
    Pool status looked ok, but will get some diagnostics. It's currently doing a parity check due to an unrelated unplanned reboot.


    Sent from my ONEPLUS A5000 using Tapatalk

  6. Suddenly had the message "Cache pool BTRFS missing device"

    The pool which I use for VMs and Docker, running from 2 nvme drives had a problem that a drive suddenly went missing.

    I closed the VMs, took a diagnostics, and rebooted.

    On reboot, the pool appears fine and the VMs & dockers are running, but I don't know what to do to check the health of the cache pool - will BTRFS have fixed any differences automatically, is there something I should do to force checks, is there something I must avoid doing after this issue?

    Diagnostics attached (there might be a mess of other issues in there as I have a tendency to fiddle...)

    tower-diagnostics-20210424-0857.zip

  7. 9 hours ago, jonp said:

    There are additional things that our creator does that a simple IMG file does not. 

    Don't know if things have changed, but when I first started out with Unraid - or when I did some additional playing around - I found that the tool didn't set the keyboard, which caused me issues when using the GUI mode (a temporary thing). Some of us get used to the " and @ keys being in certain places... Still not sure that was ever resolved.

    Totally get that Unraid is a GUI, and should start off as such with the installer. The options setting in the imager are important in helping new (and old) users avoid the command line, in the same way the browser interface sorts out (nearly?) all the configuration.

    I also understand that there are very good imaging tools available, so providing a default image for users that want it and understand that it doesn't do the nice things an installer does will satisfy users that prefer their own imager.

  8. 4 minutes ago, binhex said:

    i store my backups on my array and i havent really seen any issues with this, so unless there is a particular reason to move it then i would keep it on the array, i dont think i would be too concerned with not being able to calculate a share size.

    Thanks for your reply. I think I'll leave it as is, though I might see if I can restrict it to a single disk and move other shares to other drives. Although perhaps I'm trying to be too neat with it. Beats the pain of trying to copy the files to another disk (which seemed problematic when I tried it briefly).

  9. I really like what it's doing, having de-duped backups of a number of systems is great. Thanks @binhex for building and maintaining this docker.

    Now, a few questions...

    I am noticing that when a backup is running  (full image backup in this case) that urbackup maxes out one cpu core. It alternates every minute or so which one it is, but it 's unusual in doing this.

    image.png.1bd56404eae7e0f59f137044dd246abd.png

     

    Also, I initially allocated a single disk for backups, outside of the array. Then I thought I might run out of space, so set it to be inside the array instead (avoiding cache). Due to the number of links (I believe) if I run "Compute All" on the shares then the size of the urbackup share can't be calculated. Would I be better off putting this back onto a dedicated disk instead, and is there a good way to move the backups or do I have to start over again?

  10. 23 hours ago, bonienl said:

    Unraid supports 802.3ad aka dynamic link aggregation.

    That's the issue, my switches only support Static Link aggregation. Thanks Netgear.

    I'm connecting 2 ports from my Unraid box to a Netgear GS116Ev2  where the ports can be set for Static LAG. That connects via 2 ports to a Netgear GS908E with LAG set up at both ends. Then into my windows box which I can configure for static LAG.

    I've been trying to improve the speed (just for the sake of it) without spending too much. Looks like the best way might be to put a card in each machine and use a direct cable run (avoiding the switches), but I've got to use the existing cables as putting in a run of fibre is not feasible. There are some 2.5G cards that have recently come on the market (Amazon didn't have any recently, but they now do) - I might get a pair of those to try.

     

    Thanks for replying.

     

     

  11. On 1/13/2020 at 1:34 PM, AlexBGames said:

    Did you use the latest drivers?

    Sorry, can't remember. Assuming you mean Windows drivers in the guest VM, then I would have updated to the latest ones ASAP. I keep changing things around to suit other family members, and am moving at least one (what will be a heavily used gaming based machine) back to physical. Keep the virtual for remote desktopping into and an occasional, low use KVM machine.

  12. The test preclear was a success, but at the top of the Log file there is a line (just under Preclear Disk Version: 1.0.6) that says:

    Disk /dev/sdd is a SSD, disabling head stress test.

    The disk is not an SSD, but is connected to a cheap PCIE SATA board. I think it's this:

    [1095:3132] 06:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01)

     

    I'm going to assume the SSD identification won't cause any problems and start another PreClear run.

     

    @gfjardim - Thanks for the updates and the excellent support.

     

     

  13. I've just had a similar error to Simon above. A new "shucked" WD 6tb drive.

    Unassigned devices shows:

    image.png.60448e4a63afb8648127f0e368e7de25.png

    Near the end of the preclear log I see these lines:

    Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: sd 3:0:0:0: [sdc] Attached SCSI disk
    Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: WDC_WD60EDAZ-11U78B0_WD-WX21D690LD9T (sdc) 512 11721045168
    Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: excluded disks=sda sda2 sdb sdc sdf
    Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 1 --frequency 4 --cycles 1 --no-prompt /dev/sdc
    Nov 24 14:25:56 preclear_disk_WD-WX21D690LD9T_12518: syslog: Disk /dev/sdc is a SSD, disabling head stress test.

    Note that the disk is not an SSD.

    Only thing I can think of is that during the zeroing run I added a USB drive to the server (an old drive in the donor USB case). That seemed to pause the zeroing whilst it formatted, but is working as a UD attached disk.

    Preclear logs attached.

     

    What do I do now. I was going to use it as a replacement parity disk, but wanted to give it a try out. Is it unreasonable to just go ahead and swap it with the existing parity?

     

    Thanks,

    Jon.

     

    TOWER-preclear.disk-20191124-1934.zip

    • Like 1
  14. I'm not currently running PiHole, but I am running an adblocker on my router. Have just tried switching that off along with suspending adblock and ublock in the browser, but it makes no difference. Have tried a few browsers - the only one to show anything is Edge (and IE) on Windows which show "Undefined" so something is happening at the client end. If you look at "System Stats" you will see network activity (as long as you're not in a VM on the Unraid server!), so it's likely it's just the display widgets which are broken client side.

  15. Agree. I'm fairly new to unraid and remote access is great, but I'm just evaluating whether I want to run it and use it as a desktop machine hosting several VMs, and I'm stuck because I can't set the keyboard.

    It would be great if it was just a setting to change the layout of the connected keyboard, but also would be helpful if it was part of the usb installer to set it right from the beginning.

     

    [I've installed nerdpack, kbd, and typed "loadkeys uk " but it doesn't appear to change anything]

×
×
  • Create New...