Jump to content

whwunraid

Members
  • Content Count

    39
  • Joined

  • Last visited

Community Reputation

2 Neutral

About whwunraid

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    KC Mo

Recent Profile Visitors

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

  1. Even after taking that into account and making the change, unraid clock still lost 2 hours overnight. Will verify the BIOS clock again with a reboot and set the unraid clock 1 more time. I've seen a few of these issues on the board and never a resolution.
  2. I have a 2 fold issue that I thought was issue 1 causing issue 2... My clock in Unraid will not stay sync'd with the current time, I have tried setting it manually and using available NTP servers, nothing works. I did have to replace the mainboard battery and the clock in the BIOS is current as of my last reboot. My 2nd issue is that I cannot update successfully from 6.6.7 to 6.7.2 When I did the first time the system ran for 12 hours and then locked up. I had to do a hard shutdown and when it cam back up it lasted 30 mins and locked up again. Nothing works not even from the console on the server. I restated a 3rd time, in SAFE mode, and still same issue, locks up after 30 mins. I rolled back to 6.6.7 and the server runs fine, other than the time issue. I am attaching Diagnostics from 667, have not tried to pull them on 672. I see the time error listed in the logs but not much else, hoping a 2nd pair of eyes may catch something. Thanks... unraid1-diagnostics-20191212-0318.zip
  3. I am working with Emby Support on an issue with the Docker app, so I assumed the path they asked me to look into should be relative to the docker (makes sense after the above clarification). Thanks Guys...
  4. Can someone point me to a resource that shows the directory structure for the server and what is where. Try'd using Krusader but it just make things more confusing. Would appreciate any help/"roadmap"... thanks.
  5. I have a similar issue, 8TB USB 3.0 drive. It shows in Unassigned Devices as sdb and spun down, clicking Spin Up does nothing. It is currently formatted as NTFS; been trying differing backup strategies. So at this point I can do nothing with it. I have no options for Unassigned Devices in the Settings or Tools Menu as mentioned above. v6.5.2 Thanks for any ideas...
  6. Yeah that was my 1st thought, new 500GB cache drive and 473GB free..
  7. For the last 2 weeks I have been having an issue where Deluge will download torrents just fine then will put any torrent into Pause, existing download or new. It will continue that behavior for a few days and then works fine again. Have rebooted the server, no help, input VPN credentials again and again, no help. So not sure what might be happening here. Log has nothing unusual in it. Any one have this issue lately? Any thoughts as to remedy would be appreciated.
  8. Yes replaced cache drive and rebuilt docker image and reinstalled a docker.. so something else has to be wrong.
  9. So there is still some underlying issue with the GUI freezing up and then even a POWERDOWN command will not restart the box. Dockers install fine then freeze the GUI once you try and start them, recreating the docker image has no effect. I just want to install 6.4.1 to a new fresh USB thumb drive (current one is easily 10 years old). So at this point I just want to preserve the disk & share config and port that into 6.4.1 USB drive. Can the files in the \FLASH\CONFIG\ & \FLASH\CONFIG\SHARES relating to shares and disks just be copied over, anything else necessary? I do not want to take docker, app data, domain, etc.. to the new install, something in there is totally messed up. Don't want to lose data (likely not going to happen), but pretty frustrated with this right now. Diags attached for good measure... unraid1-diagnostics-20180218-1559.zip
  10. Yeah I think so too, picked up new larger PCI-e SSD for cache... thanks for all your help.
  11. SMART finally came back with pre-fails.. so looks like the disk. Lets see if diags say the same... thanks for the assist.
  12. Here are the diagnostics, I opened case and re-seated the SATA connectors on card and SSDs. Shouldn't be bad wires, less than a year old. unraid1-diagnostics-20180216-2158.zip
  13. Its never going to stop messing with me, now I am getting tons of disk errors from cache drive reporting it is Read Only. ErrorWarningSystemArrayLogin Feb 16 20:23:02 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 131944448 csum 0xf5a0e085 expected csum 0x00000000 mirror 1Feb 16 20:23:02 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:02 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 41873408Feb 16 20:23:02 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 41873408 csum 0x844d252a expected csum 0x00000000 mirror 1Feb 16 20:23:02 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:02 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 49410048Feb 16 20:23:02 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 49410048 csum 0xeda1d89a expected csum 0x00000000 mirror 1Feb 16 20:23:02 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:02 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 49410048Feb 16 20:23:02 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 49410048 csum 0xeda1d89a expected csum 0x00000000 mirror 1Feb 16 20:23:43 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:43 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 3104768Feb 16 20:23:43 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 3104768 csum 0x321c030a expected csum 0x00000000 mirror 1Feb 16 20:23:43 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:43 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 41873408Feb 16 20:23:43 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 41873408 csum 0x844d252a expected csum 0x00000000 mirror 1Feb 16 20:23:43 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:43 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 3104768Feb 16 20:23:43 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 3104768 csum 0x321c030a expected csum 0x00000000 mirror 1Feb 16 20:23:43 unRAID1 kernel: BTRFS critical (device sdj1): corrupt leaf, bad key order: block=379185201152, root=1, slot=187Feb 16 20:23:43 unRAID1 kernel: BTRFS info (device sdj1): no csum found for inode 31277 start 41873408Feb 16 20:23:43 unRAID1 kernel: BTRFS warning (device sdj1): csum failed root 5 ino 31277 off 41873408 csum 0x844d252a expected csum 0x00000000 mirror 1Feb 16 20:23:54 unRAID1 kernel: lo_write_bvec: 9 callbacks suppressedFeb 16 20:23:54 unRAID1 kernel: loop: Write error at byte offset 3869896704, length 4096.Feb 16 20:23:54 unRAID1 kernel: print_req_error: 9 callbacks suppressedFeb 16 20:23:54 unRAID1 kernel: print_req_error: I/O error, dev loop2, sector 7558392Feb 16 20:23:54 unRAID1 kernel: btrfs_dev_stat_print_on_error: 9 callbacks suppressedFeb 16 20:23:54 unRAID1 kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 20, rd 0, flush 0, corrupt 0, gen 0Feb 16 20:27:00 unRAID1 root: Fix Common Problems Version 2018.02.16Feb 16 20:27:06 unRAID1 root: Fix Common Problems: Error: Unable to write to cacheFeb 16 20:27:06 unRAID1 root: Fix Common Problems: Error: Unable to write to Docker ImageFeb 16 20:27:06 unRAID1 root: Fix Common Problems: Error: unclean shutdown detected of your server ** IgnoredFeb 16 20:27:09 unRAID1 root: Fix Common Problems: Warning: Template URL for docker application binhex-delugevpn is missing.Feb 16 20:27:10 unRAID1 sSMTP[24828]: Creating SSL connection to hostFeb 16 20:27:10 unRAID1 sSMTP[24828]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256Feb 16 20:27:13 unRAID1 sSMTP[24828]: Sent mail for wwhtpc@gmail.com (221 2.0.0 closing connection f63sm11927568ioj.74 - gsmtp) uid=0 username=root outbytes=863Feb 16 20:37:23 unRAID1 ool www[11230]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' ''Feb 16 20:38:33 unRAID1 login[14662]: ROOT LOGIN on '/dev/pts/0'
  14. Here is what I got when I checked the cache disk: root@unRAID1:~# fsck /dev/sdj fsck from util-linux 2.30.2 e2fsck 1.43.6 (29-Aug-2017) ext2fs_open2: Bad magic number in super-block /sbin/e2fsck: Superblock invalid, trying backup blocks... /sbin/e2fsck: Bad magic number in super-block while trying to open /dev/sdj The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> or e2fsck -b 32768 <device> /dev/sdj contains `DOS/MBR boot sector; partition 1 : ID=0x83, start-CHS (0x0,0,0), end-CHS (0x0,0,0), startsector 64, 250069616 sectors, extended partition table (last)' data