July 29, 201213 yr Hi all, Anytime the mover script initiates, whether it be scheduled or me pushing the button in unmenu, it starts transferring files and then the system freezes. I am unable to access it via telnet or unmenu. If the cache drive has very little on it, it finishes fine and then freezes. If the cache drive has more on it, it will freeze in the middle of the transfer. The freeze generally seems to happen at the same time after the mover is initiated. I have no other add-on packages running except for what the system comes with, screen and unmenu. At least, there shouldn't be. If there are, I am unaware of it. I did manage to snap a photo with my phone of what it is displaying on the monitor attached to the tower. The system log I created was after a hard shutdown (this is the only way to get a functioning system again). I have attached it but I am not sure it will be of much help, it doesn't display the text that is in the photo. Using an ASUS-IPIBL-LB motherboard out of an HP desktop with 4GB of RAM. My flash drive is a sony microvault, and I am using version 5.0-rc5. I did recently moved the system to this motherboard after an unfortunate incident with a failing power supply that killed my mobo and flash drive. I made sure to put the parity drive and all other drives exactly as they were assigned previously, including the same SATA_# on the new motherboard. Some of the device ID's were swapped. The parity remained sda, but two of the hard drives and the cache drive had new assignments. Parity check reports no errors. I confirmed with a reiserfsck on all disks, including the cache but not the parity drive, that everything was okay. SMART reports are all clean. It survived also 24-hour memtest without incident. I hope i gave enough information to get a sense of whatever the problem is. Thanks! EDIT: I added the telnet tail log. Terminal_Saved_Output.txt
July 29, 201213 yr Use the telnet-tail method to collect a log during a crash: http://lime-technology.com/forum/index.php?topic=9880.0
July 30, 201213 yr I saw the same phenomenon on a friend's machine. It turned out that he hat corrupt file entries on his cache drive - when mover tried to move the files, the machine crashed/hung completely. Try to move away all files from the cache drive, or look into the log and find out which file caused the hang. As we deleted those files from the cache drive, the mover ran without any problem.
Archived
This topic is now archived and is closed to further replies.