project6

Here is the output from --rebuild-tree, not sure how I should interpret it... looks like it didn't finish? Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Thu Nov 19 10:43:56 2020 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 488378638 blocks marked used Skipping 23115 blocks (super block, journal, bitmaps) 488355523 blocks will be read 0%block 11428318: The number of items (3) is incorrect, should be (1) - corrected block 11428318: The free space (480) is incorrect, should be (1040) - corrected pass0: vpf-10210: block 11428318, item 0: The item with wrong offset or length found [2145255427 4292362239 0x66460007 DRCT (2)], len 3008 - deleted block 12095023: The number of items (1027) is incorrect, should be (1) - corrected block 12095023: The free space (0) is incorrect, should be (4048) - corrected pass0: vpf-10150: block 12095023: item 0: Wrong key [0 0 0x4 SD (0)], deleted ....20%....40%....60%....80%....100% left 0, 40403 /sec 2558925 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 488355523 Leaves among those 601777 - leaves all contents of which could not be saved and deleted 3 Objectids found 2559678 Pass 1 (will try to insert 601774 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....Not enough allocable blocks, checking bitmap...there are 1 allocable blocks, btw out of disk space Aborted This is what it looks like after trying to start the array now:

Ok, will do. Should I keep the array in maintenance mode for the SMART run or can I enable the array after the rebuild-tree?

Thanks. It's running and correcting stuff now, it will take a couple of hours. So I guess this is a symptom of the disk going bad? Never happened to me so far. My cabinet is unfortunately full so I can't easily just extend with another drive, I'd prefer to size up my partition drive first and then replace existing drives with larger ones.

Should I try running: reiserfsck --rebuild-tree /dev/md3 as suggested? I get a massive ASCII warning prompt when attempting it and not sure if I should continue

Filesystem check output: reiserfsck 3.6.27 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' ########### reiserfsck --check started at Thu Nov 19 08:56:55 2020 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..Bad nodes were found, Semantic pass skipped 2 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Thu Nov 19 09:38:07 2020 ########### bad_path: The right delimiting key [4546696 4546697 0x19544001 IND (1)] of the node (423911883) must be greater than the last (2) element's key [4547201 4547202 0x1 IND (1)] within the node. block 423912896: The level of the node (48314) is not correct, (1) expected the problem in the internal node occured (423912896), whole subtree is skipped bad_stat_data: The objectid (4547202) is shared by at least two files. Can be fixed with --rebuild-tree only. bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (0) to the block (38724350), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (1) to the block (38724351), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (2) to the block (38724352), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (3) to the block (38724353), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (4) to the block (38724354), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (5) to the block (38724355), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (6) to the block (38724356), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (7) to the block (38724357), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (8) to the block (38724358), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (9) to the block (38724359), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (10) to the block (38724360), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (11) to the block (38724361), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (12) to the block (38724362), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (13) to the block (38724363), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (14) to the block (38724364), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (15) to the block (38724365), which is in tree already bad_indirect_item: block 380601268: The item (4547201 4547202 0x1 IND (1), len 68, location 820 entry count 0, fsck need 0, format new) has the bad pointer (16) to the block (38724366), which is in tree already vpf-10640: The on-disk and the correct bitmaps differs.

Yep, filesystem check is in progress.

I've been running Unraid for years without a single problem, currently using version 6.8.0. A few days ago I started receiving email alerts that disk3 was full (100%) but was not able to look into it since I didn't have access to the server for a few days. I figured it will just assign new data to the other disks (there is plenty of space left on at least one drive). When I managed to get access to the UI I logged in and found this: So I logged in on the server and `df -h` shows this: Filesystem Size Used Avail Use% Mounted on rootfs 3.8G 985M 2.9G 26% / tmpfs 32M 480K 32M 2% /run devtmpfs 3.8G 0 3.8G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 224K 128M 1% /var/log /dev/sda 7.3G 611M 6.7G 9% /boot /dev/loop0 9.0M 9.0M 0 100% /lib/modules /dev/loop1 5.9M 5.9M 0 100% /lib/firmware /dev/md1 1.9T 1.7T 138G 93% /mnt/disk1 /dev/md2 1.9T 1.7T 165G 92% /mnt/disk2 /dev/md3 1.9T -15T 16T - /mnt/disk3 /dev/md4 1.9T 214G 1.7T 12% /mnt/disk4 /dev/sdb1 56G 50G 6.1G 90% /mnt/cache shfs 7.3T -11T 18T - /mnt/user0 shfs 7.4T -11T 18T - /mnt/user /dev/loop2 60G 26G 31G 46% /var/lib/docker shm 64M 0 64M 0% /var/lib/docker/containers/.../mounts/shm shm 64M 0 64M 0% /var/lib/docker/containers/.../mounts/shm As you can see my disk3 is reporting as -15 TB used and 16 TB available. The mover doesn't like this, and it had been invoked probably with this information and was stuck so and I couldn't do anything but force a shutdown/reboot. Is there anything I can do to recover disk3 and get it back to reporting it's original used/free space? Solution I got some excellent help from @JorgeB and managed to solve this without data loss, so I figured I'd describe the process here instead of needing to read through all the posts. The short answer is to get a disk that's larger than the one that filled up (in my case a 2 TB drive got filled up so I used a 4 TB USB external drive) and clone the disk and fix it on the larger drive, then copy back the data. Note: Many of these commands destroy data on the target device so always double check that you use the correct devices and partitions throughout. So the first step is to check the filesystem on the filled up array device. In my case this was /dev/md3: reiserfsck --check /dev/md3 It reported errors and needed to be run with --rebuild-tree, so I tried that: reiserfsck --rebuild-tree /dev/md3 This took a while and corrected some blocks and sizes, but during the allocation phase the process aborted since it did not have enough free space on the drive: Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Thu Nov 19 10:43:56 2020 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 488378638 blocks marked used Skipping 23115 blocks (super block, journal, bitmaps) 488355523 blocks will be read 0%block 11428318: The number of items (3) is incorrect, should be (1) - corrected block 11428318: The free space (480) is incorrect, should be (1040) - corrected pass0: vpf-10210: block 11428318, item 0: The item with wrong offset or length found [2145255427 4292362239 0x66460007 DRCT (2)], len 3008 - deleted block 12095023: The number of items (1027) is incorrect, should be (1) - corrected block 12095023: The free space (0) is incorrect, should be (4048) - corrected pass0: vpf-10150: block 12095023: item 0: Wrong key [0 0 0x4 SD (0)], deleted ....20%....40%....60%....80%....100% left 0, 40403 /sec 2558925 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 488355523 Leaves among those 601777 - leaves all contents of which could not be saved and deleted 3 Objectids found 2559678 Pass 1 (will try to insert 601774 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....Not enough allocable blocks, checking bitmap...there are 1 allocable blocks, btw out of disk space Aborted So I plugged in the external drive and made sure I knew what dev was assigned using dmesg (/dev/sdh in my case). My external drive came with some preinitialized Windows partitions, so I erased them using fdisk and cleared the drive to zeroes using dd: dd if=/dev/zero of=/dev/sdh status=progress Then I cloned the full disk to the external drive. Note: make sure to use the actual disk (/dev/sdX) and not the raid device (/dev/mdX). In my case /dev/md3 was /dev/sdg: dd if=/dev/sdg of=/dev/sdh status=progress Once finished, you have a copy of the disk on the external drive. The external drive now has a 2 TB partition, we need to extend that so we have enough space to rebuild the file system. I removed the existing partition (again with fdisk) and created a new one with the same start sector but utilizing the entire disk instead of 2 TB. The start sector should be 64 and this can not be set with fdisk, however it can be done using sgdisk. This command will create a new partition with correct start sector and using all available space on the disk: sgdisk -o -a 8 -n 1:32K:0 /dev/sdh I then re-created the superblock as explained here and then ran the reiserfsck command to rebuild the tree again on the new partition: reiserfsck --rebuild-tree /dev/sdh1 Since the new partition now covers the entire 4 TB drive, the scanning and allocation phases is going to take a long time. Especially if you use a USB drive like I did. When finished you should have a working reiserfs file system on the USB drive! I mounted the drive using the Unassigned Devices plugin and looked through the files making sure everything was OK. As a final step I formated the old 2 TB drive using the unraid web UI and then I manually copied over the data from the mounted USB disk back to the freshly formated 2 TB drive. This is also a good opportunity to format in e.g. xfs instead of reiserfs. Once everything is back on the original disk, and verified, you can release the USB external drive and use it for something else.

I'm having some troubles with the influxdb container. Not sure if it's docker related or if it's in the actual software. I can create a new influxdb container just fine, everything starts up and I can for example create a new database using the command line `influx` followed with `create database whatever`. After doing this however, no external requests come through. (I get read timeouts and the log shows 500 errors) and upon restarting the container the influxdb service is stuck at the following ts=2019-01-03T10:41:37.540767Z lvl=info msg="Open store (start)" log_id=0Clpi4cl000 service=store trace_id=0Clpi510000 op_name=tsdb_open op_event=start I had this working a couple of weeks ago, this happened the last few days. I tried a couple of different tags down to version 1.6 but still the same. Solved: It turns out this docker container does not work when the Unraid Global Share Setting Tunable (enable Direct IO) is set to True, I set it back to Auto and everything works as expected.

Hi, I just upgraded to 6.4 and when I SSH to the machine and hit backspace the caret is moved forwards instead of backwards. I use the exact same client to other linux machines and it works as expected there. Tried setting different TERMs but it doesn't seem to help. Any ideas?

Would it be possible to add the awk program to this image? I'm pretty sure it's been in there before but recently I've been adding it myself after noticing it is missing. It is quite useful in the pre/post scripts. pacman -S awk

Awesome plugin. Instead of routing all traffic, Is there any way to select which of the Unraid Docker containers should use the OpenVPN interface?

Hi, anyone got the Cups image working withGoogle Cloud Print? For me authentication fails, I have two-factor auth enabled on my account. (I tried with several app-specific passwords)

Hi, I've been running Unraid 5.0-rc3 since its release without any problems, I noticed today a 5.0 final version is available. 1) Are there any major bug/performance fixes between rc-3 and final? 2) What are the upgrade instructions from rc-3 to final? The change notes just says "backup your Flash, reformat, re-install, restore 'config' directory, and then reboot". Reformat what? Thanks, Edit: I read through the entire changes document and I now understand the phrase above refers to the 4.7 installation instructions. I'm going to follow that to upgrade.

I had a quick go at this, but no success. The events don't seem to be triggering. I just had a look in the /usr/local/emhttp/plugins and I see some other applications placed event scripts there as well, however they seem to use unmounting_disks and not stopping_services, I will try with that name instead. Edit: This event is not triggered on my installation of Unraid 5-rc3: /usr/local/emhttp/plugins/<myappname>/event/stopping_services Instead I use the following, which is working great: /usr/local/emhttp/plugins/<myappname>/event/unmounting_disks

What version of unRAID are you using? If the 5.0-rc series, then unRAID DOES have event hooks to start processes AFTER the array is online, and to kill them BEFORE the array is stopped. See here on how you might use them: http://lime-technology.com/forum/index.php?topic=26201.msg228957;topicseen#msg228957 In the 4.6/4.7 series you can use a unraid_addon_control.sh script similar to the one I described (and attached) in this post: http://lime-technology.com/forum/index.php?topic=5686.msg53271#msg53271 I've been using unraid_addon_control.sh for a number of years now and it works perfectly. (It would work on the 5.X series too, but the built in events are easier for plugin users to utilize.) I use it to start a number of add-ons after the array is started, and to properly stop them prior to the array when the array is being stopped. Here is an example of somebody using the unraid_addon_control.sh script: http://lime-technology.com/forum/index.php?topic=10978.msg199652#msg199652 Joe L. I am indeed using 5.0 rc3 so I will look into the event hooks. Exactly what I was looking for, thanks!

I have some custom applications that are installed/started in my go script. Everything starts up like I want it. The problem is if I want to restart Unraid, I go to the web interface and click Stop to take the array off-line. Now unraid seems to wait forever for certain processes before it can take the array offline. I need to manually kill these processes. 1) The processes don't seem to be using the filesystem, so I'm not sure why unraid needs to wait for them - is there any way to see if/what the processes are using to cause this behavior? 2)Is there any way I can have these processes killed when clicking the stop array button in the web UI? Either by installing/running them in some specific manner or if there is some way to attach a script to this stop event? Thanks,

Hi, I'm trying to get my blink(1) device working with my Unraid server. I'm curious if anyone on the forum is using this device and got it working with Unraid? (5.0-rc3) There is a command-line tool for Linux available on the blink(1) product page, but it does not work out of the box. I tried downloading the source and building it myself but I get a lot of errors. Reading the Makefile it seems to have the following dependancies: gcc-avr avr-libc libusb-1.0.0-dev (should be included) I googled the AVR stuff to try and find some packages to install but it seems ot require even more dependencies, etc, etc. A pre-compiled version of the blink(1) command-line tool, working with Unraid, would be great! /project6

Can anyone put together a script that downloads and installs FlexGet on startup, or better yet, put together a Unraid 5 FlexGet addon? It's a great little tool and the old file I used to install it is no longer available.

Hi, installed unraid a few days ago. Got plex running easy, also got flexget working with transmission. I have some problems connecting to trackers though. I checked my configuration and I am reachable (port is open). It seems to work if I use http trackers but not https. Is https not supported? Or do I need to make some configuration change in order to communicate with a https tracker, like add/trust the certificate or something? Thanks Edit: Went back to HTTP trackers for now. Could be a tracker problem, not sure.