gatorguy

I'm mostly done with converting the data drives to xfs. However, last night the server locked up again. Also, my router locked up again. Can you tell by the diagnostics zip if the router locking up is causing the server to lock up? In the syslog.txt which is part of the New diagnostics.zip from this morning (attached below), there are a lot of Ethernet adapter reset unexpectedly. Then around 6:50am, there's something to do with Ethernet saying "detected hardware unit hang". I'm not sure what all that means, but that's why I'm asking if somehow when my router locks up if it's causing the server to lock up also. Any thoughts? diagnostics-20171002-0744.zip

Great, thanks! I'll start converting tonight then. No hard drive purchasing required!

So to be clear, the destination drive doesn't necessarily have to be bigger than the source drive as long as there's more free space on the destination drive than data on the stored drive. Is that correct? For example, I have one 8TB WD Purple drive in my array that I use exclusively for writing security camera footage to. It currently only has 340GB of data. My other data drives in the array are 3TB and 4TB drives and I have an empty 4TB drive. I wouldn't need to buy another 8TB drive to do all the converting, right? In other words, I don't HAVE to copy from 8TB to another 8TB even though there's only 340GB of data on that drive, right? I can just start copying data amounts from large to small as long as the empty, xfs formatted destination disk has more free space than data on the source disk. Hopefully I made sense with those words.

Wow, so I just was reading https://forums.lime-technology.com/topic/35815-re-format-xfs-on-replacement-drive-convert-from-rfs-to-xfs-discussion-only/ and see it's quite the process to convert from reiserfs to xfs. It'll take me a couple of weeks probably. I need to see if I have a spare drive to even do this. What will happen if the server freezes in the middle of a disk copy? I guess I'll have to cross that bridge when I come to it.

Thanks for the reply! I'll read up on the conversion process and have it done by the weekend, at the latest. If you think that could be the cause of the server freezing, I'll do that ASAP and report back with a new diagnostic.zip if the issue repeats.

Dear Smart People, I've been running unRAID for 5 years or so and have a server pro license. I upgraded my hardware several months ago and all has been fine. It may be coincidence, but since I upgraded to 6.3.5, I've been having intermittent server lock ups. Meaning the UI isn't accessible and my Windows 10 Pro VM isn't accessible and I cannot telnet into the server. The most recent occurrence was last night. I typed "diagnostics" from the command prompt on the console while the UI was locked up and have attached the file here. I'm using the Windows 10 VM primarily for running Blue Iris for recording IP cams, and when the server locks up, I don't have any ability to record video. The server typically runs about 25% CPU usage due to the VM and Blue Iris. I've had an (I think) unrelated issue of my router locking up recently. That couldn't be related, could it? Can anybody tell me what direction I should start looking to prevent the server from locking up? Thanks in advance for your time and help. diagnostics-20170927-1715.zip

I agree fully. Good advice. I currently have a 4TB HGST as my parity with a second 4TB HGST sitting there pre-cleared and ready to be installed in an emergency (failure of parity or data drive). I have 5-3TB data drives. If I went to 8TB parity, I'd probably buy 2 and do the same setup. I had this setup before the dual parity stuff came out. I need to read up on that some more also.

Just went to this link and it's $259 today! Amazon is $311 today. That's a big difference! I'm thinking of picking one up to make my parity drive. Any thoughts on that?

I followed the instructions in the following thread to resolve my issue! https://lime-technology.com/forum/index.php?topic=52864.0

What did you end up finding out? I'm in about the exact same boat right now. Background: I've had this unRAID box running 3 years or so with no issue. I just recently did the latest update to 6.2.4, I think it was from 6.2.2, I think. No hardware has changed in many, many months.

After reading another hundred forum posts, I changed my sata configuration in my BIOS to AHCI. When I rebooted unRAID, it said the cache drive wasn't formatted. I let it format and then copied all the files back to the cache drive which I had backed up on my laptop. All is well now. Drive size and free space are reporting correctly. By the way, the cache drive was reporting as a hda before the BIOS change and it's sdf now. All the other drives were reporting as sdX before.

Here's the deal: I'm running 5.0.6 and had a 120gb ssd cache drive working perfectly for a year plus. I bought a 240gb ssd as an upgrade. I used a StarTech hard drive duplicator to copy the data from the 120gb to the 240gb drive. Once I installed the 240gb drive in the unRAID server, unRAID sees the drive as 240gb, but reports the free space as if it's the 120gb drive. I've searched all kinds of search strings trying to find an answer on my own. I'm guessing I need to just reformat the 240gb drive and simply copy the files over instead of trying to do a cloning with the drive duplicator dock, BUT I can't even figure out how to format the dad gum cache drive. I'd appreciate any help from the guys/gals in the know! Thanks, and sorry for being a dunce.

As an update, I replaced the drive in question with a WD Red 3TB. The new drive is staying spun down like it is supposed to, oh yeah! I still don't know the cause of the old 2TB staying spun up, but I can only imagine it has something to do with the drive itself. Either way, it's beyond me.

I bought another new cable and installed on disk 2. I attached my syslog after the new cable just in case somebody sees something new. At this point, I'm assuming it's something with the drive and I'll just replace it when it dies. I've stressed too much over the damn thing. Thanks to those who gave suggestions. syslog-2013-08-03.zip

The log posted doesn't contain the original lines I posted earlier in the thread because I rebooted the server several times as I powered down multiple times to try different cable/bus positions before saving the syslog to file. You've given me some good information. If it's a communication error with the drive, maybe there's a problem on the drive's connectors themselves. I will also try a third cable just to see if that helps. I guess the communication error can keep the drive from staying spun down? I appreciate you trying to help out!

I'm asking this question out of ignorance: if one of the add-ons was accessing the drive, would I see the activity while watching a Putty window with the command inotifywait -mr /mnt/disk2? I've had such a window open all day and have seen no activity. When I manually spin down, the drive spins back up within 90 seconds and puts the lines listed above in the syslog.

Thanks for trying to help. Sorry I didn't post the whole log. Here it is along with a SMART report from drive 2. syslog-2013-07-21.zip smart.txt

Ok, I have tried a few different things: Traded SATA cables with another drive. Disk 2 still would not stay spun down. Traded SATA ports on the motherboard with another drive. Disk 2 still would not stay spun down. (notice the error is now ata4) Replaced SATA cable and left Disk 2 on ata4 and still would not stay spun down. Disk 2 is starting to become a common denominator... Finally connected Disk 2 via PCI-e SAS RAID Controller which has its own cable. Took almost 10 minutes this time, but drive spun up. See log below. BTW, had inotifywait -mr /mnt/disk2 running and had no activity when the disk spun up. Syslog with New cable connected to ata4 on motherboard: Jul 20 14:03:33 GatorguyMedia emhttp: Spinning down all drives... (Other emhttp) Jul 20 14:03:33 GatorguyMedia kernel: mdcmd (19): spindown 0 (Routine) Jul 20 14:03:34 GatorguyMedia kernel: mdcmd (20): spindown 1 (Routine) Jul 20 14:03:35 GatorguyMedia kernel: mdcmd (21): spindown 2 (Routine) Jul 20 14:03:36 GatorguyMedia kernel: mdcmd (22): spindown 3 (Routine) Jul 20 14:03:37 GatorguyMedia emhttp: shcmd (44): /usr/sbin/hdparm -y /dev/hda $stuff$> /dev/null (Drive related) Jul 20 14:05:15 GatorguyMedia kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x10202 action 0xe frozen (Errors) Jul 20 14:05:15 GatorguyMedia kernel: ata4: irq_stat 0x00400000, PHY RDY changed (Drive related) Jul 20 14:05:15 GatorguyMedia kernel: ata4: SError: { RecovComm Persist PHYRdyChg } (Errors) Jul 20 14:05:15 GatorguyMedia kernel: ata4: hard resetting link (Minor Issues) Jul 20 14:05:25 GatorguyMedia kernel: ata4: softreset failed (1st FIS failed) (Minor Issues) Jul 20 14:05:25 GatorguyMedia kernel: ata4: hard resetting link (Minor Issues) Jul 20 14:05:26 GatorguyMedia kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Jul 20 14:05:26 GatorguyMedia kernel: ata4.00: configured for UDMA/133 (Drive related) Jul 20 14:05:26 GatorguyMedia kernel: ata4: EH complete (Drive related) Syslog when connected to PCI-e controller: Jul 20 15:03:58 GatorguyMedia emhttp: Spinning down all drives... (Other emhttp) Jul 20 15:03:58 GatorguyMedia kernel: mdcmd (19): spindown 0 (Routine) Jul 20 15:03:59 GatorguyMedia kernel: mdcmd (20): spindown 1 (Routine) Jul 20 15:04:00 GatorguyMedia kernel: mdcmd (21): spindown 2 (Routine) Jul 20 15:04:01 GatorguyMedia kernel: mdcmd (22): spindown 3 (Routine) Jul 20 15:04:02 GatorguyMedia emhttp: shcmd (44): /usr/sbin/hdparm -y /dev/hda $stuff$> /dev/null (Drive related) Jul 20 15:13:44 GatorguyMedia kernel: mvsas 0000:02:00.0: Phy2 : No sig fis (Drive related) Jul 20 15:13:49 GatorguyMedia kernel: mvsas 0000:02:00.0: Phy2 : No sig fis (Drive related) Jul 20 15:13:54 GatorguyMedia kernel: sas: sas_form_port: phy2 belongs to port0 already(1)! (Drive related) So is this a drive issue of some sort?

I did as you suggested and the drive spun up as it has been doing. I copied the syslog and you can see the network link go down, the same messages I posted above and then the network link coming up after I plugged the cable in. Do those error messages have anything to do with addons? Syslog: Jul 20 12:20:27 GatorguyMedia emhttp: Spinning down all drives... (Other emhttp) Jul 20 12:20:27 GatorguyMedia kernel: mdcmd (47): spindown 0 (Routine) Jul 20 12:20:28 GatorguyMedia kernel: mdcmd (48): spindown 1 (Routine) Jul 20 12:20:29 GatorguyMedia kernel: mdcmd (49): spindown 2 (Routine) Jul 20 12:20:29 GatorguyMedia kernel: mdcmd (50): spindown 3 (Routine) Jul 20 12:20:30 GatorguyMedia emhttp: shcmd (51): /usr/sbin/hdparm -y /dev/hda $stuff$> /dev/null (Drive related) Jul 20 12:20:32 GatorguyMedia kernel: r8168: eth0: link down (Network) Jul 20 12:21:56 GatorguyMedia kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen (Errors) Jul 20 12:21:56 GatorguyMedia kernel: ata3: irq_stat 0x00400000, PHY RDY changed (Drive related) Jul 20 12:21:56 GatorguyMedia kernel: ata3: SError: { RecovComm Persist PHYRdyChg 10B8B } (Errors) Jul 20 12:21:56 GatorguyMedia kernel: ata3: hard resetting link (Minor Issues) Jul 20 12:22:06 GatorguyMedia kernel: ata3: softreset failed (1st FIS failed) (Minor Issues) Jul 20 12:22:06 GatorguyMedia kernel: ata3: hard resetting link (Minor Issues) Jul 20 12:22:08 GatorguyMedia kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Jul 20 12:22:08 GatorguyMedia kernel: ata3.00: configured for UDMA/133 (Drive related) Jul 20 12:22:08 GatorguyMedia kernel: ata3: EH complete (Drive related) Jul 20 12:22:30 GatorguyMedia kernel: r8168: eth0: link up (Network)

Thanks for the reply. I'm willing to try anything. My addons are all installed on the cache drive. Only have couchpotato, sabnzbd, sickbeard and twonky. Here comes a dumb question. How can I find out if the drive is spinning when I have the network disconnected? I can hook up a monitor to the unRAID box, but what command would I use to see if the disk is spinning?

I've read a lot of threads before posting, but I have been unable to find an answer. My array has a parity drive, 3 data drives and a cache drive. My disk 2 spins constantly and has been for weeks. If I manually spin down all drives, disk 2 will start back within 30-90 seconds. My unRAID server is approx 1.5 years old. I've tried: inotifywait -mr /mnt/disk2 (saw no activity) lsof /mnt/* (saw only cache activity) sysctl vm.block_dump=1 followed by tail -f /var/log/syslog (saw no read/write activity that I didn't cause myself by accessing a .pdf reads/writes on disk2 don't change in myMAIN view The only thing I see in the syslog that I think may be related is this section which shows me spinning down and then what happens when drive starts back up: Jul 20 10:38:50 GatorguyMedia emhttp: Spinning down all drives... Jul 20 10:38:50 GatorguyMedia kernel: mdcmd (39): spindown 0 Jul 20 10:38:51 GatorguyMedia kernel: mdcmd (40): spindown 1 Jul 20 10:38:52 GatorguyMedia kernel: mdcmd (41): spindown 2 Jul 20 10:38:53 GatorguyMedia kernel: mdcmd (42): spindown 3 Jul 20 10:38:54 GatorguyMedia emhttp: shcmd (49): /usr/sbin/hdparm -y /dev/hda &> /dev/null Jul 20 10:39:16 GatorguyMedia kernel: shfs(31921): dirtied inode 4026531842 (mounts) on proc Jul 20 10:40:36 GatorguyMedia kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x10202 action 0xe frozen Jul 20 10:40:36 GatorguyMedia kernel: ata3: irq_stat 0x00400000, PHY RDY changed Jul 20 10:40:36 GatorguyMedia kernel: ata3: SError: { RecovComm Persist PHYRdyChg } Jul 20 10:40:36 GatorguyMedia kernel: ata3: hard resetting link Jul 20 10:40:46 GatorguyMedia kernel: ata3: softreset failed (1st FIS failed) Jul 20 10:40:46 GatorguyMedia kernel: ata3: hard resetting link Jul 20 10:40:47 GatorguyMedia kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 20 10:40:47 GatorguyMedia kernel: ata3.00: configured for UDMA/133 Jul 20 10:40:47 GatorguyMedia kernel: ata3: EH complete I thought maybe it was a hardware issue. I checked the cable connections last night, but didn't replace a cable. Any other thoughts? I was running 5.0-rc12a until last night when I updated to 5.0-rc16c. The "issue" happens on both versions. Thanks in advance for your help!

Did you ever get this figured out? I'm in the same position at this time.

I'm no expert, but you should be able to "right click" all of the files you want to move in Midnight Commander to select multiple files. They will turn yellow when selected. I'm also having an issue on 5 b14 where the mover doesn't work automatically at night. It works everytime when I start it manually from the settings/share settings page. I'll have to post my error messages sometime.