John_M

Members
  • Posts

    4727
  • Joined

  • Last visited

  • Days Won

    12

Report Comments posted by John_M

  1. On 6/6/2022 at 10:22 PM, thecode said:

    I would appreciate if someone confirm my findings

     

    It worked for me, but using Firefox on a Mac! You don't press F12 but Option-Command-I to open the Developer Tools window. From that point select the Storage tab and Cookies and delete the 'rdx-init' cookie.

     

  2. I looked for documentation about the about the scrub and balance schedulers that were recently introduced for btrfs volumes. What kind of scrub is done on a schedule? Is it a correcting one or a read-only one, given that there's a choice when a scrub is run manually? What kind of balance is done on a schedule? Is it a full one or one based on partially filled extents? Does the presence of the Block group usage parameter imply that it's the latter?

     

    1170632483_ScreenShot2022-05-11at19_03_13.png.bb919ce915751bddf6389b2cb28fbfd1.png

  3. On 4/25/2022 at 8:52 PM, eagle470 said:

    I have a few bugs to report for RC4:

     

    It looks like you have a problem with your "dockers" pool (corrupt 515432):

     

    Apr 25 11:52:19 Unraid1 kernel: BTRFS info (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 515432, gen 4

     

  4. 3 hours ago, Greggers said:

    its a saved username/password that I know was working previously..

     

    Can you enter the username (it can only be 'root') and password manually? Browsers store username/password combinations against the URL of the page. If you're using https the URL has changed from https://<hash>.unraid.net to https://<local ip address with dashes>.<hash>.myunraid.net with this update.

  5. On 11/14/2021 at 2:37 PM, nikos134 said:

    I am passing through my GPU 5700XT

     

    Nov 14 16:23:38 NIKOS-TOWER kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device.

     

    According to the syslog snippet you posted you are loading the amdgpu driver which will prevent the card being passed through to a VM. Either stop loading the amdgpu driver or, if you need it for another AMD GPU, bind your 5700XT card to the VirtIO driver on the Tools -> System Devices page.

     

    As mentioned in the release notes, at the top of this page,

     

    Quote

    In-tree GPU drivers are now loaded by default if corresponding hardware is detected:

    • amdgpu
    • ...

     

    which would explain the different behaviour.

    • Like 1
  6. My upgrade from 6.9.2 to 6.10.0-rc2 was uneventful, thank you.

     

    Quote

    Dashboard graphs

    • The dashboard has now two graphs available. The CPU graph is displayed by default, while the NETWORK graph is a new option under Interface (see the 'General Info' selection)

     

    Shouldn't that say 'Network traffic' instead of 'General Info'?

     

    1467705690_ScreenShot2021-11-10at19_48_42.png.79467052d1e4a9e20827bf366a50dc13.png

  7. 8 hours ago, danioj said:

    Last few hours of my logs:

     

    Sep 2 18:56:40 unraid kernel: mdcmd (55): set md_write_method 1

     

     

    It looks like you have the Turbo-write plugin installed. I believe it's responding to the spin-ups and spin-downs, rather than causing them, but it might be worth disabling it temporarily just in case.

     

  8. 7 minutes ago, Pawel said:

    No Rock Ridge... so how ubuntu does it and shows filles with long names?

     

    Standards are so good that everyone wants their own, so that's what Microsoft did:

     

    7 minutes ago, Pawel said:

    Joliet with UCS level 3 found

     

    See here: https://tldp.org/HOWTO/CDROM-HOWTO/x1186.html#AEN1328

     

    Perhaps Joliet support is not included in the Unraid kernel but it is in the Ubuntu kernel. That would make sense because Unraid is not a general purpose Linux and has a lot of unnecessary options removed. If that's the case then your options would be:

    • re-create your .iso with Rock Ridge enabled;
    • use a different image file format that supports long filenames and mixed case natively;
    • use an Ubuntu VM to mount the .iso file;
    • make a feature request for Joliet support to be included in a future release;
    • investigate the possibility of compiling your own kernel with Joliet support included.

     

    • Thanks 1
  9. From the mount(8) man page:

     

    Quote

    Normal iso9660 filenames appear in a 8.3 format (i.e., DOS-like restrictions on filename length), and in addition all characters are in upper case. Also there is no field for file ownership, protection, number of links, provision for block/character devices, etc.

     

    Rock Ridge is an extension to iso9660 that provides all of these unix like features. Basically there are extensions to each directory record that supply all of the additional information, and when Rock Ridge is in use, the filesystem is indistinguishable from a normal UNIX filesystem (except that it is read-only, of course).

     

    What is the origin of your .iso file? Is it Rock Ridge compatible? Using a standard Kubuntu installation image, it works fine for me:

     

    root@Pusok:~# mkdir t
    root@Pusok:~# mount -t iso9660 /mnt/user/isos/kubuntu-20.10-desktop-amd64.iso t
    mount: /root/t: WARNING: source write-protected, mounted read-only.
    root@Pusok:~# ls t
    EFI/                boot/         casper/  install/    pics/  preseed/
    README.diskdefines  boot.catalog  dists/   md5sum.txt  pool/  ubuntu@
    root@Pusok:~# ls t/casper
    filesystem.manifest                 filesystem.size          initrd
    filesystem.manifest-minimal-remove  filesystem.squashfs      vmlinuz
    filesystem.manifest-remove          filesystem.squashfs.gpg
    root@Pusok:~# umount t
    root@Pusok:~# rmdir t

     

    I suggest you try the same (or similar) standard file.

     

    • Thanks 1
  10. Why are you loading the Intel integrated graphics driver?

    # Load the i915 driver
    modprobe i915

     

    This should really be posted in the General Support section. It isn't an Unraid bug and it isn't Urgent.

     

    Have you done a memory test? Have you tried enabling syslog mirroring to flash to see if it catches the problem?

  11. I have this too on a server with parity and three data disks connected to the four motherboard SATA ports. With the array started the access light flashes at approximately 1 Hz, whether the disks are spinning or not. With the array stopped it flashes occasionally, without an obvious pattern. The next thing to try would be safe mode.