Jump to content

Tyranian

Members
 View Profile  See their activity

  • Posts

    28

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by Tyranian

    [Support] binhex - Sonarr

    in Docker Containers

    Posted

    Couldnt see if this has already been stated but after updating to the new Unraid RC (6.10 RC5) from stable I have got permission errors on several Binhex containers here is the error for Sonarr  

     

    System.Data.SQLite.SQLiteException (0x80004005): attempt to write a read-only database

     

    updating the permissions or reinstalling the App fresh and restore of backup works (i went with the restore as wasnt sure what other files may have permission issues)

    BTFRS Disk issue - Disk 1 Read only

    in General Support

    Posted

    I have a disk that will only mount RO and has the following issue when BTRFS checked I have tried Scrubbing but errors remain what are my next options?

     

    Disk 1 has the following errors when doing a BTFRS check

     

    [1/7] checking root items

    [2/7] checking extents

    parent transid verify failed on 1591866720256 wanted 3177 found 3193

    parent transid verify failed on 1591866720256 wanted 3177 found 3193

    Ignoring transid failure

    parent transid verify failed on 2617519161344 wanted 1827879 found 1827895

    parent transid verify failed on 2617519161344 wanted 1827879 found 1827895

    Ignoring transid failure

    parent transid verify failed on 2736103292928 wanted 1828130 found 1828146

    parent transid verify failed on 2736103292928 wanted 1828130 found 1828146

    Ignoring transid failure

    backref bytes do not match extent backref, bytenr=4500955992064, ref bytes=679936, backref bytes=684032

    backpointer mismatch on [4500955992064 679936]

    backref bytes do not match extent backref, bytenr=5663998078976, ref bytes=557056, backref bytes=561152

    backpointer mismatch on [5663998078976 557056]

    backref bytes do not match extent backref, bytenr=5663998640128, ref bytes=565248, backref bytes=569344

    backpointer mismatch on [5663998640128 565248]

    backref bytes do not match extent backref, bytenr=7142533070848, ref bytes=745472, backref bytes=749568

    backpointer mismatch on [7142533070848 745472] backref bytes do not match extent

    backref, bytenr=7939927638016, ref bytes=630784, backref bytes=634880

    backpointer mismatch on [7939927638016 630784] backref bytes do not match extent

    backref, bytenr=11081639366656, ref bytes=753664, backref bytes=757760

    backpointer mismatch on [11081639366656 753664] ERROR: errors found in extent allocation tree or chunk allocation

    [3/7] checking free space cache

    there is no free space entry for 4500956672000-4500956676096

    there is no free space entry for 4500956672000-4501146697728

    cache appears valid but isn't 4500072955904

    there is no free space entry for 5663998636032-5663998640128

    there is no free space entry for 5663998636032-5664009093120

    cache appears valid but isn't 5662935351296

    there is no free space entry for 7142533816320-7142533820416

    there is no free space entry for 7142533816320-7142551584768

    cache appears valid but isn't 7141477842944

    there is no free space entry for 7939928268800-7939928272896

    there is no free space entry for 7939928268800-7940341760000

    cache appears valid but isn't 7939268018176

    there is no free space entry for 11081640120320-11081640124416

    there is no free space entry for 11081640120320-11082110337024

    cache appears valid but isn't 11081036595200

    [4/7] checking fs roots

    parent transid verify failed on 1591866720256 wanted 3177 found 3193

    Ignoring transid failure

    parent transid verify failed on 2617519161344 wanted 1827879 found 1827895

    Ignoring transid failure

    parent transid verify failed on 2736103292928 wanted 1828130 found 1828146

    Ignoring transid failure

    [5/7] checking only csums items (without verifying data)

    parent transid verify failed on 1591866720256 wanted 3177 found 3193

    Ignoring transid failure

    there are no extents for csum range 4500956672000-4500956676096

    csum exists for 4500676567040-4500973539328 but there is no extent record

    there are no extents for csum range 5663999205376-5663999209472

    Right section didn't have a record

    there are no extents for csum range 5663998636032-5664008814592

    csum exists for 5663968206848-5664008814592 but there is no extent record

    there are no extents for csum range 7142533816320-7142533820416

    csum exists for 7141477842944-7142551478272 but there is no extent record

    there are no extents for csum range 7939928268800-7939928272896

    csum exists for 7939804889088-7939934044160 but there is no extent record

    parent transid verify failed on 2617519161344 wanted 1827879 found 1827895

    Ignoring transid failure

    parent transid verify failed on 2736103292928 wanted 1828130 found 1828146

    Ignoring transid failure

    there are no extents for csum range 11081640120320-11081640124416

    csum exists for 11081633353728-11081987842048 but there is no extent record

    ERROR: errors found in csum tree

    [6/7] checking root refs

    [7/7] checking quota groups skipped (not enabled on this FS)

    ERROR: transid errors in file system

    Opening filesystem to check...

    Checking filesystem on /dev/md1

    UUID: 1e50bdfa-ef2a-486c-a920-873abd0d967b

    found 5604656373760 bytes used, error(s) found

    total csum bytes: 5465849760

    total tree bytes: 6225084416

    total fs tree bytes: 361398272

    total extent tree bytes: 88276992

    btree space waste bytes: 300423581

    file data blocks allocated: 5605679144960

    referenced 5598424096768

     

    Thanks

    Anybody planning a Ryzen build?

    in Motherboards and CPUs

    Posted

    Then if it helps I'm stable in general other then the VM at the moment which has just started crashing after a day or so of usage now I've finished setting it up, I have C-state enabled and my suffers no other types of crashes then the VM one.

     

    I'm using Ryzen 1600 & Gigabyte Gaming 5 Mobo with F8 bios.

     

    There is now a AGESA 1.0.0.6b bios so may try that next.

    Anybody planning a Ryzen build?

    in Motherboards and CPUs

    Posted · Edited by Tyranian

    On 9/13/2017 at 0:19 PM, luisv said:

    I still need to have C-State disabled, but have been stable for the last 15 days, 11 hours, 8 mins.   Asus released another BIOS update for my motherboard and I'm looking to add another HD to my system.  Once I purchase the drive, hopefully before the weekend, the plan is to shut the system down, add the HD, update the BIOS, enable C-State and check to see if the system is stable with C-State enabled.  If not, I'll upgrade to rc8q and again, see if it's stable with C-State enabled, otherwise, I'll just leave C-State disabled until the next round of BIOS / unRAID updates are released.  

     

    When not using C state what error do you see? does the VM crash and then you cannot restart the VM due to a PCI error until rebooting unraid? if so that may be the issue I have just started to see on my VM when leaving on overnight.. Im already on rc8q and latest bios for my Aorus Gaming5.

×
×
  • Create New...