You are not logged in.
Pages: 1
I have just switched to Arch and it is going great except for a couple of issues. I cannot unrar any files. I have installed unrar and xarchiver. I have also tried file-roller. FR says that several parts have failed a crc check, but that applies even to files that I had successfully unrar'ed b4 the switch to Arch. It seems to me the crc check invoked by the programs must be wrong.
So I am stumped why I cannot unrar.
BTW, I much prefer a gui for this task.
[Update] I am on amd-64. It seems there is a known issue with unrar on 64bit systems. So I thought I would install wine. No 64 bit exists. Virtualbox is only in AUR.
Decided to be coward and install i686 instead.
Last edited by Ozdemon (2010-04-18 06:19:08)
Offline
I'm on x86_64, I never had any issue with unrar. I use it in a terminal (unrar e or unrar x) and it always works flawlessly.
You didn't give any errors, nothing. We can't really help you ![]()
Install i686 instead of x86_64 will decrease the performance of your PC, it's a pity.
Offline
I also had some problems with unrar but only if I use the gui ("extract here" option in nautilus), some files won't unrar, segmentation fault etc. If I use the terminal (unrar e somefile.rar) the same achive will extract fine. That's not the case with all RARs but it happened to me a few times. Maybe a bug in nautilus?
@Ozdemon
What happens when you try to unrar the file in the CLI?
Offline
Urfaust,
As the files I need to unrar are many folders deep, the idea of using the cli every time I need to do it doesn't appeal. So when I could not get either file roller or xarchiver to work, and could not install a 64 bit version of wine, and would need to use AUR to install 64-bit virtualbox, it reminded me why I dropped 64 bit Ubuntu a year or so ago. There are just too many extra issues for too little benefit for the type of computing I do. Others would have a different perspective.
So I have gone back to 32 bit, and file roller now works. ![]()
Offline
@Ozdemon:
7zip might have been the answer under arch x86_64 but since you went back to 32 bit you can not crosscheck anymore ![]()
My archlinux x86_64 host:
AMD E350 (2x1.6GHz) / 8GB DDR3 RAM / GeForce 9500GT (passive) / Arch running from 16GB USB Stick
Offline
@Ozdemon:
7zip might have been the answer under arch x86_64 but since you went back to 32 bit you can not crosscheck anymore
Well I spoke too soon. ![]()
Having installed i686, file roller worked once.
I get the crc error with xarchiver, file roller, 7zip under wine and unrar e using the cli.
As an example, with a file that I had previously extracted before installing Arch, the output from file roller is:
{file}.avi : packed data CRC failed in volume /home/tpb/Desktop/{file name}.part01.rar
{file}.avi : packed data CRC failed in volume /home/tpb/Desktop/{file name}.part08.rar
Not all the parts fail the crc check, about a third do.
This is all happening on a new pc with a fresh arch install. Does this suggest a faulty part, i.e. motherboard, cpu (you can see how desperate for an explanation I am getting).
Last edited by Ozdemon (2010-04-19 09:58:39)
Offline
I've never had CRC issues with rar. You can try using p7zip, which is the 7zip command line on Linux ![]()
Offline
bad crc means faulty downloads or faulty harddisk in most cases... you might want to check your hardware
He hoped and prayed that there wasn't an afterlife. Then he realized there was a contradiction involved here and merely hoped that there wasn't an afterlife.
Douglas Adams
Offline
bad crc means faulty downloads or faulty harddisk in most cases... you might want to check your hardware
Errr...you were right. It turned out to be bad RAM. A lot of heartache to find the source of the problem though. Unfortunately, I am not the only one with this faulty RAM. http://gskill.us/forum/showthread.php?t=4952
All fine now with replacement parts.
Offline
Pages: 1