[Solved] Cant boot after editing fstab ( virtualbox )
what information do i need to post here to help, and how do i get it since i cant boot in ?
Last edited by Shockwave0 (2013-11-07 00:48:14)
im using openbox i opened up /etc/fstab with leafpad heres what it looks like
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1
UUID=aff5b1d2-0452-467f-81e7-dc3b2298101e / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3
# UUID=1519cef9-0d8d-4ea4-b9d5-cc94b09cd59a none swap defaults 0 0
Last edited by Shockwave0 (2013-11-07 00:05:54)
Similar Messages
-
My macbook pro retina 15'' cant boot after smc reset .
My macbook pro retina 15" cant boot after smc reset. Can someone find me a solution which does not require opening my laptop ? Thnx in advance .
Try Resetting the PRAM
-
[SOLVED] Black screen after grub in Virtualbox guest install
Hi everyone,
I thought I'd give Arch a try and wanted to install it as a guest VM in Virtualbox. I downloaded the 2013.11.01 release ISO (checked md5 sigs) and went to install in my Virtualbox environment. I'm currently running Gentoo as the host (64-bit) and have 64-bit Windows 7, CentOS, and Ubuntu guests that all run without issue.
Upon booting from the ISO, I get a grub prompt and select the x86_64 option. At this point the Virtualbox screen goes black. Zero output and zero disk activity indicated by Virtualbox. VBox.log doesn't indicate any errors that would cause this as far as I can tell. The only error in fact the following (which appears in other guest logs as well):
"00:00:00.550 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={09eed313-cd56-4d06-bd56-fac0f716b5dd} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false"
The Hardware Detection Tool runs fine and detects all the Vbox devices w/o issue as well.
If you'd like the VBox.log I can certainly post it, but I didn't see anything. I'm hoping this is something people have run across before.
Also choosing the i686 option doesn't work as it's a 64-bit system just in case someone asks.
Thanks all!
Edit:
Ok so after some more testing it occurred to me that maybe I should just try a prior release. Gave the 2013.10.01 release a go, and everything boots up fine. Now sure what it was about my VBox set up that Arch didn't like, but it's working now.
Last edited by sgt_b2002 (2013-11-19 19:34:41)As for me, I update my VirtualBox to 4.3.6 and it helps me.
-
[SOLVED] No boot after update unable to find root device|libmount.so.1
Hi,
after my most recent update, which was the first for a long time, I am getting the following error when trying to boot my system:
mount: /lib/libmount.so.1: version 'MOUNT_2.20' not found (required by mount)
cat: can'topen '/proc/cmdline': No such file or directory
ERROR: Unable to find root device ' '
The same for MOUNT_2.21. This error still persists after chroot manual installs of util-linux and glibc. I tried downgrading util-linux still witout success. Following reply #15 of: https://bbs.archlinux.org/viewtopic.php?pid=1130638 did not solve it either.
I also reinstalled grub just to be on the safe side, but nothing helped.
Please help.
Thanks
Last edited by mark-o-solo (2012-08-02 14:56:36)https://wiki.archlinux.org/index.php/Pa … nger_boot.
If you fucked up the glibc migration (read "The /lib directory becomes a symlink" from the archlinux.org front page), there are countless threads about this, including a big one (350+ replies) in the "Pacman & Package Upgrade Issues" category. I'm sure you will find some answers there. -
[SOLVED] Not booting after update to grub, syslinux
I did a system update trying to fix some package dependencies for a mongodb issue. I saw that there were changes to grub, so I stopped, and was good. I checked the home page, I checked the forums. The only thing I found was a thread saying that it should be fine. So I ran the update. syslinux also updated.
After it completed, I diff'd the pacnew files, made all the appropriate changes (I thought) and rebooted.
:: Triggering uevents...
Waiting 10 seconds for device /dev/sda3 ...
ERROR: device 'dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3',
I was then dumped into the recovery shell, which was completely useless since it doesn't seem to be loading the USB drivers and so my keyboard won't work. I think I've got a PS2 keyboard in storage, I'll try to grab it tomorrow. (With my luck, I purged it last time I was cleaning.) I downloaded a fresh image and got a bootable USB going, but I'm at a loss as to what to do next.
I'd wipe and restore the damn thing so I could get back to work, but there's a couple ssh keys that would be a pain to replace. (Yeah, I know, I should have backed them up some place. I didn't.)
Help?
Last edited by jbhelfrich (2013-07-31 19:49:08)I have two partitions on SDA. Partition 1 has the core file system and partition 2 has the contents of the /home directory. I mounted them and chroot into them.
I found http://sourceforge.net/projects/bootinfoscript/, and downloaded that and ran it. It shows that sda1 has syslinux as the boot sector type, but that "the 2 ADV sectors are not the same (corrupt)."
Can I pacman -R grub safely at this point, to at least remove one source of confusion?
Looking at the syslinux.cfg file to see if I can figure out what I missed.
EDIT: OK, the syslinux.cfg has "APPEND root=/dev/sda3 rw" for both arch and archfallback. I assume I can change those to either sda1 or the UUIDs listed in etc/fstab and be good to go?
And yes, I see the trend on wiki articles. Sadly there's not a wiki entry for "hey, what's that linux admin command that I've forgotten will totally save me?" to point me in the right direction.
Last edited by jbhelfrich (2013-07-31 18:24:53) -
[Solved] Error boot after upgrading and util-linux-tools and sysvinit
Hi all ...
This morning I did a sudo pacman -Syu to update my laptop which packs sysvinit-tools 2.88-8 and 2.22-6 util-linux packages including ...
My surprise that I take is that a few hours ago after starting my laptop again I come across a series of error messages which do not allow me log into the laptop. catches of messages are these:
Picture 1
Picture 2
The log of pacman to upgrade is:
[09.24.2012 9:01] Running 'pacman-Syu'
[09.24.2012 9:01] synchronizing package lists
[09.24.2012 9:03] starting full system upgrade
[09.24.2012 9:21] removed eject (2.1.5-7)
[09.24.2012 9:22] upgraded coreutils (8.17-3 -> 8.19-1)
[09.24.2012 9:22] upgraded libmtp (1.1.4-1 -> 1.1.5-1)
[09.24.2012 9:22] upgraded mlocate (0.25-2 -> 0.26 to 1)
[09.24.2012 9:22] upgraded procps-ng (3.3.3-3 -> 3.3.3-6)
[09.24.2012 9:22] upgraded qt (4.8.3-2 -> 4.8.3-3)
[09.24.2012 9:22] upgraded util-linux (2.21.2-5 -> 2.22-6)
[09.24.2012 9:22] upgraded sysvinit-tools (2.88-7 -> 2.88-8)
[09.24.2012 9:22] upgraded transmission-gtk (2.61-3 -> 2.61-4)
[09.24.2012 9:22] upgraded whois (5.0.18-1 -> 5.0.19-1)
In making this latest update pacman eject told me that was going to be replaced by util-linux ... before answering affirmatively check the official website of ArchLinux to see if there were any announcement about this change ... I assumed there was none like it was nothing critical and permitted the installation of this patch ....
At the end of the error message you see in the pictures I show that I can run a command or shortcut systemctl keyboard to enter the "default mode" but I have no way to give commands and keyboard shortcut does not work.
No I could do to recover the system (other than reinstalling ArchLinux with new. Iso) ...
Someone has spent the same??? found a solution???
Greetings and thanks in advance!
Sorry my bad English!
Last edited by jesusangelm (2012-09-25 18:12:20)in another forum recommended me to downgrade the updated packages to restore the system and use it.
but installing the updated packages I get this error
If I try the downgrade util-linux gives me:
pacman -U /var/cache/pacman/pkg/util-linux-2.21.2-5-x86_64.pkg.tar.xz
loading packages...
warning: downgrading package util-linux (2.22-6 => 2.21.2-5)
resolving dependencies...
looking for inter-conflicts...
Targets (1): util-linux-2.21.2-5
Total Installed Size: 7.45 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [############################################] 100%
(1/1) loading package files [############################################] 100%
(1/1) checking for file conflicts [############################################] 100%
error: failed to commit transaction (conflicting files)
util-linux: /bin/dmesg exists in filesystem
util-linux: /bin/findmnt exists in filesystem
util-linux: /bin/login exists in filesystem
util-linux: /bin/lsblk exists in filesystem
util-linux: /bin/more exists in filesystem
util-linux: /bin/mount exists in filesystem
util-linux: /bin/mountpoint exists in filesystem
util-linux: /bin/umount exists in filesystem
util-linux: /sbin/agetty exists in filesystem
util-linux: /sbin/blkid exists in filesystem
util-linux: /sbin/blockdev exists in filesystem
util-linux: /sbin/cfdisk exists in filesystem
util-linux: /sbin/chcpu exists in filesystem
util-linux: /sbin/ctrlaltdel exists in filesystem
util-linux: /sbin/fdisk exists in filesystem
util-linux: /sbin/findfs exists in filesystem
util-linux: /sbin/fsck exists in filesystem
util-linux: /sbin/fsck.cramfs exists in filesystem
util-linux: /sbin/fsck.minix exists in filesystem
util-linux: /sbin/fsfreeze exists in filesystem
util-linux: /sbin/fstrim exists in filesystem
util-linux: /sbin/hwclock exists in filesystem
util-linux: /sbin/losetup exists in filesystem
util-linux: /sbin/mkfs exists in filesystem
util-linux: /sbin/mkfs.bfs exists in filesystem
util-linux: /sbin/mkfs.cramfs exists in filesystem
util-linux: /sbin/mkfs.minix exists in filesystem
util-linux: /sbin/mkswap exists in filesystem
util-linux: /sbin/pivot_root exists in filesystem
util-linux: /sbin/raw exists in filesystem
util-linux: /sbin/sfdisk exists in filesystem
util-linux: /sbin/swaplabel exists in filesystem
util-linux: /sbin/swapoff exists in filesystem
util-linux: /sbin/swapon exists in filesystem
util-linux: /sbin/switch_root exists in filesystem
util-linux: /sbin/wipefs exists in filesystem
util-linux: /usr/bin/cal exists in filesystem
util-linux: /usr/bin/chfn exists in filesystem
util-linux: /usr/bin/chrt exists in filesystem
util-linux: /usr/bin/chsh exists in filesystem
util-linux: /usr/bin/col exists in filesystem
util-linux: /usr/bin/colcrt exists in filesystem
util-linux: /usr/bin/colrm exists in filesystem
util-linux: /usr/bin/column exists in filesystem
util-linux: /usr/bin/cytune exists in filesystem
util-linux: /usr/bin/fallocate exists in filesystem
util-linux: /usr/bin/flock exists in filesystem
util-linux: /usr/bin/getopt exists in filesystem
util-linux: /usr/bin/hexdump exists in filesystem
util-linux: /usr/bin/i386 exists in filesystem
util-linux: /usr/bin/ionice exists in filesystem
util-linux: /usr/bin/ipcmk exists in filesystem
util-linux: /usr/bin/ipcrm exists in filesystem
util-linux: /usr/bin/ipcs exists in filesystem
util-linux: /usr/bin/isosize exists in filesystem
util-linux: /usr/bin/linux32 exists in filesystem
util-linux: /usr/bin/linux64 exists in filesystem
util-linux: /usr/bin/logger exists in filesystem
util-linux: /usr/bin/look exists in filesystem
util-linux: /usr/bin/lscpu exists in filesystem
util-linux: /usr/bin/mcookie exists in filesystem
util-linux: /usr/bin/namei exists in filesystem
util-linux: /usr/bin/newgrp exists in filesystem
util-linux: /usr/bin/pg exists in filesystem
util-linux: /usr/bin/prlimit exists in filesystem
util-linux: /usr/bin/rename exists in filesystem
util-linux: /usr/bin/renice exists in filesystem
util-linux: /usr/bin/rev exists in filesystem
util-linux: /usr/bin/script exists in filesystem
util-linux: /usr/bin/scriptreplay exists in filesystem
util-linux: /usr/bin/setarch exists in filesystem
util-linux: /usr/bin/setsid exists in filesystem
util-linux: /usr/bin/setterm exists in filesystem
util-linux: /usr/bin/tailf exists in filesystem
util-linux: /usr/bin/taskset exists in filesystem
util-linux: /usr/bin/ul exists in filesystem
util-linux: /usr/bin/unshare exists in filesystem
util-linux: /usr/bin/uuidgen exists in filesystem
util-linux: /usr/bin/whereis exists in filesystem
util-linux: /usr/bin/write exists in filesystem
util-linux: /usr/bin/x86_64 exists in filesystem
util-linux: /usr/include/blkid/blkid.h exists in filesystem
util-linux: /usr/include/libmount/libmount.h exists in filesystem
util-linux: /usr/include/uuid/uuid.h exists in filesystem
util-linux: /usr/lib/libblkid.a exists in filesystem
util-linux: /usr/lib/libblkid.so exists in filesystem
util-linux: /usr/lib/libblkid.so.1 exists in filesystem
util-linux: /usr/lib/libblkid.so.1.1.0 exists in filesystem
util-linux: /usr/lib/libmount.a exists in filesystem
util-linux: /usr/lib/libmount.so exists in filesystem
util-linux: /usr/lib/libmount.so.1 exists in filesystem
util-linux: /usr/lib/libmount.so.1.1.0 exists in filesystem
util-linux: /usr/lib/libuuid.a exists in filesystem
util-linux: /usr/lib/libuuid.so exists in filesystem
util-linux: /usr/lib/libuuid.so.1 exists in filesystem
util-linux: /usr/lib/libuuid.so.1.3.0 exists in filesystem
util-linux: /usr/lib/pkgconfig/blkid.pc exists in filesystem
util-linux: /usr/lib/pkgconfig/mount.pc exists in filesystem
util-linux: /usr/lib/pkgconfig/uuid.pc exists in filesystem
util-linux: /usr/sbin/addpart exists in filesystem
util-linux: /usr/sbin/delpart exists in filesystem
util-linux: /usr/sbin/fdformat exists in filesystem
util-linux: /usr/sbin/ldattach exists in filesystem
util-linux: /usr/sbin/partx exists in filesystem
util-linux: /usr/sbin/readprofile exists in filesystem
util-linux: /usr/sbin/rtcwake exists in filesystem
util-linux: /usr/sbin/tunelp exists in filesystem
util-linux: /usr/sbin/uuidd exists in filesystem
util-linux: /usr/sbin/vigr exists in filesystem
util-linux: /usr/sbin/vipw exists in filesystem
util-linux: /usr/share/getopt/getopt-parse.bash exists in filesystem
util-linux: /usr/share/getopt/getopt-parse.tcsh exists in filesystem
util-linux: /usr/share/locale/ca/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/cs/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/da/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/de/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/es/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/et/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/eu/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/fi/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/fr/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/gl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/hu/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/id/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/it/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/ja/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/nl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/pl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/pt_BR/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/ru/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/sl/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/sv/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/tr/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/uk/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/vi/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/zh_CN/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/locale/zh_TW/LC_MESSAGES/util-linux.mo exists in filesystem
util-linux: /usr/share/man/man1/cal.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chrt.1.gz exists in filesystem
util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem
util-linux: /usr/share/man/man1/col.1.gz exists in filesystem
util-linux: /usr/share/man/man1/colcrt.1.gz exists in filesystem
util-linux: /usr/share/man/man1/colrm.1.gz exists in filesystem
util-linux: /usr/share/man/man1/column.1.gz exists in filesystem
util-linux: /usr/share/man/man1/dmesg.1.gz exists in filesystem
util-linux: /usr/share/man/man1/fallocate.1.gz exists in filesystem
util-linux: /usr/share/man/man1/flock.1.gz exists in filesystem
util-linux: /usr/share/man/man1/getopt.1.gz exists in filesystem
util-linux: /usr/share/man/man1/hexdump.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ionice.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ipcmk.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ipcrm.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ipcs.1.gz exists in filesystem
util-linux: /usr/share/man/man1/logger.1.gz exists in filesystem
util-linux: /usr/share/man/man1/login.1.gz exists in filesystem
util-linux: /usr/share/man/man1/look.1.gz exists in filesystem
util-linux: /usr/share/man/man1/lscpu.1.gz exists in filesystem
util-linux: /usr/share/man/man1/mcookie.1.gz exists in filesystem
util-linux: /usr/share/man/man1/more.1.gz exists in filesystem
util-linux: /usr/share/man/man1/mountpoint.1.gz exists in filesystem
util-linux: /usr/share/man/man1/namei.1.gz exists in filesystem
util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem
util-linux: /usr/share/man/man1/pg.1.gz exists in filesystem
util-linux: /usr/share/man/man1/prlimit.1.gz exists in filesystem
util-linux: /usr/share/man/man1/rename.1.gz exists in filesystem
util-linux: /usr/share/man/man1/renice.1.gz exists in filesystem
util-linux: /usr/share/man/man1/rev.1.gz exists in filesystem
util-linux: /usr/share/man/man1/script.1.gz exists in filesystem
util-linux: /usr/share/man/man1/scriptreplay.1.gz exists in filesystem
util-linux: /usr/share/man/man1/setsid.1.gz exists in filesystem
util-linux: /usr/share/man/man1/setterm.1.gz exists in filesystem
util-linux: /usr/share/man/man1/tailf.1.gz exists in filesystem
util-linux: /usr/share/man/man1/taskset.1.gz exists in filesystem
util-linux: /usr/share/man/man1/ul.1.gz exists in filesystem
util-linux: /usr/share/man/man1/unshare.1.gz exists in filesystem
util-linux: /usr/share/man/man1/uuidgen.1.gz exists in filesystem
util-linux: /usr/share/man/man1/whereis.1.gz exists in filesystem
util-linux: /usr/share/man/man1/write.1.gz exists in filesystem
util-linux: /usr/share/man/man3/libblkid.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_clear.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_compare.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_copy.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate_random.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate_time.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_generate_time_safe.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_is_null.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_parse.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_time.3.gz exists in filesystem
util-linux: /usr/share/man/man3/uuid_unparse.3.gz exists in filesystem
util-linux: /usr/share/man/man5/fstab.5.gz exists in filesystem
util-linux: /usr/share/man/man8/addpart.8.gz exists in filesystem
util-linux: /usr/share/man/man8/agetty.8.gz exists in filesystem
util-linux: /usr/share/man/man8/blkid.8.gz exists in filesystem
util-linux: /usr/share/man/man8/blockdev.8.gz exists in filesystem
util-linux: /usr/share/man/man8/cfdisk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/chcpu.8.gz exists in filesystem
util-linux: /usr/share/man/man8/ctrlaltdel.8.gz exists in filesystem
util-linux: /usr/share/man/man8/cytune.8.gz exists in filesystem
util-linux: /usr/share/man/man8/delpart.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fdformat.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fdisk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/findfs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/findmnt.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fsck.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fsck.minix.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fsfreeze.8.gz exists in filesystem
util-linux: /usr/share/man/man8/fstrim.8.gz exists in filesystem
util-linux: /usr/share/man/man8/hwclock.8.gz exists in filesystem
util-linux: /usr/share/man/man8/i386.8.gz exists in filesystem
util-linux: /usr/share/man/man8/isosize.8.gz exists in filesystem
util-linux: /usr/share/man/man8/ldattach.8.gz exists in filesystem
util-linux: /usr/share/man/man8/linux32.8.gz exists in filesystem
util-linux: /usr/share/man/man8/linux64.8.gz exists in filesystem
util-linux: /usr/share/man/man8/losetup.8.gz exists in filesystem
util-linux: /usr/share/man/man8/lsblk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkfs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkfs.bfs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkfs.minix.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mkswap.8.gz exists in filesystem
util-linux: /usr/share/man/man8/mount.8.gz exists in filesystem
util-linux: /usr/share/man/man8/partx.8.gz exists in filesystem
util-linux: /usr/share/man/man8/pivot_root.8.gz exists in filesystem
util-linux: /usr/share/man/man8/raw.8.gz exists in filesystem
util-linux: /usr/share/man/man8/readprofile.8.gz exists in filesystem
util-linux: /usr/share/man/man8/rtcwake.8.gz exists in filesystem
util-linux: /usr/share/man/man8/setarch.8.gz exists in filesystem
util-linux: /usr/share/man/man8/sfdisk.8.gz exists in filesystem
util-linux: /usr/share/man/man8/swaplabel.8.gz exists in filesystem
util-linux: /usr/share/man/man8/swapoff.8.gz exists in filesystem
util-linux: /usr/share/man/man8/swapon.8.gz exists in filesystem
util-linux: /usr/share/man/man8/switch_root.8.gz exists in filesystem
util-linux: /usr/share/man/man8/tunelp.8.gz exists in filesystem
util-linux: /usr/share/man/man8/umount.8.gz exists in filesystem
util-linux: /usr/share/man/man8/uuidd.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem
util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem
util-linux: /usr/share/man/man8/wipefs.8.gz exists in filesystem
util-linux: /usr/share/man/man8/x86_64.8.gz exists in filesystem
Errors occurred, no packages were upgraded.
If I try the downgrade sysvinit-tool gives me:
pacman -U /var/cache/pacman/pkg/sysvinit-tools-2.88-7-x86_64.pkg.tar.xz
loading packages...
warning: downgrading package sysvinit-tools (2.88-8 => 2.88-7)
resolving dependencies...
looking for inter-conflicts...
Targets (1): sysvinit-tools-2.88-7
Total Installed Size: 0.17 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [############################################] 100%
(1/1) loading package files [############################################] 100%
(1/1) checking for file conflicts [############################################] 100%
error: failed to commit transaction (conflicting files)
sysvinit-tools: /bin/pidof exists in filesystem
sysvinit-tools: /sbin/bootlogd exists in filesystem
sysvinit-tools: /sbin/fstab-decode exists in filesystem
sysvinit-tools: /sbin/killall5 exists in filesystem
sysvinit-tools: /sbin/sulogin exists in filesystem
sysvinit-tools: /usr/bin/last exists in filesystem
sysvinit-tools: /usr/bin/lastb exists in filesystem
sysvinit-tools: /usr/bin/mesg exists in filesystem
sysvinit-tools: /usr/bin/utmpdump exists in filesystem
sysvinit-tools: /usr/bin/wall exists in filesystem
sysvinit-tools: /usr/include/initreq.h exists in filesystem
sysvinit-tools: /usr/share/man/man1/last.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/lastb.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/mesg.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/utmpdump.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man1/wall.1.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/bootlogd.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/fstab-decode.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/killall5.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/pidof.8.gz exists in filesystem
sysvinit-tools: /usr/share/man/man8/sulogin.8.gz exists in filesystem
Errors occurred, no packages were upgraded.
If I try the downgrade eject gives me:
pacman -U /var/cache/pacman/pkg/eject-2.1.5-7-x86_64.pkg.tar.xz
loading packages...
resolving dependencies...
looking for inter-conflicts...
Targets (1): eject-2.1.5-7
Total Installed Size: 0.14 MiB
Proceed with installation? [Y/n] y
(1/1) checking package integrity [############################################] 100%
(1/1) loading package files [############################################] 100%
(1/1) checking for file conflicts [############################################] 100%
error: failed to commit transaction (conflicting files)
eject: /usr/bin/eject exists in filesystem
eject: /usr/share/man/man1/eject.1.gz exists in filesystem
Errors occurred, no packages were upgraded. -
Hi
i was trying the unlocked sempron 140 and after i shutdown the pc i wasnt able to boot the next day. this has happened before but now after i try to reset the bios the system still fails to boot. all i get is black screen. and no matter how many times i try to reset the bios i cant get anything on screen at POST.
again i have had this problem before but now resetting bios doesnt seem to help .
so i have to post here and ask any if anyone has any suggestions?
PS. sorry couldnt find better forum to post.
MY System:
Mobo: Msi 770-c45
GPU: saphire radeon 4850
CPU: sempron 140
Bios: latest
PSU: COMPUCASE PSU 550W 12CM ATX12 V2.0Quote from: Henry on 04-March-10, 06:39:57
Please provide information for all components, not just some. You do not say what RAM you have among other things.
>> Posting Guide <<
Ok here's new updated list:
Mobo: Msi 770-C45
GPU: sapphire radeon 4850 512 mb
CPU: Athlon II X4 630/AM3 2.80GHz 2MB-L2 95W
PSU: ANTEC PSU 650W 12CM ATX12V2.2 80+
RAM: 1GB 1333MHZ DDR3 NON-ECC CL9 DIMM x 4
Other devices: 3 x HDs , 1 CD-Rom
OS: win xp home
Bios: latest -
[Solved]Wont boot after installing syslinux; unknown filesystem 'swap'
After installing syslinux to be my boot manager I can no longer boot into Arch, I can however boot into Windows 7. When I try to boot into Arch I get the following error.
Loading ../vmlinuz-linux......
Loading ../initramfs-linux.img......ready.
Probing EDD (edd=off to disable)... ok
Decompressing Linux... Parsing ELF... done
Booting the kernel.
:: running early hook [udev]
:: running hook [udev]
:: Triggering uevents...
:: performing fsck on '/dev/sda3'
fsck: fsck.swap: not found
fsck: error 2 while executing fsck.swap for /dev/sda3
ERROR: fsck failed on 'dev/sda3'
:: mounting '/dev/sda3' on real root
mount: unknown filesystem type 'swap'
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs /]#
What's going on?
Last edited by slughappy1 (2012-07-05 22:50:35)loafer wrote:Can you post your syslinux.cfg please.
Surely
# Config file for Syslinux -
# /boot/syslinux/syslinux.cfg
# Comboot modules:
# * menu.c32 - provides a text menu
# * vesamenu.c32 - provides a graphical menu
# * chain.c32 - chainload MBRs, partition boot sectors, Windows bootloaders
# * hdt.c32 - hardware detection tool
# * reboot.c32 - reboots the system
# * poweroff.com - shutdown the system
# To Use: Copy the respective files from /usr/lib/syslinux to /boot/syslinux.
# If /usr and /boot are on the same file system, symlink the files instead
# of copying them.
# If you do not use a menu, a 'boot:' prompt will be shown and the system
# will boot automatically after 5 seconds.
# Please review the wiki: https://wiki.archlinux.org/index.php/Syslinux
# The wiki provides further configuration examples
DEFAULT arch
PROMPT 1 # Set to 1 if you always want to display the boot: prompt
TIMEOUT 50
# You can create syslinux keymaps with the keytab-lilo tool
#KBDMAP de.ktl
# Menu Configuration
# Either menu.c32 or vesamenu32.c32 must be copied to /boot/syslinux
UI menu.c32
#UI vesamenu.c32
# Refer to http://syslinux.zytor.com/wiki/index.php/Doc/menu
MENU TITLE Arch Linux
#MENU BACKGROUND splash.png
MENU COLOR border 30;44 #40ffffff #a0000000 std
MENU COLOR title 1;36;44 #9033ccff #a0000000 std
MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all
MENU COLOR unsel 37;44 #50ffffff #a0000000 std
MENU COLOR help 37;40 #c0ffffff #a0000000 std
MENU COLOR timeout_msg 37;40 #80ffffff #00000000 std
MENU COLOR timeout 1;37;40 #c0ffffff #00000000 std
MENU COLOR msg07 37;40 #90ffffff #a0000000 std
MENU COLOR tabmsg 31;40 #30ffffff #00000000 std
# boot sections follow
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
LABEL arch
MENU LABEL Arch Linux
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux.img
LABEL archfallback
MENU LABEL Arch Linux Fallback
LINUX ../vmlinuz-linux
APPEND root=/dev/sda3 ro
INITRD ../initramfs-linux-fallback.img
LABEL windows
MENU LABEL Windows7
COM32 chain.c32
APPEND hd0 1
LABEL hdt
MENU LABEL HDT (Hardware Detection Tool)
COM32 hdt.c32
LABEL reboot
MENU LABEL Reboot
COM32 reboot.c32
LABEL off
MENU LABEL Power Off
COMBOOT poweroff.com -
I installed Arch in my laptop from usb following the beginners guide
Used GPT partitioning and my current disk structure is :
1007K free space
sda1 100M Win
sda2 54G Win ( windows 7 )
sda3 3G swap
sda4 16.3G arch ( /mnt)
sda5 38.4G home (/mnt/home)
on running
# grub-install --target=i386-pc --recheck /dev/sda
i get the output :
/usr/sbin/grub-bios-setup: warning : this GPT partition label contains no BIOS boot Partition; embedding wont be possible
/usr/sbin/grub-bios-setup: warning : Embedding id not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-bios-setup: error : will not proceed with blocklists
so i ran
# grub-install --target=i386-pc --recheck --force /dev/sda
i got the same warning but no error
finally
# grub-mkconfig -o /boot/grub/grub.cfg
i got the output :
Found Linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs--linux.img
Warning: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
No volume groups found
Found Windows 7 (loader) on /dev/sda1
done
exited the chroot, unmounted the disks and rebooted
on reboot i get
GRUB <blinking cursor>
what should i do now??
Last edited by soumyaxyz (2013-03-18 19:03:47)s1ln7m4s7r wrote:
i get the output :
/usr/sbin/grub-bios-setup: warning : this GPT partition label contains no BIOS boot Partition; embedding wont be possible
/usr/sbin/grub-bios-setup: warning : Embedding id not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-bios-setup: error : will not proceed with blocklists
Your setup doesn't respect the preliminary requirements for GRUB2 on GPT (lack of bios boot partition)
https://wiki.archlinux.org/index.php/Gr … structions
I tried syslinux earlier but then i got just a blinking cursor after rebooting
so is there any way for me to salvage the installations ?
[edit] I forgot to mention the 1007k free space at the start ( i have edited the original post)
Warning: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
No volume groups found
Are you using any lvm volumes?
No I did not set up any logical volume
Last edited by soumyaxyz (2013-03-18 19:05:30) -
Cant boot after upgrade with conflicts
hi
always when i install arch and do:
pacman -Syu
i have error:
failed to comit transaction (conflicting files)
without that upgrade i cant install desktop manager so i try:
pacman -Syuf
pacman -Sc
pacman -Syu
and it finish upgrade without errors but when i reboot it want boot:
Unable to find root device /dev/sda10
You are beign dropped to a recovery shell
and my keyboard doesnt work too, only i can i reinstall Arch and when i do that i have same problem next time with conflicting files.
i try many linux distros, gentoo, slackware and every of them works great only arch have stupit conflictioning, is this a bug ?
what can i do ?
thanxFor an explanation about those conflicting file errors (and how to fix them), take a look here.
As for the "unable to find root device" error, you probably borked something by running "pacman -Syuf" (never use the -f flag for a generic update). Take a look here at how to fix that. -
Cant boot after installin OS X
Just got a Power Mac G4 Tower. I installed OS X, everything looked fine but when on the restart it got stuck on a grey screen with a broken folder icon. What does this mean and how do I fix it?
Please help.This is the current situation. As previously mentioned I got 2 G4 towers, the second upgraded without any problems it has Panther on it now. With the other tower I’ve installed OS 9.2.2 and upgraded the firmware (with your help, thank you.) I put in the same CD’s that worked in the second tower and now get an error “Startup Disk was unable to select the install CD as the startup disk. (-2)” I’ve also tried restarting holding down C with the panther install disks in and I no longer get the broken folder icon but a flashing apple face and question mark. I let go of C and it boots up in 9.2.2
I feel like I’ve made some progress but I’m still stumped on my next move.
oh yea. the only difference between the 2 towers is one is from 2000 and the other is 2001. The 2000 is the one giving me trouble. Don't know if that matters or not. -
cant boot after i ran out of battery during update later when i recharged it i left macbook on for 12hours without moving off the boot screen (the grey apple with the circle loading thing) i tried repairing it with mac install disk but nothing. not sure what operating system i got it end of 2010
You will need to do the following:
Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.
When formatting has completed quit DU and return to the installer. Complete the OS X installation.
BTW, your profile says Mac Pro, but you have a MacBook Pro, so you should change it to reflect what you are using. -
T540p wont boot after bios update
I updated my T540p a few days ago using Lenovo Solution centre, hiwever, it cant boot after update. The power button is on and fan spins, but the screen is black. I tried: remove battery and all external device and press power button for 30 seconds, out back the battery, still screen wont show anything; tried usb recovery stick, didn't work; tried Recovery discs from Lenovo, still failed.
Please help. Thanks in advance.Ouch. And just out of luck.
Chances are, the board is bricked. -
[Solved] Unable to boot after install
Forgive me for the lack of code tags, having to write this on my phone.
I am unable to boot after installation. I receive an error wich has the incorrect UDID string. It doesn't even exist. I will update with error after posting so I can give grub config generation error first
When I run:
grub-mkconfig -o /boot/grub/grub.cfg
I get this:
Found Linux image : /boot/vmlinuz-linux
Found initd image: /boot/initramfs-linux.img
Warning: failed to connect to lvmetad: no such file or directory. falling back to internal scanning.
No volume groups found
[ 279.601712] SQUASHFS error: can't find a SQUASHFS superblock on sda3
[ 279.604502] EXT4-fs (sda3):unable to read superblock
[ 279.607266] EXT4-fs (sda3):unable to read superblock
[ 279.609928] EXT4-fs (sda3):unable to read superblock
Found Windows 7 (loader) on /dev/sda1
Done
Sda3 is an extended volume
Edit: I just deleted the old .cfg and recreated a new one by re running the above command, uncounted and rebooted and it booted into CLI. 3rd time a charm after all. Marking this one solved
Last edited by Kirito (2013-05-15 07:55:31)Oh, looking at your setup, it would seem that your system is likely still configured to boot to /dev/sdd (the windows drive).
As a user with numerous drives, you should be aware that using /dev/sdXY to identify your disks is a bad idea. There is no gaurantee that Arch will be /dev/sde every time, nor that windows will be /dev/sdd. You should use either filesystem labels (LABEL= or /dev/disk/by-label) or UUIDs (UUID= or /dev/disk/by-uuid). Though if you are using GPT, there is also the option of the PARTLABEL as well (which are the labels you create within the partitioner). -
[SOLVED] Arch won't boot after I created a separate /var parition
Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)
Maybe you are looking for
-
Proft center field pick up in recon a/c but not in cust/vendor line item
Dear All My client want in fbl5n & fbl1n line item should display profit center, How can it be shown& and how recon a/c automatically pick profit center? Thanks in advance vishvas bhavsar Edited by: vishvas bhavsar on Apr 2, 2008 11:44 AM
-
im relatively new to dw 8 and have a problem. in split vied or code view I cant edit change or remove tags. ie if i want to remove a <font> tag. i can highlight it in the code view window but if i try to cut nothing happens. Im sure i just have a set
-
After software update my ipod touch is not working at all?
I updated my ipod with the latest software and after that it went dead. Completely
-
I do internet website rating and when I try to rate a mobile page, I first go to tools, then to mobile plugins, then put mark by mobile plugins. But when I go to the mobile page, it doesn't disply the page like you would see on your phone. I have to
-
Why won't apple acknowledge and fix the IOS 5 update encryption bug?
When updating to IOS5 and saving a backup, if you intentionally do not encrypt the backup, the software will do it for you against your will without letting you know. The source for the assigned against your will and knowledge password for that back