iarp

Members
  • Posts

    103
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

iarp's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. This connection is direct using putty from windows. Aug 4 13:03:16 storage sshd[6898]: Close session: user root from 192.168.2.20 port 58866 id 0 Aug 4 13:03:16 storage sshd[6898]: Connection closed by 192.168.2.20 port 58866 Aug 4 13:03:16 storage sshd[6898]: pam_unix(sshd:session): session closed for user root Aug 4 13:03:16 storage sshd[6898]: Transferred: sent 2800, received 2416 bytes Aug 4 13:03:16 storage sshd[6898]: Closing connection to 192.168.2.20 port 58866
  2. I only leave terminals in root's home directory /root (via a plain cd command), it's a habit after running into lock issues many years ago. This issue just requires logging into the server and stopping the array, the connection will be immediately disconnected.
  3. Every time I stop the array, the ssh process is killed. I always use screen to keep sessions going but whatever is happening in the background its killing them. If this was added to unraid, what version was it first added? Is it possible to stop this from occurring in the most recent?
  4. I reconnected the drive to the system and ran memtest which found no errors. Upon restarting into unraid the cache drive is randomly back. Should I trust this is ok? Edit: I didn't trust it and attempted to rm the appdata folder because i had already restored that using a backup directly to the array and i didn't want things to get mixed. I'm hit with the following message on hundreds of files rm: cannot remove 'appdata/jellyfin/dlna/system/Sony Bravia (2014).xml': Read-only file system rm: cannot remove 'appdata/jellyfin/dlna/system/Sony PlayStation 3.xml': Read-only file system rm: cannot remove 'appdata/jellyfin/dlna/system/Sony PlayStation 4.xml': Read-only file system rm: cannot remove 'appdata/jellyfin/dlna/system/WDTV Live.xml': Read-only file system rm: cannot remove 'appdata/jellyfin/dlna/system/Xbox One.xml': Read-only file system rm: cannot remove 'appdata/jellyfin/dlna/user': Read-only file system But other files on the system can be deleted without issue. Edit 2: I'm now hunting for a way to somehow verify every bit of an ssd to see if it catches some kind of error? I'm not sure if thats possible.
  5. The 3rd command listed under the read-only section "ro,notreelog,nologreplay" worked and I'm copying as we speak. It's unclear to me if this is a failing drive or something else happened and i'm safe to just reformat and put it back into service. I grabbed diagnostics before shutting it down the first time, according to my emailed errors this happened at exactly 9AM my time.
  6. [ 33.024701] sd 16:0:0:0: [sde] 488397168 512-byte logical blocks: (250 GB/233 GiB) [ 33.025587] sd 16:0:0:0: [sde] Write Protect is off [ 33.025590] sd 16:0:0:0: [sde] Mode Sense: 00 38 00 00 [ 33.026552] sd 16:0:0:0: [sde] Asking for cache data failed [ 33.026561] sd 16:0:0:0: [sde] Assuming drive cache: write through [ 33.051175] sde: sde1 [ 33.054211] sd 16:0:0:0: [sde] Attached SCSI disk [ 33.186906] BTRFS: device fsid 3346e7ab-0a8a-4c11-bb04-9ccbcdc4e414 devid 1 transid 14150489 /dev/sde1 [ 33.256468] BTRFS info (device sde1): using free space tree [ 33.256471] BTRFS info (device sde1): has skinny extents [ 33.350488] BTRFS info (device sde1): start tree-log replay [ 33.402424] BTRFS info (device sde1): leaf 5668864 gen 14150490 total ptrs 179 free space 2321 owner 2 [ 33.402799] BTRFS error (device sde1): unable to find ref byte nr 51566100480 parent 0 root 5 owner 12453882 offset 2129920 [ 33.403016] BTRFS: error (device sde1) in __btrfs_free_extent:3077: errno=-2 No such entry [ 33.403018] BTRFS: error (device sde1) in btrfs_run_delayed_refs:2188: errno=-2 No such entry [ 33.403022] BTRFS: error (device sde1) in btrfs_replay_log:2281: errno=-2 No such entry (Failed to recover log tree) [ 33.485774] BTRFS error (device sde1): open_ctree failed [ 52.162186] BTRFS info (device sde1): using free space tree [ 52.162191] BTRFS info (device sde1): has skinny extents [ 52.260330] BTRFS info (device sde1): start tree-log replay [ 52.310696] BTRFS info (device sde1): leaf 5668864 gen 14150490 total ptrs 179 free space 2321 owner 2 [ 52.311070] BTRFS error (device sde1): unable to find ref byte nr 51566100480 parent 0 root 5 owner 12453882 offset 2129920 [ 52.311321] BTRFS: error (device sde1) in __btrfs_free_extent:3077: errno=-2 No such entry [ 52.311323] BTRFS: error (device sde1) in btrfs_run_delayed_refs:2188: errno=-2 No such entry [ 52.311328] BTRFS: error (device sde1) in btrfs_replay_log:2281: errno=-2 No such entry (Failed to recover log tree) [ 52.401769] BTRFS error (device sde1): open_ctree failed [ 74.423093] BTRFS info (device sde1): using free space tree [ 74.423095] BTRFS info (device sde1): has skinny extents [ 74.520379] BTRFS info (device sde1): start tree-log replay [ 74.570325] BTRFS info (device sde1): leaf 5668864 gen 14150490 total ptrs 179 free space 2321 owner 2 [ 74.570705] BTRFS error (device sde1): unable to find ref byte nr 51566100480 parent 0 root 5 owner 12453882 offset 2129920 [ 74.570924] BTRFS: error (device sde1) in __btrfs_free_extent:3077: errno=-2 No such entry [ 74.570926] BTRFS: error (device sde1) in btrfs_run_delayed_refs:2188: errno=-2 No such entry [ 74.570932] BTRFS: error (device sde1) in btrfs_replay_log:2281: errno=-2 No such entry (Failed to recover log tree) [ 74.655031] BTRFS error (device sde1): open_ctree failed I've taken it out of the unraid box and its connected to my main linux machine to see if i could do anything here but all i get is "Error mounting /dev/sde1 at /media...: mount(2): system call failed: No such file or directory" How to proceed? Is there anything that can be done? While googling some things I saw another unraid post mention running the command "btrfs fi show /dev/sde1" which outputs the following, it still shows used space. Label: none uuid: 3346e7ab-0a8a-4c11-bb04-9ccbcdc4e414 Total devices 1 FS bytes used 87.25GiB devid 1 size 232.89GiB used 126.02GiB path /dev/sde1
  7. Only the number 7 is in the age box. Sent from my Nexus 7 using Tapatalk
  8. I'm the only user. The only activity in this share is at 11am from my computer backing up and 7am/7pm sql backups. I executed the find atime command and all of the "Copy #..." files are returned. But they are never deleted. As of now the webpage still shows 66G and its been 9 hours. If i redo a du -sh on the backup recycle bin its at 94G.
  9. I'm not sure when this started happening but the plugin is failing to do two things. 1) display the correct Trash Size for each user share and 2) delete old files. I'm not even sure where to begin with the Trash Sizing issue because the webpage currently shows 66G for Trash Size on the backup share however: root@storage:/mnt/user/backup/.Recycle.Bin# du -sh ./* 94G ./MYCOMP 9.9M ./SQL root@storage:/mnt/RecycleBin/User Shares/backup# du -sh ./* 94G ./MYCOMP 9.9M ./SQL Additionally, it's not deleting old files. It's currently set for 7 days and over the smb share i can see files dated 2021-04-08 root@storage:/mnt/user/backup/.Recycle.Bin/MYCOMP/Backup Job MYCOMP_1# stat Copy\ #1\ of\ Backup\ Job\ MYCOMP.vbm File: Copy #1 of Backup Job MYCOMP.vbm Size: 295051 Blocks: 584 IO Block: 4096 regular file Device: 2fh/47d Inode: 648799823889937712 Links: 1 Access: (0666/-rw-rw-rw-) Uid: ( 99/ nobody) Gid: ( 100/ users) Access: 2021-04-08 11:02:01.997199995 -0400 Modify: 2021-04-08 11:00:34.032458553 -0400 Change: 2021-04-15 08:30:47.766812889 -0400 Birth: - Version 2021.04.24
  10. My monthly parity check happened last night with 5 errors. My current scheduled setting is the monthly does not correct. If I run the check with corrections enabled and it finds those 5 again relatively quickly, are they fixed immediately or is the repair delayed until the end? I'm thinking now that a full check has happened, once it finds and corrects those 5 again i'll just stop it manually.
  11. I'm looking for some clarification on the Disk Verification Schedule and the Tasks. So the help says So in this example you have 3 disks and you have put each disk on a separate task. My understanding of the above is that Task 1 executes on the Monday, then the following Monday Task 2, and the following Monday after that Task 3. But then when does it restart? The next Monday after the week with Task 3 finishing its back to Task 1? If I select Monthly, is that going to run Task 1 in Jan, Task 2 in Feb, Task 3 in March? Is there anyway to set it up so it checks all disks once a month but separate the tasks by a day or a week? Also on the Integrity page in the help it states "0 represents an open operation", does that mean a running operation? Like it's actively doing something in the background?
  12. I've run extended on all 3 disks. I see some errors but they seem to have happened quite a few powered-on-hours ago. ST2000DM001-1CH164_S240QKH5-20210128-0750.txt ST2000DM001-1CH164_W1E22PJR-20210128-0749.txt ST2000DM001-1CH164_W1E26DX7-20210128-0750.txt
  13. What are your share settings? As far as I know, if the share has cache set to anything other than No it'll be included in the size.
  14. Just upgraded this machine from v5-rc15 to 6.8.3 and practically immediately I've got a warning about disk3 with SMART "reported uncorrect is 6". Is this something to be worried about at this time? backup-diagnostics-20210127-1952.zip
  15. Essentially I have a 60GB vdisk with only 15GB in use. If I attempt to copy it in any way it copies 60GB fully, not 15GB. # qemu-img info vdisk1.img image: vdisk1.img file format: raw virtual size: 60 GiB (64424509440 bytes) disk size: 14.9 GiB