gshipley

Awesome! Thanks mate. I have been struggling all day and this solved my issue.

Wow, late to this thread but yeah, I created and still maintain a docker for bliss and the template provided in this thread is correct. I did update it a few months ago to work correctly with file permissions. I pushed a new version yesterday actually. I should probably ping squid to get it added to community applications as I have been using it for almost 6 months with no issues.

Yeah, pretty much any subsonic client will work with this for iOS. However, you will not get the dedicated audiobook style features. My favorite one is called SubHub.

Bumping this as I am seeing the same problem...

Where is the bash_profile that gets used when unraid boots? I want to make some changes to it like: TERM=xterm But I am under the impression that if I modify the /root/.bash_profile that it will get rewritten on reboot. Maybe this isn't the case but I can't reboot my server right now to test it out.

Have you ran a reiserfck --check /dev/md(drive letter) on it? If so, did it suggest that you run with rebuild-tree?

Currently using the following: http://www.newegg.com/Product/Product.aspx?Item=N82E16817139006 CORSAIR TX Series CMPSU-750TX 750W ATX12V v2.3 SLI Ready CrossFire Ready 80 PLUS BRONZE Certified Active PFC Compatible with New 4th Gen CPU Certified Haswell Ready I also have a spare (new in box) power supply as well that is not currently being used. Rosewill ATX 12V 750-Watt 80 PLUS BRONZE Certified Power Supply Hive-750 http://www.amazon.com/gp/product/B005ILWYT6?psc=1&redirect=true&ref_=oh_aui_detailpage_o06_s00 I really appreciate the help!

Attached is the complete diagnostics information. Upon reboot the unmountable drives changed from 7, 8 and 10 to 7 and 14. hog-diagnostics-20150805-1126.zip

Yeah, sorry for the confusing wording. When I said rebuilding I did indeed mean rebuilding the data drives based off of parity. The last data drive should be rebuilt in a few minutes. I will reboot after that and provide more logs. The previous thread in question is: https://lime-technology.com/forum/index.php?topic=41875.0

Bumping this. Am I asking the question wrong or wording it so it confuses people or is it just weird error that most haven't seen and can't help out with? I honestly have searched for answers but if it is a common issue, I am happy reading doc if someone can point me to the right one.

syslog attached: If you haven't viewed my other threads, I recently upgraded my system mobo/cpu/ram and hit the virt sata add-on card problems with marvel controllers. I am using a new 8x pcix add on card with the on mobo ports to eliminate the bad cards. Once i got all the new hardware "working" things were fine for a day and then I had a drive failure (red x) with a ton of read errors. So I replaced the drive. Once parity rebuilt I had another drive failure so I replaced that one as well. Now while parity is rebuilding on that drive (I just recently rebooted) three of the drives are showing as unmountable again. disk7 for example is one that had a million read errors during party rebuilt so I did the following: reiserfsck --check /dev/md7 When that finished it wanted me to do it with a rebuild-tree. So I did that. It finally finished and I rebooted again which is when drive7 as well drive 8 and 10 are showing as unmountable. Instead of continuing down the road I have been I thought it was probably time to ask for help to see if you guys see anything in the syslog that is pointing to larger problems than just my old sata card corrupting some drives. Any help is appreciated before I throw this thing in the bin and move over to drive pools on windows (I kid, I kid). All of my non-replaceable items have been backed up at this point to other machines (pictures etc) and I just have media (movies/tv etc) that is replaceable if need be. Screenshot also attached. What makes me think its still a hardware (non drive) related issue is I am seeing these in the syslog on the brand new drive4: Aug 4 22:43:24 Hog kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 18330 does not match to the expected one 3 Aug 4 22:43:24 Hog kernel: REISERFS error (device md4): vs-5150 search_by_key: invalid format found in block 484016440. Fsck? Aug 4 22:43:24 Hog kernel: REISERFS error (device md4): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [21144 22288 0x0 SD] Maybe parity rebuilding is just rebuilding corrupted files or something? hog-syslog-20150804-2232.zip

I am currently rebuilding parity and only have 1.5 hours left. In the meantime, I thought I would brag about my new system. Before I was running anywhere from 70-100% cpu load depending on if the server was sitting idle. Memory (2gb) was around 60% when idle and 100% when doing anything of note. Check out this screenshot of the new system.

Rob, thanks for all of the help. So, I figured a few things out that may be helpful to others. I actually turned IMMU and all virt settings back on without issues. The problem did end up being both sata add-on cards in combination with virt on. On the new Mobo ( GA-Z97X-UD5H-BK) with the i7-4790k Devils Canyon CPU, my old PCI sata cards with cause these hangs every single time and sometimes system crashes. I tried both cards independently while only hooking up one drive and would still get the issues. Since these cards are so old and only support 3.0Gbs it was probably time for an upgrade anyway. Old sata add-on cards causing the issue: SUPERMICRO AOC-SAT2-MV8 64-bit PCI-X133MHz SATA II (3.0Gb/s) Controller Card New cards that work great out of the box: SUPERMICRO AOC-SAS2LP-MV8 PCI-Express 2.0 x8 SATA / SAS 8-Port Controller Card I think all my frustration came from the following scenario: With virt disabled, old cards worked but I still saw those reiserfs mount errors which made me think the cards were still bad. I should have paid closer attention to the logs and put two and two together. Old cards do work fine if you disable virt (as per your post in the defect/bug forum). Links to parts in question: Motherboard: http://www.newegg.com/Product/Product.aspx?Item=N82E16813128722&cm_re=ga-z97x-ud5h-bk-_-13-128-722-_-Product CPU: http://www.newegg.com/Product/Product.aspx?Item=N82E16819117369&cm_re=BX80646I74790K_i7-4790K-_-19-117-369-_-Product Old Sata add-on cards not working with virt: http://www.newegg.com/Product/Product.aspx?Item=N82E16815121009 New Sata add-on cards working with virt: http://www.newegg.com/Product/Product.aspx?Item=N82E16816101792

Yeah, the plan is to rebuild parity after I am done with all of this.

I think I figured it out..... For some reason, the journal parameter on the reiserfs drives became toast on the unmountable drives. To fix this, I run the following: # reiserfsck --check /dev/sdh1 //sdh1 is an example. Use the right one scxx for your drive that you see in the menu. reiserfs_open_journal: journal parameters from the superblock does not match to the journal headers ones. It looks like that you created your fs with old reiserfsprogs. Journal header is fixed. I hope my two days of frustration helps people in the future.... not sure how this happened to so many drive.

Yeah, so I give up officially. Re-installed original mobo, cpu, ram and same errors. Tried new sata cards, three motherboards, new cables, with same result.

Oh man... I really am in upgrade hell. I had a good quad core AMD board laying around that I decided to try out. The first couple of boots I was seeing missing disks (2 of them) so I rechecked all the cables, and rebooted. Boot happened fine, bios on cards saw all drives and unraid started. However, even with a different board/cpu I am now seeing the exact same unmountable drives as when I was using the new Z97 motherboard. I have no clue.

Just upgraded to 6.1-rc2 with same unmountable drives. 6.1-rc2 log attached. hog-syslog-20150731-1607.zip

Installed a new SATA card today with same results. Guys, I am really at a loss here. Could it be the motherboard? -- gs

Also booted into Ubuntu and the same drives can not be mounted which rules out UNRaid itself as having a problem.

Upgraded bios to latest version with same results. I am crying today.

And just for completeness sake, the MOBO in question is: GA-Z97X-UD5H-BK running BIOS F6 http://www.gigabyte.com/products/product-page.aspx?pid=4978#ov

Thanks for the help. I did disable IOMMU and the boot was much fast (no 30 second delay) but the drives are still showing as unmountable. There are some bios updates so I may try that as well. I have attached a new syslog with IOMMU turned off. Excerpt showing no hang: ---------- Jul 31 18:16:17 Hog emhttp: shcmd (51): mkdir -p /mnt/disk10 Jul 31 18:16:17 Hog kernel: REISERFS warning (device md9): sh-2022 reiserfs_fill_super: unable to initialize journal space Jul 31 18:16:17 Hog emhttp: shcmd (52): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md10 /mnt/disk10 |& logger Jul 31 18:16:17 Hog kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal Jul 31 18:16:17 Hog kernel: REISERFS (device md10): using ordered data mode Jul 31 18:16:17 Hog kernel: reiserfs: using flush barriers Jul 31 18:16:19 Hog kernel: REISERFS warning (device md10): sh-462 check_advise_trans_params: bad transaction max size (4294967295). FSCK? Jul 31 18:16:19 Hog logger: mount: wrong fs type, bad option, bad superblock on /dev/md10, Jul 31 18:16:19 Hog logger: missing codepage or helper program, or other error Jul 31 18:16:19 Hog logger: In some cases useful info is found in syslog - try Jul 31 18:16:19 Hog logger: dmesg | tail or so Jul 31 18:16:19 Hog logger: Jul 31 18:16:19 Hog emhttp: shcmd: shcmd (52): exit status: 32 Jul 31 18:16:19 Hog emhttp: mount error: No file system (32) Jul 31 18:16:19 Hog emhttp: shcmd (53): rmdir /mnt/disk10 Jul 31 18:16:19 Hog kernel: REISERFS warning (device md10): sh-2022 reiserfs_fill_super: unable to initialize journal space Jul 31 18:16:19 Hog emhttp: shcmd (54): mkdir -p /mnt/disk11 Jul 31 18:16:19 Hog emhttp: shcmd (55): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md11 /mnt/disk11 |& logger Jul 31 18:16:19 Hog kernel: XFS (md11): Mounting V5 Filesystem Jul 31 18:16:19 Hog kernel: XFS (md11): Ending clean mount Jul 31 18:16:19 Hog emhttp: shcmd (56): xfs_growfs /mnt/disk11 |& logger Jul 31 18:16:19 Hog logger: meta-data=/dev/md11 isize=512 agcount=4, agsize=244188659 blks Jul 31 18:16:19 Hog logger: = sectsz=512 attr=2, projid32bit=1 Jul 31 18:16:19 Hog logger: = crc=1 finobt=1 Jul 31 18:16:19 Hog logger: data = bsize=4096 blocks=976754633, imaxpct=5 Jul 31 18:16:19 Hog logger: = sunit=0 swidth=0 blks Jul 31 18:16:19 Hog logger: naming =version 2 bsize=4096 ascii-ci=0 ftype=1 Jul 31 18:16:19 Hog logger: log =internal bsize=4096 blocks=476930, version=2 Jul 31 18:16:19 Hog logger: = sectsz=512 sunit=0 blks, lazy-count=1 Jul 31 18:16:19 Hog logger: realtime =none extsz=4096 blocks=0, rtextents=0 Jul 31 18:16:19 Hog emhttp: shcmd (57): mkdir -p /mnt/disk12 Jul 31 18:16:19 Hog emhttp: shcmd (58): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md12 /mnt/disk12 |& logger Jul 31 18:16:19 Hog kernel: REISERFS (device md12): found reiserfs format "3.6" with standard journal Jul 31 18:16:19 Hog kernel: REISERFS (device md12): using ordered data mode Jul 31 18:16:19 Hog kernel: reiserfs: using flush barriers Jul 31 18:16:19 Hog kernel: REISERFS warning (device md12): sh-462 check_advise_trans_params: bad transaction max size (4294967295). FSCK? Jul 31 18:16:19 Hog logger: mount: wrong fs type, bad option, bad superblock on /dev/md12, Jul 31 18:16:19 Hog logger: missing codepage or helper program, or other error Jul 31 18:16:19 Hog logger: In some cases useful info is found in syslog - try Jul 31 18:16:19 Hog logger: dmesg | tail or so Jul 31 18:16:19 Hog logger: Jul 31 18:16:19 Hog emhttp: shcmd: shcmd (58): exit status: 32 Jul 31 18:16:19 Hog emhttp: mount error: No file system (32) Jul 31 18:16:19 Hog emhttp: shcmd (59): rmdir /mnt/disk12 ----------------------- hog-syslog-20150731-1820.zip

Here are some relevant messages from the log: Jul 30 23:37:00 Hog emhttp: shcmd (170): mkdir -p /mnt/disk6 Jul 30 23:37:00 Hog emhttp: shcmd (171): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md6 /mnt/disk6 |& logger Jul 30 23:37:00 Hog kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal Jul 30 23:37:00 Hog kernel: REISERFS (device md6): using ordered data mode Jul 30 23:37:00 Hog kernel: reiserfs: using flush barriers Jul 30 23:37:00 Hog kernel: REISERFS warning (device md6): sh-462 check_advise_trans_params: bad transaction max size (4294967295). FSCK? Jul 30 23:37:00 Hog kernel: REISERFS warning (device md6): sh-2022 reiserfs_fill_super: unable to initialize journal space Jul 30 23:37:00 Hog logger: mount: wrong fs type, bad option, bad superblock on /dev/md6, Jul 30 23:37:00 Hog logger: missing codepage or helper program, or other error Jul 30 23:37:00 Hog logger: In some cases useful info is found in syslog - try Jul 30 23:37:00 Hog logger: dmesg | tail or so Jul 30 23:37:00 Hog logger: Jul 30 23:37:00 Hog emhttp: shcmd: shcmd (171): exit status: 32 Jul 30 23:37:00 Hog emhttp: mount error: No file system (32) Jul 30 23:37:00 Hog emhttp: shcmd (172): rmdir /mnt/disk6 Jul 30 23:37:00 Hog emhttp: shcmd (173): mkdir -p /mnt/disk7 Jul 30 23:37:00 Hog emhttp: shcmd (174): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md7 /mnt/disk7 |& logger Jul 30 23:37:00 Hog kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal Jul 30 23:37:00 Hog kernel: REISERFS (device md7): using ordered data mode Jul 30 23:37:00 Hog kernel: reiserfs: using flush barriers Jul 30 23:37:00 Hog kernel: REISERFS warning (device md7): sh-462 check_advise_trans_params: bad transaction max size (4294967295). FSCK? Jul 30 23:37:00 Hog kernel: REISERFS warning (device md7): sh-2022 reiserfs_fill_super: unable to initialize journal space Jul 30 23:37:00 Hog logger: mount: wrong fs type, bad option, bad superblock on /dev/md7, Jul 30 23:37:00 Hog logger: missing codepage or helper program, or other error Jul 30 23:37:00 Hog logger: In some cases useful info is found in syslog - try Jul 30 23:37:00 Hog logger: dmesg | tail or so Jul 30 23:37:00 Hog logger: Jul 30 23:37:00 Hog emhttp: shcmd: shcmd (174): exit status: 32 Jul 30 23:37:00 Hog emhttp: mount error: No file system (32) Jul 30 23:37:00 Hog emhttp: shcmd (175): rmdir /mnt/disk7 Jul 30 23:37:00 Hog emhttp: shcmd (176): mkdir -p /mnt/disk8 Jul 30 23:37:00 Hog emhttp: shcmd (177): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md8 /mnt/disk8 |& logger Jul 30 23:37:00 Hog kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal Jul 30 23:37:00 Hog kernel: REISERFS (device md8): using ordered data mode Jul 30 23:37:00 Hog kernel: reiserfs: using flush barriers Jul 30 23:37:00 Hog kernel: REISERFS warning (device md8): sh-462 check_advise_trans_params: bad transaction max size (4294967295). FSCK? Jul 30 23:37:00 Hog logger: mount: wrong fs type, bad option, bad superblock on /dev/md8, Jul 30 23:37:00 Hog logger: missing codepage or helper program, or other error Jul 30 23:37:00 Hog logger: In some cases useful info is found in syslog - try Jul 30 23:37:00 Hog logger: dmesg | tail or so Jul 30 23:37:00 Hog logger: Jul 30 23:37:00 Hog emhttp: shcmd: shcmd (177): exit status: 32 Jul 30 23:37:00 Hog emhttp: mount error: No file system (32) Jul 30 23:37:00 Hog emhttp: shcmd (178): rmdir /mnt/disk8

Hello all: I built my system 6 years ago and some of my drives have been in service since day one. I recently upgraded the mobo etc in order to run docker containers better but when powering on the system half of the array is unmountable. It sees the drives and they are green. I have two 8 port sata add-on cards so I my guess is one of them got fried somehow. I went ahead and ordered a new one but thought I would get a sanity check from the log to see if you folks things this is indeed the case. A lot of read errors on the unmountable drives so I assume all 7 drives didn't go bad and it must be the add-on card. syslog attached. hog-syslog-20150730-2342.zip