sunnyville

Thanks for your reply. I am not too savvy with the command line but will try to get that log file. To answer your questions: I also run PlexServer. That runs flawlessly. All the time. Every day.

Hi there. I need some help. Basically I am running a dicker (unBALANCE) and it will freeze the system. I have attached a log as I believe it might not actually be the locker itself that is at fault. Can you tell me what you see from 11:49 onwards? It's only a few seconds worth of information. Any help would be much appreciated! Log_Information.pdf

I have attached a log file concerning the problem I am always encountering. The relevant Timing is from "11:50 am" onwards. Basically as soon as I click on "Move" in unBALANCE, it throws a ton of errors and the system Freezes. Log_Information.pdf

ok new problem: Whenever I tried to move flies from one disk to the next it would move one or two Folders then fail. It did not matter what Folders I chose, what disk I said I would like to or from. Then I came across a thread here where it said it might be down to .AppleDouble files. So I let BlueHarvest (a mac app for removing said flies) run on the share that contained the files I wanted moved. It completed the task. Then, I hit the move button, and again it locked up the server within seconds. No access. Neither via ssh, telnet, nothing at all. Any ideas?

Ok, I am using this for the first time. I want to free up a disk. I did exactly what the person in the previous post did, it adds the Folders I want to move but then when I click on calculate it "says nothing to do" EDIT: resolved the issue - read through the forum: don't use the entire path! ;-)

Quote from the Plex Website: "Plex Media Server 0.9.12.13 is now available for all users" I used to use iOS Photo Sync. I can't do that with the current version of Plex available via the repository. Could you please add the current version? Thank you!

I have this case and it works very well. There is however very little room between the back end of the drives (Where you plug in the cables) and the Fans. However once you have seated those cables, all is well. My server runs nearly 24/7. It sucks in barely any dust. The case is sturdy and very easy to set up even for people who don't do this on a daily basis. Definitely recommend it!

Just a quick thing I noticed in regards to the dynamix thing: I can only access shares that were created pre-installing-dynamix. When I try to create shares now it will never work. I click on create, and it doesn't get created. At one time a share got created (it appeared under 'shares') but disappeared after a reboot. There is no trace of it on any of the disks.

Alright, thank you!

Hi, I just moved my 27TB Server from an old Computer Case to a 24-Bay server enclosure (Xcase 424s). It is up and running, went relatively smooth. I have never had hot swap caddies before. A quick question: I have a few drives lying around that I would like to eventually add to the server and would like to run SMART tests, but not add them to the unraid cluster yet. Could I theoretically insert a drive WHILE the server is running and run a SMART test or is it advisable to always switch the server off, add drives, switch back on?

Thank you all for your help! It seems as though simply preclearing all disks solved the issue. Tried adding them today, it worked first time!

no UnRaid Gurus willing to help? I am really at a loss here. Willing to do any troubleshooting but just don't know where to start.

So, here is the log, starting at just before I select the new disk till after I have hit "start": syslog.pdf

I am just about to add the log. Can't copy& past so will zip it.

Ok, Disabled plex and crashplan, just for the sake of it, rebooted the server, added 1 drive, no luck. Nothing happens. Went into the terminal, typed in sgdisk, got this: root@Tower:~# sgdisk Usage: sgdisk [-A|--attributes list|[partnum:show|or|nand|xor|=|set|clear|toggle|get[:bitnum|hexbitmask]]] [-a|--set-alignment value] [---backup file] [-c|--change-name partnum:name] [-C|--recompute-chs] [-d|--delete partnum] [-D|--display-alignment] [-e|--move-second-header] [-E|--end-of-largest] [-f|--first-in-largest] [-F|--first-aligned-in-largest] [-g|--mbrtogpt] [-G|--randomize-guids] [-h|--hybrid partnum[:partnum...]] [-i|--info partnum] [-l|--load-backup file] [-L|--list-types] [-m|--gpttombr partnum[:partnum...]] [-n|--new partnum:start:end] [-N|--largest-new partnum] [-o|--clear] [-p|--print] [-P|--pretend] [-r|--transpose partnum:partnum] [-R|--replicate device_filename] [-s|--sort] [-S|--resize-table numparts] [-t|--typecode partnum:{hexcode|GUID}] [-T|--transform-bsd partnum] [-u|--partition-guid partnum:guid] [-U|--disk-guid guid] [-v|--verify] [-V|--version] [-z|--zap] [-Z|--zap-all] [-?|--help] [--usage] [OPTION...] <device> root@Tower:~# no complaining of any sort about libraries, at least as far as I can tell (I am not versed in the intricacies of Linux but I am always eager to learn ;-) )

Thank you very much! I will try that tonight. I Do have Simplefeatures installed as well as plex and crashplan. The disk configuration has not changed, parity drive is installed (and synched). I'll give it a go tonight and see if it is a missing library or something along those lines.

Well I have a problem, but it is not critical. I have three drives that were previously used in my unraid a while back and had been replaced with larger drives. I had them lying around and now want to add them to unraid again as I need more space. 1x1TB, 1x2TB, 2x3TB. These are not pre cleared but have also not failed in the past. I don't mind if my server goes offline for a while to clear drives so I figured I could just add them. I select them when the server has booted (but not started), a blue ball appears next to each, next to the START button it warns me that it will now erase the drives etc, I click ok and START, but nothing happens, it simply reloads the page. The logs also show zero info on what just happened. I can repeat this as many times as I want, nothing happens. I then proceeded to simply try adding one drive, but nothing happened. So my question: Must I preclear the drives in order for them to get accepted by unraid? In the past I never pre cleared (if something were to go wrong, my fault) but all drives I added were completely new. Is the problem that there is data on the disks? Thank you all in advance for any input!

Thank you! Ran rebuild of tree (as it advised this after the filesystem check) Seems to be working again now! I Thought I had lost 2TB of data but all is good now ;-)

what does this mean: /usr/bin/tail -f /var/log/syslog Apr 13 13:57:40 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD] Apr 13 13:57:40 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1 Apr 13 13:57:40 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck? Apr 13 13:57:40 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD] Apr 13 13:57:57 Tower shfs/user: shfs_setxattr: setxattr: user.org.netatalk.supports-eas.IoZKzr /mnt/disk8/Backups (30) Read-only file system Apr 13 13:57:57 Tower afpd[11216]: volume "Backups" does not support Extended Attributes, using ea:ad instead

during the rebuild I had these errors: /usr/bin/tail -f /var/log/syslog Apr 11 17:56:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1 Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck? Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD] Apr 11 17:56:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1 Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck? Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD] Apr 11 17:56:06 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 29541 does not match to the expected one 1 Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-5150 search_by_key: invalid format found in block 423168048. Fsck? Apr 11 17:56:06 Tower kernel: REISERFS error (device md8): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [385809 385817 0x0 SD] Apr 11 17:56:26 Tower emhttp: title not found Apr 11 17:56:27 Tower emhttp: title not found Apr 11 17:56:49 Tower shfs/user: shfs_setxattr: setxattr: user.org.netatalk.supports-eas.CESAHN /mnt/disk8/Backups (30) Read-only file system Apr 11 17:56:49 Tower afpd[24664]: volume "Backups" does not support Extended Attributes, using ea:ad instead

Could it be that my 3TB drive which used to be a parity drive is "recorded" by UNRaid somewhere and thereby does not let me reuse it as a normal drive?

Ok, my 3TB disk which replaced the original 1TB still has its red ball. Here's the thing: If i disable it, it says that it is looking for exactly that disk. If I select that 3TB disk it stays red balled. What am I to do? It doesn't report temperature or anyhting, but if I run a SMART test it says test passed. I can start the array unprotected and mount disk9 (the faulty one) and I can see all my data ist still there (I am thankful for that!) but I don't know how to get unraid to rebuild parity to the 3 TB drive. I want my array protected again!

Ok, I am in trouble! I have a 10 disk array + parity. Parity used to be 3TB, I wanted to expand the file system. I then replaced the parity drive, had it rebuild parity, worked fine. I then replaced a random 1TB drive with the original 3TB drive. The WEBGUI noticed the disk, said "rebuild disk & expand" I clicked yes. It rand for an hour, then said there were disk errors and stopped. I thought maybe it's down to bad cabling, so I powered down the server, checked cabling, turned it back on. Now it said parity valid (!!!!) next to the 3TB disk with a red ball. (I did not click on "start") I then switched it back off, tried unplugged the 3TB drive and plugged back in the 1TB drive (I haven't overwritten it just in case). It came up with a blue ball saying the original drive should be the 3TB one and the new drive is too small. OK so what now? EDIT: Running 5b10

seems like you guys were right. I made no changes to the hardware, simply shut down, rolled back to beta 11, now running a parity check, and even after 2 hours, it is still going without freezing. Before this would take between 2-5 Minutes before the server became unresponsive.

Yes, it is a dreaded loop. I guess I could roll back to 5b11. However will the BLK Issue go away? IF yes then I'll roll back. I can't go all the way back to 4.7 even though that worked a dream for a long long time, because I am now using a lot of 3TB drives.