General Linux Chat and Small Questions v. I broke my Arch Install - Hardware & Software

[QUOTE=Adamhully;45926372]Everything I ever do is shit. Tried installing mint alongside windows 8, it finished installing but I have no options to boot into Linux or any evidence that it exists apart from some new partitions. I don't get it.[/QUOTE] As a general rule, you always install Windows first, then Linux. Linux bootloaders automatically add an option to boot into Windows if it detects it being installed. This is salvagable though, you just need to use the LiveCD/USB to reinstall GRUB again.

I've had Win 8 installed for a few months, I popped the live CD in and then installed mint whilst it was loaded. Picked the "Install alongside windows 8" option. It went through. One thing that did happen though, after it finished installing I chose the "reboot" option and it kinda got stuck on shutting down and my PC never powered off. I pressed Ctrl Alt Del and it said one of the shutdown processes failed so I had to do a cold reboot, maybe that fucked it?

[QUOTE=Adamhully;45926976]I've had Win 8 installed for a few months, I popped the live CD in and then installed mint whilst it was loaded. Picked the "Install alongside windows 8" option. It went through. One thing that did happen though, after it finished installing I chose the "reboot" option and it kinda got stuck on shutting down and my PC never powered off. I pressed Ctrl Alt Del and it said one of the shutdown processes failed so I had to do a cold reboot, maybe that fucked it?[/QUOTE] I assume something went really wrong during the install process. Usually configuring and installing grub is the last thing before it tells you to reboot. It may have been fucked before that point.

If it was really just rebooting, a hard shutdown shouldn't be a huge problem. If it was running some install script and "rebooting" really meant "do some more stuff right before rebooting", then you probably need to start from scratch. Can you at least chroot in?

I think the burn went wrong. There seems to be a 'piece' missing from the burned part of the DVD. [IMG]http://i.imgur.com/KDRG9Xv.jpg[/IMG] I've never seen that before.

Looks fine to me.

Seems fine to me too, however why did you burn a DVD instead of just using a USB? On another topic of my own, related to my previous post, I am now forced to test the viability of establishing a rebuild-everything system to recompile every package back to the point it is now (with the exception of having a true multilib system, and not some broken shit) completely automatic, so I don't have to do shit. I've written two scripts to regenerate my kernel and initramfs again, and I'm currently testing if just copying a world file to a new installation will allow the user to do "emerge -av @world" and pull in tons of new packages with the correct use flags set. Here we go again.

[QUOTE=Adamhully;45927077]I think the burn went wrong. There seems to be a 'piece' missing from the burned part of the DVD. [IMG]http://i.imgur.com/KDRG9Xv.jpg[/IMG] I've never seen that before.[/QUOTE] CD's and DVD's burn "center-out". Whatever you burned used only under half the disc, and the lighter portion is the actual data.

My main laptop broke so I decided to put linux (mint) on this tiny one I had around and tada, it works! It originally had windows 7 but it was slow as shit and complaining about too little memory. This seems to work fine though.

[QUOTE=Demache;45932403]CD's and DVD's burn "center-out". Whatever you burned used only under half the disc, and the lighter portion is the actual data.[/QUOTE] Oh I know about that, I'm talking about that tiny dot that is the same colour of the unburned part where the data has been burned. To my knowledge pieces of the disc shouldn't be skipped like that, it should be a solid full circle on the disc. Also I didn't use USB because I had issues last time, my MoBo doesn't play nice with bootable USB devices.

[QUOTE=Adamhully;45932966]Oh I know about that, I'm talking about that tiny dot that is the same colour of the unburned part where the data has been burned. To my knowledge pieces of the disc shouldn't be skipped like that, it should be a solid full circle on the disc. Also I didn't use USB because I had issues last time, my MoBo doesn't play nice with bootable USB devices.[/QUOTE] Oh now I see it. For some reason I completely missed it. Yeah, that's not supposed to be like that.

Anybody tried [url]http://www.voidlinux.eu//[/url] yet? Reading the description, it sounds kinda nice. Might give it a spin in a VM.

[QUOTE=kaukassus;45939633]Anybody tried [url]http://www.voidlinux.eu//[/url] yet? Reading the description, it sounds kinda nice. Might give it a spin in a VM.[/QUOTE] Once I've finished recompiling my Gentoo/Funtoo installation, I'll slam that in a VM and see how well it works. I'm already using both runit and source+binary package managers, so there's not much in the package for me to switch to be honest. However, reporting back about the [b]glibc+gcc multilib[/b] issue, it turns out I couldn't find any way to make my system work. Hence, I backed up my /etc/portage directory, my /etc/fstab, and my /var/lib/portage/world file. I then mkfs.ext4'd the partition from within Ubuntu, extracted a new stage3 + portage-snapshot, then extracted my backup in there as well. It took a slight bit of work (not much), but most of it was just removing packages from the world file that either I had no idea why the fuck I installed, or were not present in the default repository. After that, emerge -avNuD @world, and it merged a bit over 800 packages. Still going though, about 30 packages left. I will still be looking into the issue to determine what could've possibly fixed my problem, but I'm partially stumbed on the issue at the moment. Anyway, I did a reinstall, and it works. [editline]10th September 2014[/editline] This is yet another good time to remind the fuck out of everyone to have a seperate home partition in case your shit gets fucked. However, I am so fucking happy that it is really just a matter of copying use flags and a world file and your packages get pulled in easily.

I can't think of any reason not to have a separate home partition.

I just solved a problem with pacman -S --force today. Let's hope it won't bite me in the ass. The problem was loads of files being disowned by loads of packages. It refused to install the packages because it wouldn't overwrite the files, which were corrupted. With --force it gladly complied.

Moving the original files to .bak files would have probably been safer. Then again, I --force'd pacman with a broken package database, so.

[QUOTE=nikomo;45940549]Moving the original files to .bak files would have probably been safer. Then again, I --force'd pacman with a broken package database, so.[/QUOTE] I couldn't start the login manager to copy and paste the lines and edit it with a decent text editor (sublime)

[QUOTE=Darkwater124;45940156]I can't think of any reason not to have a separate home partition.[/QUOTE] For me, it's not needing to think about space allocation. What does a separate home partition help with? What sort of problem would make your root partition unmountable (that would not also affect your home partition)?

[QUOTE=Larikang;45940908]For me, it's not needing to think about space allocation. What does a separate home partition help with? What sort of problem would make your root partition unmountable?[/QUOTE] Filesystem corruption, but that could be the case regardless. However, for me it's a case of safety. Even IF the entire system goes bonkers and dies, and the filesystem corrupts itself to hell, I still have my personal files. I do need to get myself an external drive that I can dump it on though.

[QUOTE=mastersrp;45941252]Filesystem corruption, but that could be the case regardless. However, for me it's a case of safety. Even IF the entire system goes bonkers and dies, and the filesystem corrupts itself to hell, I still have my personal files. I do need to get myself an external drive that I can dump it on though.[/QUOTE] I think that's a pretty big IF. If you're whole fs goes bonkers, why would your home partition's fs be miraculously spared? Personally, I would be much more concerned about complete drive failure, which a separate partition also isn't going to help with. [editline]10th September 2014[/editline] I guess if you do fresh installs frequently, a separate partition would be much more convenient.

[QUOTE=Larikang;45941301]I think that's a pretty big IF. If you're whole fs goes bonkers, why would your home partition's fs be miraculously spared? Personally, I would be much more concerned about complete drive failure, which a separate partition also isn't going to help with. [editline]10th September 2014[/editline] I guess if you do fresh installs frequently, a separate partition would be much more convenient.[/QUOTE] Pacman being a dickhole, you being a dickhole with portage, I mean there's a whole slew of areas where things can go wrong, where the user can be an idiot, and so on. Maybe YOU don't have this problem, and that's great. But for most people, it can be a huge issue having to reinstall their operating system after it was made unbootable and they didn't have an alternate PC to recover from/to. [editline]10th September 2014[/editline] Besides, things like BTRFS nullifies the whole "space" issue, as you could just have a "system" volume and a "home" volume on one disk. Then you just have to worry about rm -rf's and Btrfs not fucking up.

[QUOTE=FPtje;45940164]I just solved a problem with pacman -S --force today. Let's hope it won't bite me in the ass. The problem was loads of files being disowned by loads of packages. It refused to install the packages because it wouldn't overwrite the files, which were corrupted. With --force it gladly complied.[/QUOTE] Advice on this: Only ever --force on [I]single packages[/I]. When you identify a package as causing problems, and it's not an integral system package, force-reinstalling probably doesn't cause problems. On the other hand, if it's systemd or something that modifies stuff in /, you probably wanna solve the conflicts by hand.

[img]http://i.imgur.com/tloppvb.png[/img] :v:

[QUOTE=esalaka;45941606]Advice on this: Only ever --force on [I]single packages[/I]. When you identify a package as causing problems, and it's not an integral system package, force-reinstalling probably doesn't cause problems. On the other hand, if it's systemd or something that modifies stuff in /, you probably wanna solve the conflicts by hand.[/QUOTE] Yeah, right now the only problem I have is this: [code] falco@manjaro:~$ yaourt -S mdm warning: mdm-1.6.9-1 is up to date -- reinstalling resolving dependencies... looking for inter-conflicts... Packages (1): mdm-1.6.9-1 Total Installed Size: 14.24 MiB Net Upgrade Size: 0.00 MiB :: Proceed with installation? [Y/n] y (1/1) checking keys in keyring [##########################################################################################] 100% (1/1) checking package integrity [##########################################################################################] 100% (1/1) loading package files [##########################################################################################] 100% (1/1) checking for file conflicts [##########################################################################################] 100% (1/1) checking available disk space [##########################################################################################] 100% (1/1) reinstalling mdm [##########################################################################################] 100% ldconfig: File /usr/lib/libpoppler-qt5.so.1.1.0 is empty, not checked. ldconfig: File /usr/lib/libpoppler-qt5.so is empty, not checked. ldconfig: File /usr/lib/libpoppler-qt5.so.1 is empty, not checked. ldconfig: File /usr/lib/libQt5Script.so is empty, not checked. ldconfig: File /usr/lib/libQt5Script.so.5 is empty, not checked. ldconfig: File /usr/lib/libQt5Script.so.5.3 is empty, not checked. ldconfig: File /usr/lib/libQt5ScriptTools.so is empty, not checked. ldconfig: File /usr/lib/libQt5ScriptTools.so.5 is empty, not checked. ldconfig: File /usr/lib/libQt5ScriptTools.so.5.3 is empty, not checked. ldconfig: File /usr/lib/libQt5Script.so.5.3.1 is empty, not checked. ldconfig: File /usr/lib/libQt5ScriptTools.so.5.3.1 is empty, not checked. falco@manjaro:~$ sudo pacman -Qo /usr/lib/libpoppler-qt5.so error: No package owns /usr/lib/libpoppler-qt5.so [/code] those ldconfig errors are thrown every time I install anything. The solution to this is probably reinstalling the packages that own these files. I'll try to guess the packages that own them by the library names :v: [editline]10th September 2014[/editline] And it's resolved, the packages were qt5-script and poppler-qt5

[QUOTE=mastersrp;45941374]Pacman being a dickhole, you being a dickhole with portage, I mean there's a whole slew of areas where things can go wrong, where the user can be an idiot, and so on. Maybe YOU don't have this problem, and that's great.[/QUOTE] Again, what could cause the root partition to be unmountable that wouldn't also affect the home partition? Even with everything in one partition and an unbootable system, you can easily backup files by booting a live image and mounting the partition. On the rare occasions when I've totally fucked up the OS, that's what I've always done. I've never heard of someone actually destroying their root filesystem by accident and rendering it unmountable. That strikes me as too rare a problem to be worth guarding against.

[QUOTE=Mega1mpact;45941734][img]http://i.imgur.com/tloppvb.png[/img] :v:[/QUOTE] I call it [I]Bold and Bash.[/I]

[QUOTE=Larikang;45942278]Again, what could cause the root partition to be unmountable that wouldn't also affect the home partition? Even with everything in one partition and an unbootable system, you can easily backup files by booting a live image and mounting the partition. On the rare occasions when I've totally fucked up the OS, that's what I've always done. I've never heard of someone actually destroying their root filesystem by accident and rendering it unmountable. That strikes me as too rare a problem to be worth guarding against.[/QUOTE] [QUOTE=mastersrp;45941374][...]Maybe YOU don't have this problem, and that's great. But for most people, [...][/QUOTE] Come on man, I mean I already wrote what could be the cause of this. And sure, you happen to know how to recover from this, but the average user does not. HENCE why a home partition would be a good idea, because there's far greater possibility of recovering home data when reinstalling, if you can just mount the partition and maybe change an fstab entry, rather than having to call a support center or go on forums with angry people to ask them for help about something, which you don't even understand. I'm just saying. Things happen, and great if they don't happen to you, but they DO happen. [editline]10th September 2014[/editline] An analogy could be that I've never been robbed in my life, and I have never lost my keys, and so on. I still lock the door, my bike, my PC, and I still have a keychain that I care about in case it happens. If I DO get robbed, I am insured. If I didn't have insurance, I would just be fucked.

I recently migrated from apache2 to nginx on my VPS, and Piwik's log import script isn't working anymore. I changed the path in the cron job, but it still doesn't update. cron job [code]@hourly python /home/apache/public_html/piwik/misc/log-analytics/import_logs.py --url=http://pred.me/piwik/ /var/log/nginx/access.log --idsite=1 --recorders=2 --enable-http-errors --enable-http-redirects --enable-static --enable-bots[/code] I tried running it manually which got me this [code]# python /home/apache/public_html/piwik/misc/log-analytics/import_logs.py --url=http://pred.me/piwik/ /var/log/nginx/access.log --idsite=1 --recorders=2 --enable-http-errors --enable-http-redirects --enable-static --enable-bots Traceback (most recent call last): File "/home/apache/public_html/piwik/misc/log-analytics/import_logs.py", line 1714, in <module> resolver = config.get_resolver() File "/home/apache/public_html/piwik/misc/log-analytics/import_logs.py", line 638, in get_resolver return StaticResolver(self.options.site_id) File "/home/apache/public_html/piwik/misc/log-analytics/import_logs.py", line 974, in __init__ 'SitesManager.getSiteFromId', idSite=self.site_id File "/home/apache/public_html/piwik/misc/log-analytics/import_logs.py", line 957, in call_api return cls._call_wrapper(cls._call_api, None, None, method, **kwargs) File "/home/apache/public_html/piwik/misc/log-analytics/import_logs.py", line 946, in _call_wrapper raise Piwik.Error(message) __main__.Error: Forbidden[/code] googling the issue got me here, [URL]http://forum.piwik.org/read.php?2,105560[/URL] but it seems like the issue has already been fixed in the latest version. I'm at loss, any idea what has caused this? the error is pretty much identical to that thread, but the fix he said to apply is already applied as far as I know from looking at the script

If you guys are a bit slow on updating arch (3 days), they finally got around to updating ncmpcpp, then new version of which breaks a lot of configs. You have been warned.

[QUOTE=Naelstrom;45942512]I call it [I]Bold and Bash.[/I][/QUOTE] More like [I]Belongs in /dev/null[/I].