Jump to content

daemian

Members
  • Content Count

    38
  • Joined

  • Last visited

Community Reputation

1 Neutral

About daemian

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. it was user scripts. Once i removed that one the array started. THANK YOU BOTH!
  2. ah sure, thanks for the clarification. I rebooted into safe mode and was able to start the array successfully. So I guess the question is how do I figure out what is hosing things up.
  3. ok i upgraded to 6.8.1 - no change I was able to start the array in maintenance mode (i presume thats what you means by safe mode). Not sure what I should do from here.
  4. I disabled VMs and Docker, and attempted to start. but am still getting the same result. Just hangs on Mounting disks New diagnostics attached if its helpful. dt-ur01-diagnostics-20200117-1633.zip
  5. Correct, the GUI just continues to show "Array Starting - Mounting disks". I can see at least some of the shares on the network, but the problem for me is that Dockers and VMs are not starting. I do see tons of errors on the cache pool: unfortunately I am not physically local to this array, so I cannot swap the cables right now. I will work on getting some cables and hands to the location. Would it be worthwhile to run the scrub prior to swapping the cables, and if so, forgive my ignorance but how do I do that? I did a bit of searching and have found a few different commands, etc. Thanks
  6. here it is dt-ur01-diagnostics-20200117-1325.zip
  7. LIke the subject says, my array wont start. I am not sure what happened exactly, but my parity drive is showing as disabled. When i try to start the array it just sticks at "Array Starting Moutning disks." I thought perhaps the parity drive had failed, so it tried removing the parity drive and starting the array, but the result is the same. I logged in and did a tail -f on /var/log/syslog prior to clicking start eh array, and this is what I got: Linux 4.19.56-Unraid. root@dt-ur01:~# tail -f /var/log/syslog Jan 16 14:19:48 dt-ur01 avahi-daemon[5075]: Joining mDNS multicast group on interface bond0.IPv6 with address fe80::225:90ff:fe67:edd4. Jan 16 14:19:48 dt-ur01 avahi-daemon[5075]: New relevant interface bond0.IPv6 for mDNS. Jan 16 14:19:48 dt-ur01 avahi-daemon[5075]: Registering new address record for fe80::225:90ff:fe67:edd4 on bond0.*. Jan 16 14:19:51 dt-ur01 ntpd[1960]: Listen normally on 4 br0 192.168.0.15:123 Jan 16 14:19:51 dt-ur01 ntpd[1960]: Listen normally on 5 br0 [fe80::c0ea:1ff:fe18:e34%13]:123 Jan 16 14:19:51 dt-ur01 ntpd[1960]: new interface(s) found: waking up resolver Jan 16 14:20:17 dt-ur01 login[4947]: ROOT LOGIN on '/dev/tty1' Jan 16 14:20:29 dt-ur01 ntpd[1960]: receive: Unexpected origin timestamp 0xe1cb440c.faff7bf0 does not match aorg 0000000000.00000000 from server@216.239.35.0 xmt 0xe1cb440d.6acf5e45 Jan 16 14:20:29 dt-ur01 ntpd[1960]: receive: Unexpected origin timestamp 0xe1cb440c.fb00e459 does not match aorg 0000000000.00000000 from server@216.239.35.8 xmt 0xe1cb440d.6bd6d743 Jan 16 14:20:47 dt-ur01 sshd[7419]: Accepted password for root from 192.168.0.101 port 63658 ssh2 Jan 16 14:21:20 dt-ur01 emhttpd: req (1): startState=STOPPED&file=&csrf_token=****************&cmdStart=Start Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (145): /usr/local/sbin/set_ncq sdb 1 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (41): set md_num_stripes 1280 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (42): set md_sync_window 384 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (43): set md_sync_thresh 192 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (44): set md_write_method Jan 16 14:21:20 dt-ur01 kernel: mdcmd (45): set spinup_group 1 0 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (46): set spinup_group 2 0 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (47): set spinup_group 3 0 Jan 16 14:21:20 dt-ur01 kernel: mdcmd (48): set spinup_group 4 0 Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (146): echo 128 > /sys/block/sdb/queue/nr_requests Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (147): /usr/local/sbin/set_ncq sdc 1 Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (148): echo 128 > /sys/block/sdc/queue/nr_requests Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (149): /usr/local/sbin/set_ncq sde 1 Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (150): echo 128 > /sys/block/sde/queue/nr_requests Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (151): /usr/local/sbin/set_ncq sdd 1 Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (152): echo 128 > /sys/block/sdd/queue/nr_requests Jan 16 14:21:20 dt-ur01 kernel: mdcmd (49): start STOPPED Jan 16 14:21:20 dt-ur01 kernel: unraid: allocating 31100K for 1280 stripes (6 disks) Jan 16 14:21:20 dt-ur01 kernel: md1: running, size: 5860522532 blocks Jan 16 14:21:20 dt-ur01 kernel: md2: running, size: 2930266532 blocks Jan 16 14:21:20 dt-ur01 kernel: md3: running, size: 5860522532 blocks Jan 16 14:21:20 dt-ur01 kernel: md4: running, size: 2930266532 blocks Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (153): udevadm settle Jan 16 14:21:20 dt-ur01 root: Starting diskload Jan 16 14:21:20 dt-ur01 emhttpd: Mounting disks... Jan 16 14:21:20 dt-ur01 emhttpd: shcmd (160): /sbin/btrfs device scan Jan 16 14:21:21 dt-ur01 root: Scanning for Btrfs filesystems Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (161): mkdir -p /mnt/disk1 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (162): mount -t xfs -o noatime,nodiratime /dev/md1 /mnt/disk1 Jan 16 14:21:21 dt-ur01 kernel: SGI XFS with ACLs, security attributes, no debug enabled Jan 16 14:21:21 dt-ur01 kernel: XFS (md1): Mounting V5 Filesystem Jan 16 14:21:21 dt-ur01 kernel: XFS (md1): Ending clean mount Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (163): xfs_growfs /mnt/disk1 Jan 16 14:21:21 dt-ur01 root: meta-data=/dev/md1 isize=512 agcount=8, agsize=183141659 blks Jan 16 14:21:21 dt-ur01 root: = sectsz=512 attr=2, projid32bit=1 Jan 16 14:21:21 dt-ur01 root: = crc=1 finobt=1, sparse=0, rmapbt=0 Jan 16 14:21:21 dt-ur01 root: = reflink=0 Jan 16 14:21:21 dt-ur01 root: data = bsize=4096 blocks=1465130633, imaxpct=5 Jan 16 14:21:21 dt-ur01 root: = sunit=0 swidth=0 blks Jan 16 14:21:21 dt-ur01 root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 16 14:21:21 dt-ur01 root: log =internal log bsize=4096 blocks=357698, version=2 Jan 16 14:21:21 dt-ur01 root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 16 14:21:21 dt-ur01 root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (164): mkdir -p /mnt/disk2 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (165): mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 Jan 16 14:21:21 dt-ur01 kernel: XFS (md2): Mounting V5 Filesystem Jan 16 14:21:21 dt-ur01 kernel: XFS (md2): Ending clean mount Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (166): xfs_growfs /mnt/disk2 Jan 16 14:21:21 dt-ur01 root: meta-data=/dev/md2 isize=512 agcount=4, agsize=183141659 blks Jan 16 14:21:21 dt-ur01 root: = sectsz=512 attr=2, projid32bit=1 Jan 16 14:21:21 dt-ur01 root: = crc=1 finobt=1, sparse=0, rmapbt=0 Jan 16 14:21:21 dt-ur01 root: = reflink=0 Jan 16 14:21:21 dt-ur01 root: data = bsize=4096 blocks=732566633, imaxpct=5 Jan 16 14:21:21 dt-ur01 root: = sunit=0 swidth=0 blks Jan 16 14:21:21 dt-ur01 root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 16 14:21:21 dt-ur01 root: log =internal log bsize=4096 blocks=357698, version=2 Jan 16 14:21:21 dt-ur01 root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 16 14:21:21 dt-ur01 root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (167): mkdir -p /mnt/disk3 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (168): mount -t xfs -o noatime,nodiratime /dev/md3 /mnt/disk3 Jan 16 14:21:21 dt-ur01 kernel: XFS (md3): Mounting V5 Filesystem Jan 16 14:21:21 dt-ur01 kernel: XFS (md3): Ending clean mount Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (169): xfs_growfs /mnt/disk3 Jan 16 14:21:21 dt-ur01 root: meta-data=/dev/md3 isize=512 agcount=6, agsize=268435455 blks Jan 16 14:21:21 dt-ur01 root: = sectsz=512 attr=2, projid32bit=1 Jan 16 14:21:21 dt-ur01 root: = crc=1 finobt=1, sparse=1, rmapbt=0 Jan 16 14:21:21 dt-ur01 root: = reflink=0 Jan 16 14:21:21 dt-ur01 root: data = bsize=4096 blocks=1465130633, imaxpct=5 Jan 16 14:21:21 dt-ur01 root: = sunit=0 swidth=0 blks Jan 16 14:21:21 dt-ur01 root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 16 14:21:21 dt-ur01 root: log =internal log bsize=4096 blocks=521728, version=2 Jan 16 14:21:21 dt-ur01 root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 16 14:21:21 dt-ur01 root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (170): mkdir -p /mnt/disk4 Jan 16 14:21:21 dt-ur01 emhttpd: shcmd (171): mount -t xfs -o noatime,nodiratime /dev/md4 /mnt/disk4 Jan 16 14:21:21 dt-ur01 kernel: XFS (md4): Mounting V5 Filesystem Jan 16 14:21:22 dt-ur01 kernel: XFS (md4): Ending clean mount Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (172): xfs_growfs /mnt/disk4 Jan 16 14:21:22 dt-ur01 root: meta-data=/dev/md4 isize=512 agcount=4, agsize=183141659 blks Jan 16 14:21:22 dt-ur01 root: = sectsz=512 attr=2, projid32bit=1 Jan 16 14:21:22 dt-ur01 root: = crc=1 finobt=1, sparse=0, rmapbt=0 Jan 16 14:21:22 dt-ur01 root: = reflink=0 Jan 16 14:21:22 dt-ur01 root: data = bsize=4096 blocks=732566633, imaxpct=5 Jan 16 14:21:22 dt-ur01 root: = sunit=0 swidth=0 blks Jan 16 14:21:22 dt-ur01 root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Jan 16 14:21:22 dt-ur01 root: log =internal log bsize=4096 blocks=357698, version=2 Jan 16 14:21:22 dt-ur01 root: = sectsz=512 sunit=0 blks, lazy-count=1 Jan 16 14:21:22 dt-ur01 root: realtime =none extsz=4096 blocks=0, rtextents=0 Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (173): mkdir -p /mnt/cache Jan 16 14:21:22 dt-ur01 emhttpd: cache uuid: 437a0de9-148c-436a-823b-1f32632b68f2 Jan 16 14:21:22 dt-ur01 emhttpd: cache TotDevices: 2 Jan 16 14:21:22 dt-ur01 emhttpd: cache NumDevices: 2 Jan 16 14:21:22 dt-ur01 emhttpd: cache NumFound: 2 Jan 16 14:21:22 dt-ur01 emhttpd: cache NumMissing: 0 Jan 16 14:21:22 dt-ur01 emhttpd: cache NumMisplaced: 0 Jan 16 14:21:22 dt-ur01 emhttpd: cache NumExtra: 0 Jan 16 14:21:22 dt-ur01 emhttpd: cache LuksState: 0 Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (174): mount -t btrfs -o noatime,nodiratime -U 437a0de9-148c-436a-823b-1f32632b68f2 /mnt/cache Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): disk space caching is enabled Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): has skinny extents Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): bdev /dev/sdg1 errs: wr 3408448785, rd 2878657541, flush 77125088, corrupt 0, gen 0 Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): bdev /dev/sdh1 errs: wr 387, rd 1, flush 0, corrupt 0, gen 0 Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): enabling ssd optimizations Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (175): /sbin/btrfs filesystem resize 1:max /mnt/cache Jan 16 14:21:22 dt-ur01 root: Resize '/mnt/cache' of '1:max' Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (176): /sbin/btrfs filesystem resize 2:max /mnt/cache Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): resizing devid 1 Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): new size for /dev/sdg1 is 500107829248 Jan 16 14:21:22 dt-ur01 root: Resize '/mnt/cache' of '2:max' Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): resizing devid 2 Jan 16 14:21:22 dt-ur01 kernel: BTRFS info (device sdg1): new size for /dev/sdh1 is 500107829248 Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (177): sync Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (178): mkdir /mnt/user0 Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (179): /usr/local/sbin/shfs /mnt/user0 -disks 30 -o noatime,big_writes,allow_other |& logger Jan 16 14:21:22 dt-ur01 shfs: stderr redirected to syslog Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (180): mkdir /mnt/user Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (181): /usr/local/sbin/shfs /mnt/user -disks 31 2048000000 -o noatime,big_writes,allow_other -o remember=0 |& logger Jan 16 14:21:22 dt-ur01 shfs: stderr redirected to syslog Jan 16 14:21:22 dt-ur01 emhttpd: shcmd (183): /usr/local/sbin/update_cron Jan 16 14:21:22 dt-ur01 root: Delaying execution of fix common problems scan for 10 minutes Jan 16 14:22:01 dt-ur01 sSMTP[9952]: Creating SSL connection to host Jan 16 14:22:01 dt-ur01 sSMTP[9952]: SSL connection using TLS_AES_256_GCM_SHA384 Jan 16 14:22:05 dt-ur01 sSMTP[9952]: Sent mail for admin@dirtyturtle.com (221 2.0.0 closing connection k6sm10383601ywh.56 - gsmtp) uid=0 username=root outbytes=920 Jan 16 14:24:20 dt-ur01 nginx: 2020/01/16 14:24:20 [error] 5132#5132: *68 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.101, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "192.168.0.15", referrer: "http://192.168.0.15/Main" Jan 16 14:25:30 dt-ur01 ntpd[1960]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jan 16 14:31:00 dt-ur01 root: Fix Common Problems Version 2019.12.29 Jan 16 14:31:01 dt-ur01 root: Fix Common Problems: Warning: Share appdata set to cache-only, but files / folders exist on the array Jan 16 14:31:09 dt-ur01 sSMTP[25208]: Creating SSL connection to host Jan 16 14:31:09 dt-ur01 sSMTP[25208]: SSL connection using TLS_AES_256_GCM_SHA384 Jan 16 14:31:11 dt-ur01 sSMTP[25208]: Sent mail for admin@dirtyturtle.com (221 2.0.0 closing connection d186sm10664771ywe.0 - gsmtp) uid=0 username=root outbytes=865 Any idea what the hang up is? Thanks
  8. OK cool. Thanks to both of you. Does -ur seem like the appropriate rsync flags given the desired operations?
  9. Hey everyone, So I created a bit of a mess, and life has just been too busy to deal with it. I finally got a chance to try to address it, but I realized I better ask for some advice before I make things worse. I am not exactly sure what happened, but here is the story. I had a drive fail and so I replaced it back in December (I think it was Dec). I do not know what I did wrong, but when I swapped in the new drive - the array did not rebuild the contents onto the new drive using parity. I put it in the slot of the old failed drive (disk 2 in my case), but I ended up with an empty disk 2 and parity must have been rebuilt at some point. At first, I didnt even realize what had happened. Then once I realized, I couldn't get the old drive to mount using the unassigned devices plugin and I did not have time to address it. Fast forward about a month and a half and the good news is after reseating the sata cable I can now mount up the old drive using unassigned devices. The files are there. But, meanwhile, my new disk 2 also has files on it. A few of my dockers (nextcloud and paperless) have files that they think are there in the db, but are missing on the actual filesystem. And outside of those apps there are files on the old disk that are no longer on the user shares. So, how do I best get the missing files back onto the array? My first thought was to use rsync with the '-ur' flags with the source of the old disk and the destination of the new disk. But then I realized that would probably create parity issues? So perhaps I should using rsync -ur with a source of the old disk and a destination of '/mnt/user/' ? The goal would be to copy any files or folders that are on the old disk, but not on the array. However, if there is a file that already exists on the array - don't overwrite it (since I have been running for about a month). Does that seem like the right approach? If so, any other rsync options I should use or is there something better I should do rather than rsync running in a tmux window? Thank for any advice. Not sure how I fubar'ed the simple disk swap, but i will just admit my stupidity and ask for help to rectify the situation now.
  10. You were exactly right. Started looking into some other issues I had and there was something wrong with the new disk I inserted. Not sure if my failed disk wrote to corrupted data to parity or what exactly happened but at the end of the day I had to re-format my new disk. Some data was certainly lost - but I will see if I can get anything off the old disk or restore from backups. The good news is my stuff is working again. Thanks anyhow!
  11. Hi - hoping I can get some help. I have been happily running this container for a few years - its awesome. Unfortunately, I recently had some issues with a disk that was failing (it has been replaced and parity rebuilt). During this time I also had to hard down the unraid server once. I ran the parity check after before proceeding with the disk replacement. Now - my nextcloud docker will start, but my clients do not connect (red icon) and when I try to browse to the webpage I get Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log. If i look at the docker log I see: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 40-config: executing... chown: changing ownership of '/data': I/O error [cont-init.d] 40-config: exited 0. [cont-init.d] 50-install: executing... [cont-init.d] 50-install: exited 0. [cont-init.d] 60-memcache: executing... [cont-init.d] 60-memcache: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. I tried running the Docker Safe New Permissions. I am not sure if it actually ever finished (the page errored out after like 12 hours) - but it did not help. My nextcloud share (mapped to /data in the docker) has the following permissions on the share folder, and the folder below (I obfuscated the user folder names): root@ur01:/mnt/user# ls -al | grep nextCloud drwxrwx--- 1 nobody users 252 Jan 7 2018 nextCloud/ root@ur01:/mnt/user# ls -al nextCloud/ total 112856 drwxrwx--- 1 nobody users 252 Jan 7 2018 ./ drwxrwxrwx 1 nobody users 48 Nov 4 11:57 ../ -rw-rw-rw- 1 nobody users 4096 Jan 26 2017 ._.DS_Store -rw-rw-rw- 1 nobody users 324 Oct 8 10:40 .htaccess -rw-rw-rw- 1 nobody users 0 Jan 26 2017 .ocdata drwxrwxrwx 1 nobody users 44 Jan 31 2017 admin/ drwxrwxrwx 1 nobody users 115 Aug 21 2018 appdata_ocnuvolb7k5t/ drwxrwxrwx 1 nobody users 96 Apr 5 2018 user1/ drwxrwxrwx 1 nobody users 6 Oct 8 10:40 files_external/ -rw-rw-rw- 1 nobody users 0 Jan 26 2017 index.html drwxrwxrwx 1 nobody users 96 Jan 7 2018 user2/ -rw-r----- 1 nobody users 110798670 Nov 8 10:00 nextcloud.log -rw-rw-rw- 1 nobody users 581632 Jan 26 2017 owncloud.db I have also deleted the docker.img file (because of issues on a different docker) and the problem persists. Any idea what i can look at to fix this? Thank you!
  12. I Love unraid and it just keeps getting better with every release. Happy Birthday!
  13. Thanks Johnnie. I upgraded to 6.5.3 and tried xfs_repair against. Still no luck. Putting this disk in another machine is not really an option for me with this one (I am remote to the site, and there are not much in the way of resources there). I think I may need to bite the bullet and just format the drive, conceding that the data from that drive is lost. Its probably not really that big of a deal. Obviously not ideal, but I don't think I have much other choice. Would I just format that drive and then run a parity check to be sure everything is ok?