AndrewT

Mount it, so it has a path to give dd of=<path>

Precleared disk listed in Unassigned Devices, but the "Mount" GUI button is greyed out, which I assumed was because it lacks a filesystem(?)

But how can I mount sdk then?

I have disks that are precleared but not formatted. When you add a disk to the array, which formats it properly, doesn't that modify the parity disk as well because the array expands? I can see the precleared disks have "device" IDs assigned under "Unassigned Devices" but is there a way to mount it and format a disk without adding it to the array?

The first time I ran badblocks, I put the log file on my flash drive and noticed the output was over 2GB and still running. I worried the file would fill up my USB, so I killed it (and foolishly removed it). The second time I ran it, I put it on my cache disk `badblocks -v -o /mnt/cache/md4.badblocks.log /dev/sdo1` but now the log file is empty and it finished and printed: Checking blocks 0 to 3907018534 Checking for bad blocks (read-only test): done Pass completed, 0 bad blocks found. (0/0/0 errors) Running it the first time wouldn't have fixed it, so since I don't have the first log listing the bad blocks and now it won't give any, is the disk4 just toast now and I have to rely on a ~80-90% backed up disk version of it?

Weird, so `reiserfsck --rebuild-tree /dev/md4` failed with this printed out: block 97091595: The number of items (1) is incorrect, should be (0) - corrected block 97091595: The free space (32768) is incorrect, should be (4072) - corrected 20% left 390393334, 14207 /sec The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. bread: Cannot read the block (98002942): (Input/output error). Aborted I looked for `badblock` and tab-completion indicates no such thing exists, only badblocks but the help menu lacks a -B option. I then tried `reiserfsck --help` and see the -B option exists there to specify a file with list of all bad blocks on the fs. Does this mean I should somehow re-run reiserfsck in such a way that it lists files with bad blocks and redirect stderr (or stdout?) to a file, then give that file to -B <file>? It seems there's a warning to not run the --rebuild-sb twice or data will be lost, but is that also true for just --rebuild-tree (source: https://www.cyberciti.biz/tips/repairing-reiserfs-file-system-with-reiserfsck.html ) ?

Thanks, I am running `reiserfsck --rebuild-tree /dev/md4` after `reiserfsck --check /dev/md4` suggested it: Checking internal tree.. block 471171107: The level of the node (52700) is not correct, (4) expected the problem in the internal node occured (471171107), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree

I updated the attachment from only the sys log to the entire diagnostics dump.

My issue is related to this post but I might need a different solution: I haven't written anything to the array since this has happened, but have been trying to fix it without any luck for a couple weeks now. Attached is a syslog after rebooting. Disk2 red balled on me, but the contents are emulated, because I was able to fully rsync the disk to my cache disk as backup (rsync /mnt/disk2 /mnt/cache/bak.disk2). I've tried twice to repair the red disk with a fresh precleared disk and both stopped rebuilding the array when it accumulated hundreds of write errors. I initially thought I just had a bad unlucky disk, but 2 in a row seemed unlikely especially after successful runs of preclear prior to adding them. Disk4 reads as Unmountable - No file system (32) and when I tried plugging it in to a Linux desktop, mounting truly doesn't seem to be possible with an error "dsk image failed : can't read superblock" What's curious to me is that disk4 is green, not red, yet remains unmountable to read the array files on it. What should I do to try to save the data from disk2 (backed up on cache) and disk4 (?) and get the array back up to running happily? I'm particularly unsure of how I might be able to save the data from disk4. Ironically, I have plenty of precleared disks that I'm preparing to build a backup tower. tower-diagnostics-20170606-1840.zip

I just upgraded to Krypton from Eden and glad to see other than the skin default it feels similarly as simple to navigate TV Shows and Movies as before. Something that concerns me is the huge increase in popularity of certain add-ons that could make the whole Kodi project develop a bad name. I only have a 1080p TV, not 4k, and recently got a Pi3 with OSMC and have been really impressed at the cost. The build of Pi3 with OSMC install direct from the install menu from NOOBS loaded on the microSD card just felt too easy compared to the older Apple TV 1 with broadcom crystal hd conversion and USB install of crystalbuntu. I held off for many years thinking the Pi wasn't powerful enough, so I can't say anything about the earlier versions, but my Pi3 handles 1080p wirelessly just fine for me on the newest Kodi Krypton within OSMC. I'd recommend this setup instead of the more expensive Chromebox.

Thank you so much for your work on this! It works very well and I'm able to stream music onto my laptop which can pass bluetooth to my stereo receiver. I also have the free Android app Subsonic Music Streamer working. Initially it couldn't connect but creating an admin + password setup worked.

Thanks for your post. I just had a similar issue and resolved it by going into Maintenance Mode, then used: reiserfsck --check /dev/md1 reiserfs_open: Your partition is not big enough to contain the filesystem of (488381143) blocks as was specified in the found super block. Failed to open the filesystem. If the partition table has not been changed, and the partition is valid and it really contains a reiserfs partition, then the superblock is corrupted and you need to run this utility with --rebuild-sb. reiserfsck --fix-fixable --rebuild-sb /dev/md1 reiserfsck --check /dev/md1 Before going off Maintenance mode and back to online.

Has anyone else been able to play music from the most updated version lately? It all worked with unraid 5 and a plugin but this Docker in unraid 6 is a new beast apparently.

I installed gfjardim/logitechmediaserver and scanned my music in, but I can't figure out why it isn't able to play music through the port 9000. Under Server Settings -> Player -> I see "Your player was not found." Here are my mappings: 3483/tcp 10.0.1.30:3483 3483/udp 10.0.1.30:3483 9000/tcp 10.0.1.30:9000 9090/tcp 10.0.1.30:9090 /config /mnt/cache/appdata/LogitechMediaServer/ /music /mnt/user/Music/ I initially had /config to /mnt/user/appdata/LogitechMediaServer/ but tried this new mapping to see if it was the issue I haven't used LMS in a couple years but I thought you were able to play music directly from logging into that port that brings up the LMS web interface? I used to have an iOS device with iPeng (~$10) and worked perfectly but now with Android I've tried apps: Squeezer, Squeeze Commander, and Squeezebox but am unable to connect to the server:9000

This was the issue -- my misunderstanding of the /mnt/user path. Thank you so much! It's clear now I should have been looking into the /mnt/user0 path if my 'cache only' share showed up and it didn't. To summarize: /mnt/cache = cache only shares (optionally will transfer onto array shares) /mnt/user0 = array shares only /mnt/user = array shares + cache only shares

I've been trying to figure out a way to keep dirs on my cache disk only and not be copied or moved onto the array (/mnt/user). As soon as I `mkdir /mnt/cache/.appdata` this is also created as /mnt/user/.appdata. This was the same for unhidden dirs when I tried `mkdir /mnt/cache/APPDIR` and it again immediately showed up in /mnt/user/APPDIR. I thought this behavior was odd, so I pulled out all my hair and restarted my server but I'm still having this issue. Similarly, when I use the WebGUI and create a new share 'ABCD' with default settings other than Use cache disk: Only, this again shows up as quick as I can cd into it: /mnt/user/ABCD. What besides the mover could be doing this? I recently upgraded to unraid 6. All disks are still reiserfs. The 'Disk Shares' is a new concept to me and remains empty, but I have several 'User Shares.' The mover schedule is set to just once a day which wouldn't explain this near-instant copying behavior. cat /boot/config/plugins/dynamix/mover.cron # Generated mover schedule: 40 2 * * * /usr/local/sbin/mover |& logger If this belongs in my other post, feel free to move mods: http://lime-technology.com/forum/index.php?topic=52163.msg502956#msg502956

Thanks for the referencing link. As you warn, it sure looks like a hack and is likely to be undone at some point. These responses made me think I'm the weird one not wanting the cache disk to have its content copied onto the array. As BobPhoenix mentioned, when I used unraid v5 I just used the cache disk to store everything to do with apps (configs, temp downloads, etc) and I back it up manually with an rsync before making big changes to a subdir within a share on my array. The one time I trusted it to transfer a bunch of documentaries I lost them, so I'm still a bit scared of the 'mover' function. I dug into the mover function for unraid 6 and it's a very well documented bash script written (credit to limetech): `less -S /usr/local/sbin/move` to view. The commenting is so good it reminded me of a trick I've forgotten about in moving from unraid 5 to 6, which is that **hidden paths are ignored by the mover!** Also, for limetech, there's a typo on L35 in the commenting: `sed -i 's/arary/array/1' /usr/local/sbin/move` So, I think this might be the best approach instead of hacking a mover disabling altogether is to just hide the handful of paths I don't want mover to touch. Please suggest otherwise if any of you disagree. Example fix: mv /mnt/cache/appdata /mnt/cache/.appdata

As others have noted, fancy backup solutions like CrashPlan allow you to hold onto files for a given time even if your path your backing up now has the file removed. Rsync is nice and is what I use mostly but I don't know of an easy solution to the feature of holding onto a file that was deleted within the past year (as an example). Here's what I use for rsync to preserve time stamps and permissions: rsync -lrtuvD <current-path-to-backup> <backup-path> I do that manually once or twice a year with files especially important to me.

Is there any way from the webgui to disable the mover? It looks like: rm /boot/config/plugins/dynamix/mover.cron && update_cron will prevent the mover from running, I'm but just surprised the option "Disable" under Scheduler->Mover schedule is lacking considering right above it the "Parity Check" cron task does have the "Disable" option.

Thanks for the link. I didn't get that far down the FAQ before.

I didn't know you can create specific paths within a Docker symlinked to the array with a specified permission (Read only, RW, etc). So you're saying I'd have couchpotato move files from CompletedDownloads/Unprocessed/movies onto a new path that could be linked directly to the array? Something like this: Update Container -> + Add another Path, Port or Variable (Add Configuration window) Config Type: Path Name: symlink-to-Movies-array Container Path: /scraped-Movies Host Path: /mnt/user/Movies Access Mode: Read/Write

I'm curious what some of you are doing once your Dockers have downloaded and scraped the files to get them onto your array. Do you have special permissions setup on a couple Dockers so this is done automatically or do you occasionally ssh as user 'nobody' and group 'users' onto your server to manually move the files from their sandboxed areas to the array? I'm just starting to setup Dockers for SickRage, CouchPotato, Headphones, Transmission, and SABnzbd. From my understanding, the value is to have these apps sandboxed so if something goes awry that they don't disrupt the important system configs and array, but as a consequence none will be able to move completed and scraped files onto the array, is that correct? Here was my former structure in unRAID 5 with plugins (excluding the red): /mnt/cache/.apps/ couchpotato headphones sabnzbd sickbeard transmission /mnt/cache/.incompletedownloads/ <dumping place for all sab and transmission downloads> /mnt/cache/CompletedDownloads/ Processed ? ebooks ? movies ? music ? tv Unprocessed ebooks gamez movies music tv I didn't have the red directories before because once the files were properly scraped, they'd be added right onto their respective shares, such as /mnt/user/movies /mnt/user/tv /mnt/user/music , etc. I'd prefer not to have the red directories, so what are your thoughts?

Mobo: ASRock 880GM-LE FX AM3+ AMD 880G Micro ATX RAM: Patriot Signature 4 GB PC3-10600 (1333 MHz) DDR3 CL9 I believe the CL9 indicates a 9-9-9-24 latency timing. By relaxing (underclocking?) are you suggesting to increase the latency numbers, decrease the frequency/Hz, decrease voltage, or a combination of these?

Thanks for clarification that mover uses rsync. Memtest was helpful! I am in the process of RMAing one of my 2 ram sticks, but the other was in its 4th pass with 0 errors. I booted into safemode and invoked mover but unRAID still freezes. When I typed mover in the telnet session, additional info was printed because before I used the webGUI mover (attached as mover_errors.txt) It looks like there's a problem with rsync but I don't understand. Syslog is also attached separately. *edit: mover_errors.txt file added syslog.txt mover_errors.txt

Thank you for your response! Your explanations of the errors in the syslogs are really helpful for my understanding. I'll run memtest for 3 cycles, then boot into safemode and try to invoke mover by telnetting and just typing mover I hope this is the correct way to do it? The unRAID Wiki indicates /usr/share/sbin/mover uses find and mv but I noticed only rsync in my syslogs http://lime-technology.com/wiki/index.php/Cache_disk#The_Mover I hope to report back and mark this as solved.