You are not logged in.
After a pacman -Syu the system began the download of packages, but it couldn't install because it said pacman was locked or something. I went and tried logging out to login, where upon the screen blanked and was forced to manual reboot.
upon trying to recover journal got this error and now i'm in [ramfs /]#
JBD: recovery failed
Ext4 -fs (sda)3: error loading journal
mount: mounting /dev/disk/by-uuid/uuid# on /new_root failed: invalid arguement
ERROR: failed to mount the real root device
bailing out, you are on your own goodluck
/bin/sh: can't access tty: job control turned off
Searches haven't found anything specific to this. My grub looks fine, not sure where to look. Anyone know of a way o recover from this without having to re-install?
where you see uuid# - i didn't want to write the whole number in there ![]()
Last edited by Snakeye (2010-06-28 02:38:12)
Offline
Maybe this could help:
http://bbs.archlinux.org/viewtopic.php?id=93107
Also, you don't need to hide the uuid, as it is not like an ip address
. No one will hack your hard drive ![]()
Last edited by x33a (2010-06-28 03:21:44)
Offline
Hi, wasn't hiding the uuid, just just didn't want to type it in...typing from an spire one can be a hassle ;
I saw that thread before and did try:
mount -t ext4 /dev/sda3/ /new_root with no success
not sure how to do that from the live cd
login as root
root@archiso with the same command mount point /new_root does not exist - never ran into this kind of prblem before so my experience is limited
Last edited by Snakeye (2010-06-28 04:12:56)
Offline
did you try this:
http://bbs.archlinux.org/viewtopic.php? … 77#p731077
Though, i haven't tried any of this, since i haven't had any such problem.
Offline
problem is i can't mount, i get this error....looks like i'm going to have to reformat and start again, unless someody has any ideas, could be the drive is buggerred too
# dmesg : tail
end_request:I/O error, dev/sda, sector 21720274
sd 4:0:0:0: [sda] unhandled error code
sd 4:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
endrequest: I/O error, dev sda, sector 21720214
JBD recovery failed
EXT4-fs: error loading journal.
sd 4:0:0:0: [sda] unhandled error code
sd 4:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
endrequest: I/O error, dev sda, sector 738992
EXT2:fs: unable to read superblock
Last edited by Snakeye (2010-06-28 23:02:57)
Offline
The drive bricked. Appears to be a problem with Seagate barracuda 7200.11 firmware. Anyone with that rev should upgrade before yours bricks ![]()
Offline
You don't say which Barracuda drive is affected nor list a relevant link. Either/both of those would be helpful.
Offline
I bought the system about 1.5 years ago. Drives affected:
500 GB : ST3500320AS (this was the drive i had)
750 GB : ST3750330AS
1000 GB : ST31000340AS
Offline
Hey, I'm having this problem too! Fun stuff. I tried mounting from the cd, but I get "unable to read superblock". Part of the cause may have been that during -Su my connection was cut off, and it stopped halfway. Definitely nothing physically wrong with the drive. I can mount my boot partition just fine. Oh, and the fallback doesn't work either. Any ideas how to finish the update? Me thinks that would fix it, but I have to mount it first...
Not sure if it's relevant, but I did suspend to disk with s2ram before waking it up and rebooting.
Last edited by obankobi (2010-07-02 18:52:15)
Offline
Any ideas how to finish the update?
Boot the arch live cd, chroot into your install (remember to mount the boot partition first), and run pacman -Syu. More info is in [wiki]Change Root[/wiki].
Last edited by hokasch (2010-07-02 18:49:28)
Offline
Any ideas how to finish the update?
Boot the arch live cd, chroot into your install (remember to mount the boot partition first), and run pacman -Syu. More info is in [wiki]Change Root[/wiki].
Tried, I literally can't mount it at all. It's fixed though, in a way. I reinstalled
Record time too, about 2 hours from cd to hulu. BAM!
Offline