April 19, 201412 yr my unraid server had a drive failure (disk4) and i am now in the process of pre-clearing a new 4 TB drive to replace it. while running the pre-clear, i noticed that i was getting "input/output errors" on to my cache drive (on the syslog). I have a hot-swappable case, so i removed the cache drive and re-inserted it (while the array was active) and suddenly started getting file-system errors for all the mounted shares. I then restarted my array altogether. after restart, everything seemed to work. the cache drive was accessible again. then i proceeded to activate the mover, to see if it could move things out. it doesn't look like things are moving due to 'rsync errors' and it is saying something about no space left in the device. i have posted the full syslog since the restart. can someone tell me what is happening? do i need to replace my cache drive? or is there something else going on. i am getting an error now saying that my upload folder is full on this forum. i've posted the full syslog on pastebin. http://pastebin.com/bRW6Gp7C thank you so much!
April 19, 201412 yr The hardware may be hot swappable, but unRAID is not. Do not pull any array drives or the cache while the array is running. Stop the the array first, then pull the drives. The server can be running but the array must be stopped. Attach or post screenshots of unRAID Main, Shares->tvshows, and Settings->Share Settings.
April 19, 201412 yr Author I can write to the /mnt/user0 folder by copying a file from a remote location. I'm still not sure what is going on. Just so you know, the reason that there is a single red-ball in the array is the disk4 which has failed. I swapped it out for a fresh drive which I am pre-clearing, but the array still shows the old drive. Could this be the problem?
April 19, 201412 yr I can write to the /mnt/user0 folder by copying a file from a remote location. I'm still not sure what is going on. Just so you know, the reason that there is a single red-ball in the array is the disk4 which has failed. I swapped it out for a fresh drive which I am pre-clearing, but the array still shows the old drive. Could this be the problem? No, this is a different problem.
April 19, 201412 yr The split level is too low for tvshows. Split level has precedence over allocation method. What is the split level for movies?
April 19, 201412 yr Author It's the same for movies. Should it be set differently? What split level would you recommend? Thanks so much dgaschk! Sent from my iPhone using Tapatalk
April 19, 201412 yr Author I should also mention that both drives that have recently given me problems are SSHD (Solid State Hybrid Drives). It seems weird because I purchased both these drives at the same time -- one is a 2 TB Seagate SSHD (this is the one that is showing up as error on the array) and the other is a 1 TB Seagate SSHD (the cache drive). Any thoughts?
April 20, 201412 yr 2 for movies. Using 2 for tvshows will keep each season together on a disk but you'll need to move The Daily Show with Jon Stewart/Season 19 or NOVA/Season 41 to a disk with more space. And you will have to manually manage when a disk becomes full with only a partial season (like whats happening now) by moving the partial season to a disk with more space. Using 3 for tvshows allows seasons to split and you don't have to manually move anything. Keeping seasons together allows easier inventory and makes it easier to know what you've lost if a disk is not recoverable but it's more work occasionally. The Min-free-space needs to be at greater than the size of the largest file that you intend to write. Blu-ray iso's are up to 40GB so I use 50GB and then top off the disks manually.
May 19, 201412 yr Author Hi, We dealt with this issue some time ago and since then my entire server crashed and I am now running it on "SAFE" mode without my plugins running. I noticed, though, now when the mover starts to work, it fails. It looks similar to the error messages I am getting now. May 14 03:51:40 Tower logger: moving tvshows/ May 14 03:51:40 Tower logger: ./tvshows/NOVA/Season 41/NOVA - S41E17 - Inside Animal Minds Bird Genius.mkv May 14 03:51:40 Tower logger: .d..t...... ./ May 14 03:51:40 Tower logger: .d..t...... tvshows/NOVA/ May 14 03:51:40 Tower logger: >f.stpog... tvshows/NOVA/Season 41/NOVA - S41E17 - Inside Animal Minds Bird Genius.mkv May 14 03:51:40 Tower shfs/user0: shfs_write: write: (28) No space left on device May 14 03:51:40 Tower logger: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) May 14 03:51:40 Tower logger: rsync: write failed on "/mnt/user0/tvshows/NOVA/Season 41/NOVA - S41E17 - Inside Animal Minds Bird Genius.mkv": No space left on device (28) May 14 03:51:40 Tower logger: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] May 14 03:51:40 Tower logger: rsync: connection unexpectedly closed (34 bytes received so far) [sender] May 14 03:51:40 Tower logger: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7] May 14 03:51:40 Tower logger: ./tvshows/NOVA/Season 41/NOVA - S41E17 - Inside Animal Minds Bird Genius.nfo May 14 03:51:40 Tower logger: .d..t...... ./ May 14 03:51:40 Tower logger: .d..t...... tvshows/NOVA/ May 14 03:51:40 Tower logger: >f.stpog... tvshows/NOVA/Season 41/NOVA - S41E17 - Inside Animal Minds Bird Genius.nfo May 14 03:51:40 Tower shfs/user0: shfs_write: write: (28) No space left on device May 14 03:51:40 Tower logger: rsync: write failed on "/mnt/user0/tvshows/NOVA/Season 41/NOVA - S41E17 - Inside Animal Minds Bird Genius.nfo": No space left on device (28) May 14 03:51:40 Tower logger: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] May 14 03:51:40 Tower logger: rsync: connection unexpectedly closed (35 bytes received so far) [sender] May 14 03:51:40 Tower logger: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7] May 14 03:51:40 Tower logger: ./tvshows/NOVA/Season 41/NOVA - S41E16 - Wild Predator Invasion-thumb.jpg May 14 03:51:40 Tower logger: .d..t...... ./ May 14 03:51:40 Tower logger: .d..t...... tvshows/NOVA/ May 14 03:51:40 Tower logger: >f.stpog... tvshows/NOVA/Season 41/NOVA - S41E16 - Wild Predator Invasion-thumb.jpg May 14 03:51:40 Tower shfs/user0: shfs_write: write: (28) No space left on device May 14 03:51:40 Tower logger: rsync: write failed on "/mnt/user0/tvshows/NOVA/Season 41/NOVA - S41E16 - Wild Predator Invasion-t humb.jpg": No space left on device (28) May 14 03:51:40 Tower logger: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] May 14 03:51:41 Tower logger: rsync: connection unexpectedly closed (35 bytes received so far) [sender] May 14 03:51:41 Tower logger: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7] May 14 03:51:41 Tower logger: ./tvshows/NOVA/Season 41/NOVA - S41E18 - Inside Animal Minds Dogs & Super Senses.mkv May 14 03:51:41 Tower logger: .d..t...... ./ May 14 03:51:41 Tower logger: .d..t...... tvshows/NOVA/ Don't know what's going on. After our last discussion (dgaschk), I changed the split level to =3 for tvshows, and 2 for movies. Do I have to do something else after I change it. What's weird is that if I run rsync from my cache drive: rsync -avzhr /mnt/cache/tvshows /mnt/user0/tvshows I am successfully able to copy the movies/tv shows off my cache drive. But the mover is not successful. What could be going on? Here are my settings --> share settings: Here are my shares --> tv shows settings Here is my main page (disk 2 appears to be full)
May 19, 201412 yr Author Thanks dgaschk, I did this before and downloaded the rmattrs script and corrected some of the problems I was getting in the syslog. I'm not sure what happened, but it looks like the mover is working again. I copied a NOVA episode (one that I had previously had problems copying with the mover) on to the cache drive and invoked the mover and it ran! Thanks again for your help... I will see if it continues to work. As always, I greatly appreciate your assistance with everything. rwickra
Archived
This topic is now archived and is closed to further replies.