I used to run Gutsy on /dev/sda2 (/dev/sda1 is still XP). I then upgraded Gutsy to Hardy via the net ( had made a live CD, though, that proved *very* useful later)Hardy went freezing up more and more until it blocked totally, locking me out from anything but console commands, so I reinstalled Gutsy fresh on a different partition /dev/sdb2.Now I mount the former gutsy boot partition as /home/data,but more and more often, then always, the partition won't automount and I "fall" into the diag console.There I can issue the "mount /dev/sda2" and "exit" commands and all
since I want to update to Hardy Heron with a clean system, I would like to get rid of a problem, which always arises when booting. I have to confess that my hard disk is a little bit unorganised since I had earlier Suse 10.3 and I never got rid of these partitions. Anyways when my Ubuntu 7.10 boots it will interupt with the following message:Log of fsck -C -R -A -a Fri Mar 21 12:05:44 2008fsck 1.40.2 (12-Jul-2007)fsck.ext3: Unable to resolve 'UUID=fa5e0896-cef7-4aff-8865-1e1952ada05b'/dev/sda6: clean, 30859/1463040 files, 950208/2921814 blocksfsck died with exit status 8 Since I am not sure ab
I believe that I may have both caused this and solved my problem. I have two drives, both Gutsy. I was trying to move files between the two and in former times, had instructions for doing that. The last line (now commented out) was that instruction. On nano-ing the line with ##, the OS restarted without problem.Of the 2 posts that discuss "fsck died with exit status 8" both have "0" replies. But here I go anyway.This is a brand new motherboard & cpu. Same hard drive, but newly installed Gutsy Desktop (tribe 2). It has been completely updated this morning. When powered u
I am receiving the following error message on startup"* Checking file systems...fsck 1.40.8 (13-Mar-2008)/dev/sde1 is mounted. e2fsck: Cannot continue, aborting.I am then asked to repair the file system manually. I am dumped into a maintenance shell, where I attempt fsck, but of course it cannot continue because of the mounted disk. I attempt to unmount /dev/sde1, and receive the message "umount: /dev/sde1: not mounted". Where do I go from here?
need some help with this please, i searched these post and found the same problem that had been resolved , unfortunatly for me there were one or two differences .So i could not resolve the problem by following the said post . 1. /var/log/fsck/checkfs gave permission denied , so thats where i got to with my problem .
I've been messing around with Lucid alpha on a second partition on my desktop computer's main drive, and I also installed a second hard drive that was given to me. I've started getting some fsck errors occasionally when I boot into my main (Hardy) installation. I'll get the message "fsck failed with status 8" (or similar wording) and then a root shell appears. If I continue with the boot, I then get the message that my home directory doesn't exist and the option to log into a different directory.If I then reboot, the next bootup is fine. In one case, it even went into a routine check
This morning, I booted up my laptop and the boot sequence got stuck at the boot splash screen (plymouth). I did an esc and I saw a failure message, the error I remember in my panic mode is: fsck terminated with status 8I rebooted, got the same message. Rebooted again and this time, to my relief, it worked.1) What happened, should I be concerned? Not sure why it worked after 2 reboots.2) Is there a possibility this could happen again?3) Are there any boot log files I could look at?4) Is there anything I can do to fix this? Or a check of some sort?I'm using Ubuntu 10.04 on a Dell Studio 1535 lap
I have a multi-partition computer with Kubuntu Edgy [/dev/hda1 & /dev/hda2], Fedora Core 6 [/dev/hda6], and Suse 10.1 [/dev/hda7]. After a rescent upgrade in Fedora I started getting the following error when booting into either Kubuntu partition:Log of fsck -C -R -A -aWed Nov 8 14:19:54 2006fsck 1.39 (29-May-2006)/dev/evms/hda1: clean, 113661/9486336 files, 1510685/18944643 blocksfsck.ext3: Unable to resolve 'UUID=1ba0e117-1c0c-4e2c-a2bd-0dfd679c4eda'Replaying journal..Reiserfs journal '/dev/evms/hda7' in blocks [18..8211]: 0 transactions replayedChecking internal tree..finishedReiserfs su
I've been chugging along nicely with Feisty but recently I've noticed some strange behaviours, notably that on every second reboot I get:fsck died with exit status 8and the bootscreen goes into console mode (instead of the splash) showing me that the system is checking the filesystem for errors.Here is my fstab:proc /proc proc defaults 0 0# Entry for /dev/sda6 :UUID=962a8ced-a159-470d-bcbe-98707bbc5e5d / jfs defaults,errors=remount-ro 0 1# Entry for /dev/sda8 :UUID=c53654eb-fd20-4954-a755-080f47c07802 /boot reiserfs notail 0 2# Entry for /dev/sda9 :UUID=f32c390b-2325-4dce-934c-da3255a91d17 /ho
I have a multi-partition computer with Kubuntu Edgy [/dev/hda1 & /dev/hda2], Fedora Core 6 [/dev/hda6], and Suse 10.1 [/dev/hda7]. After a rescent upgrade in Fedora I started getting the following error when booting into either Kubuntu partition:Log of fsck -C -R -A -aWed Nov 8 14:19:54 2006fsck 1.39 (29-May-2006)/dev/evms/hda1: clean, 113661/9486336 files, 1510685/18944643 blocksfsck.ext3: Unable to resolve 'UUID=1ba0e117-1c0c-4e2c-a2bd-0dfd679c4eda'Replaying journal..Reiserfs journal '/dev/evms/hda7' in blocks [18..8211]: 0 transactions replayedChecking internal tree..finishedReiserfs su
I installed Kubuntu, and the installation went seamlessly.I have it dual-booting with windows XP.However, when I boot into Kubuntu, I get the following messagefsck 1.39 (29-May-2006)dosfsck 2.11, 12 Mar 2005, FAT32, LFN/dev/hda1: 41 files, 375306/487010 clustersreiserfs_open: the reiserfs superblock cannot be found on /dev/hda3.Failed to open the filesystem.If the partition table has not been changed, and the partition isvalid and it really contains a reiserfs partition, then thesuperblock is corrupted and you need to run this utility with--rebuild-sb.fsck died with exit status 8If I then type
Upon reboot:Log of fsck -C3 -R -A -a Thu Jul 2 09:33:58 2009fsck 1.41.4 (27-Jan-2009)fsck.ext3: Unable to resolve 'UUID=8aad621d-6f4d-4fad-b1c3-630379f7f0e0' fsck died with exit status 8This UUID is NOT for any mounted hard drive. I don't know what it belongs to. The only change I made that may have caused this is to reformat a second (non-boot) drive to wipe XP and create a ext3 partition.Could the UUID belong to the old partition or does it point to hardware?UPDATE: Problem SolvedThe UUID changed when I reformatted sdb1.I edited fstab to include the new UUID
HiI need help ! My computer froze yesterday (it happens) but when I reboot, nothing works.I have only 3 partitions one for boot, one for swap and one for /homeIt can't find /home.And I can't find it neither. It seems to have disappeared...As I can't reboot, I'm running on the live-cd !!Here are some logs :/var/log/fsck/checkfsLog of fsck -C -R -A -a Mon Dec 28 00:33:51 2009fsck 1.41.4 (27-Jan-2009)fsck.ext3: Unable to resolve 'UUID=20fb5021-6a0a-466b-bef9-8ad42c3ea522'fsck died with exit status 8Mon Dec 28 00:33:59 2009----------------/etc/fstab# /etc/fstab: static file system information.## U
I am a newbie to ubuntu as well as linux period. I am receiving an error upon booting up ubuntu and I get the "fsck died with exit status 8" message. I looked through everything I could find on the internet and havewnt found a solution to my problem. /var/log/fsck/checkfs:Log of fsck -C3 -R -A -aSat Jan 17 20:54:09 2009fsck 1.41.3 (12-Oct-2008)dosfsck 2.11, 12 Mar 2005, FAT32, LFNThere are differences between boot sector and its backup.Differences: (offset:original/backup)71:4f/46, 72:53/41, 73:20/54, 74:53/33, 75:48/32, 76:41/00, 77:52/00, 78:45/00, 79:20/00, 80:20/00, 81:20/00Not a
what should I do? Nothing appears to be broken, however this error is really holding up my boot sequence(at least until I hit ctrl+D to continue).scragar@scragar-comp:~$ cat /var/log/fsck/checkfsLog of fsck -C3 -R -A -a Sat Apr 26 02:47:57 2008fsck 1.40.8 (13-Mar-2008)/dev/sda2 is mounted. e2fsck: Cannot continue, aborting./dev/sdb1: clean, 15299/30539776 files, 21754058/61049000 blocksfsck died with exit status 8Sat Apr 26 02:47:57 2008----------------Any help greatly appreciated.
Hi, i got this error today, at boot and was not able to fix it .i try thefsck /dev/sda2no fix-------------------------*Checking file systems...145fsck 1.41.4 (27-Jan-2009)fsck.ext3: Unable to resolve 'UUID=2c482e50-8c52-48d4-a314-a23c234bd4d6'fsck died with exit status 8----------------------thx for any help
fsck.ext3 unable to resolve 'UUID=bea292d9-0c18-45c1-84b1-021c84247b1b'fsck died with exit status 8File system check failed a log is being saved in your /var/log/fsck/checkfs if that location is writableplease repair the file system manuallya maintenance shell will now be startedCONTROL-D will terminate the shell and resume system boot-------------------------------------------------------------When i start up my computer the above message comes up halfway through the loading bar on my UBUNTU 7.10 system, i must press control & d together to continue to the splash screen to log on, i'm cur
I've seen a few of these posts here, but none seem to pertain to my problem.During boot, init or some other process tries to write to either /var/run/pppconfig or /var/run/network/initialized and says it can't because the file system is mounted readonly.Here is what the contents of /var/log/fsck/checkfs and checkroot:Log of fsck -C -R -A -aSun Feb 8 17:24:07 2009fsck 1.41.3 (12-Oct-2008)/dev/sda6 is mounted. e2fsck: Cannot continue, aborting./dev/sda7 is mounted. e2fsck: Cannot continue, aborting.fsck died with exit status 8Sun Feb 8 17:24:07 2009----------------root@mgracy-laptop:/var/log/fsc
I have tried installing Intrepid with LVM and MD RAID 1. During boot fsck fails, halting the boot process. If I ignore the error and let it continue (using Ctrl+D) it boots as though everything were just fine. This is obviously a bad thing, as the file system is not being checked and the journal not being recovered.I have included the fsck logs below. It seems that fsck completes successfully on /dev/mapper/vol0-home, but fails on /dev/mapper/vol0-root . Running a read-only fsck on /dev/mapper/vol0-root identifies some minor issues (incorrect block count [off by 7] and such).Anyone got any bri
I tried moving a 3 disk RAID5 over from one machine to another. It booted, saw it and started checking it, it got a while through then died with the following error...I'm retyping this from notes, so there may be some typos:/dev/md0 is mounted e2fsch: Cannot continue, abortingfsck died with exit status 8* File system check failedA log is at .... /var/log/fsck/checkfs But that contains just the following:cat /var/log/fsck/checkfsLog of fsck -C3 -R -A -aFri Jul 11 00:50:19 2008fsck 1.40.8 (13-Mar-2008)/dev/md2: clean, 4407/18546688 files, 1104095/37090048 blocks/dev/md0 is mounted. e2fsck: Canno
I was trying to resize my partition with Gparted (on the Ubuntu LiveCD), but I clicked cancel... I think that was a bad idea. When I went to boot, it will go through then go to a black screen with a flash cursor. When I go into recovery, it will get to the part that it checks the file system, then it will sayCode:checking Files Systems fsck 1.4.2fsck.ext3 unable to resolve 'UUID=8ac63799-2a29-4668-90cd-1cf6fc3a6a8e'fsck died with exit status 8I have looked all over for help and so far nothing has D:Please help!
uh......that doesn't sound good. I just re-partitioned my disks with gparted live cd, and reinstalled the O.S. this morning & ran all of the updates (Ubuntu 8.04 LTS). The updates required restarting on a few occasions and everything was fine. I shut down my machine this evening, then remembered something I wanted to view online so I started my machine back up and here's what it said:fsck 1.40.8 (13-Mar 2008)/dev/sda1: clean, 25373/3630144 files, 632105/7259364 blocks.......donestarting early crypto disks.......donestarting remaining crypto disks......donechecking file systems...1178fsck 1
fsck 1.40.2 (12-Jul-2007)dosfsck 2.11, 12 Mar 2005, FAT32, LFN/dev/sda5: 296 files, 3803/1220891 clustersFailed to open the device 'UUID=7fb43e05-a1ec-4a6b-aee2-e5b3d5e542bf': No such file or directoryfsck died with exit status 8Sat Feb 23 13:39:11 2008It happened after I install Ubuntu studio 7.10 on sda5 where as Ubuntu 7.10 was already installed on sda7 both are using same swap partitionit says correct the problem manually and leave me at bash root where after pressing Control+D Ubuntu opens
Im getting this error when booting (this was logged to /var/log/fsck/checkfs)Log of fsck -C -R -A -a Thu Jul 5 12:34:24 2007fsck 1.40-WIP (14-Nov-2006)/media/MyStuff: clean, 6737/13526784 files, 5394172/27000832 blocks (check in 2 mounts)fsck.ext3: Unable to resolve 'UUID=5fbd7372-1f1d-4554-9ada-3f3534790b05'fsck died with exit status 8Thu Jul 5 12:34:24 2007----------------then my partitions are all screwy once im booted up
since i've upgraded to feisty from edgy, i get this error while booting up SOMETIMES:* Checking file systems...fsck 1.40-WIP (14-Nov-2006)/dev/hda3 is mounted. e2fsck: Cannot continue, abortingfsck died with exit status 8[fail]* File system check failed.A log is being saved in /var/log/fsck/checkfs if that location is writable.then, it says if i want to continue the boot sequence press Ctrl-D. so, i do that and i get into fesity, which is where i'm writing from now. but this is REALLY annoying when it happens.here is that log file:Log of fsck -C -R -A -a Fri Jun 22 17:40:29 2007fsck 1.40-WIP (
I have a clean install of Ubuntu Feisty (works well). I rebooted and suddenly things aren't so great.It showed the black screen with white letters saying "fsck died with exit status 8" among other things. It said to repair the file system manually and gave me a debugging shell, I think.I typed "shutdown", and it complained about needing a time. I typed "shutdown --help" and the help flew by very fast, only letting me see the bottom half. First question: how do I make it go page by page?So I took a guess and typed "shutdown now". It returned the familiar
Hope someone can help. I have 6.10 server edition running as an nfs server. Problem is at boot i get the following error message.fsck.ext3: Unable to resolve 'UUID=bf2a67b2-ec21-4f56-8b8d-63eb372ac7ab'fsck.ext3: Unable to resolve 'UUID=bc743902-4999-4f59-bcb9-2aa4f6b7fe96'fsck.ext3: Unable to resolve 'UUID=2f5756bf-6a03-4dc2-a230-12c341d37d92'fsck died with exit status 8and then i boot into the maintenance shell. Promptly after booting into the maintenance shell the usb drives appear and then if i hit control-d everything is fine.this is an ls -l on /dev/disk/by-uuid/2f5756bf-6a03-4dc2-a230-12
I get this when I try to boot:*Activating swap... [fail]*Checking root file system.../dev/hda2: clean, 146286/1311552 files, 1600298/2622611 blocks[ ok ]*Checking file systems...fsck 1.39 (29-May-2006)fsck.ext3: Unable to resolve 'UUID=62100d90-0174-4bbe-b773-47beaede9e77'fsck died with exit status 8And when I log in I get this:http://i106.photobucket.com/albums/m264/kaurdal/Screenshot-gnome-session.pngMy /etc/fstab:# /etc/fstab: static file system information.## <file system> <mount point> <type> <options> <dump> <pass>proc /proc proc defaults 0 0 # /dev/hd
Help- I've ballsed up my ubuntu installation and haven't a notion how to get it going again...Basically, I've my computer set to dual boot Windows XP and Ubuntu. I've just installed the new version of Ubuntu and had it all configured the way I like it, but hadn't partitioned my /home separately. I know- stupid, but, lessons learned and all that.Anyway, I've a really old computer lying here that I wanted to run vector linux on, so I installed it's hard drive to my current computer as a slave and tried to install vector there, so I could then move it back to the old desktop (it doesn't have it's
I have a dual boot system with 3 drives. One drive is /home, second drive is /swap and / and the third drive is Windows.If I go into the BIOS and disable the Windows drive, all is fine. However, once it is enabled and I try to boot into Ubuntu I get the following message.bad magic number in super-block....fsck died with exit status 8states that this happens on the following device: /dev/sdb1/if I type "exit" at the terminal it then will go to the Ubuntu login screen, but when I try to login, it says it cannot find /<username>/home. (I think I know why see below)...When I disabl
After upgrading (and fixing xorg problems), I still get an error fsck error message which opens up a root terminal. If I exit "root", then the system goes on to boot (it concerns a partition with Suse 10.1 on it).Anyone have any ideas?ThanxDaf----------Log of fsck -C -R -A -a Wed Nov 1 11:11:27 2006fsck 1.39 (29-May-2006)/dev/hda5: clean, 10992/2215168 files, 3429595/4427907 blocks (check after next mount)fsck.ext3: Unable to resolve 'UUID=d64d70d0-f73d-4922-a64e-2bb8a663e09f'fsck died with exit status 8Wed Nov 1 11:11:27 2006----------------
Reading through the other posts didn't seem to help. I get the fsch...status 8 error when trying to boot my Xubuntu server. I'm probably missing something stupid, so hopefully someone can point it out for me!ubuntu@ubuntu:~$ sudo blkid/dev/sdb1: TYPE="swap" UUID="812630cd-efab-48aa-8cd4-7ce64174c95f" /dev/sdb2: UUID="62ca7e3f-d0e3-43e7-93b6-08db34b79707" SEC_TYPE="ext2" TYPE="ext3" /dev/sdc1: UUID="d441b06e-4df5-4576-b855-d024c87565d0" SEC_TYPE="ext2" TYPE="ext3" /dev/sdc2: TYPE="swap" UUID="b27dcfdb
Hoping someone can help me out <fingers crossed> and that I'm in the right area...I have installed ubuntu 8.10 (upgraded from 8.04) I don't know what I've done but now I randomly get this exit status 8 error when I boot up.Normally, I boot up, get the error, press ctrl+d, continue booting, then reboot once I reach the desktop (this isn't the right desktop and the home folder doesn't have any of my stuff in it) and most of the time it'll boot up without error and I'll get my correct /home folder and all will be ok.My SATA drive is partitioned with a / (sdc1 54 gig) and /home (sdc2 590gig)
unreadahead man process (713) terminated status 5mount all man process (714) terminated status 127mount all: undefined symbol: udev_monitor_filter_add_match_subsystem_devtype Updates 8.10 with automatic updates and when restarted crashes with these errors.Any advice would be helpful...
Xubuntu Hardy,During boot, quiet mode loads to about halfway, then verbose mode starts and continues to the login page. "fsck died exit status 32" appears, then the system boots just fine to the login screen. No issues, except for the verbose mode. Would like to correct the verbose issue. Once every 15 or so startups, it's quiet, with no verbose swithcing at boot.Seems like verbose starts all the time ad "DHCP Discovery." I've got the Broadcom 4306 wireless chip & wonder if this has anything to do with it?
Can't boot into Ubuntu. Using recovery mode, I get fsck exit with status 3 error. I did man on fsck and there is no reference to status 3. Same issue as http://ubuntuforums.org/showthread.php?t=457612 Please help as I have my data on sdb3 which is having this issue. File system is ext4. I can't go into shell or anything, I get the fsck error and the system reboots right away and stuck in that loop.
I am getting below error in our alert.log file when 300+ users runs.Our database server info :1 OS : Windows Server 2003 Version V5.2 Service Pack 12 ORACLE V10.2.0.2.03 processes = 500sessions = 555sga_max_size = 1182793728__shared_pool_size = 234881024__large_pool_size = 8388608__java_pool_size = 25165824db_block_size = 8192__db_cache_size = 335544320open_cursors = 300pga_aggregate_target = 3145728004. Sqlnet.ora file's parameter.SQLNET.AUTHENTICATION_SERVICES= (NONE)NAMES.DIRECTORY_PATH= (TNSNAMES) **********************Error***********************Mon Aug 13 07:33:51 2007Starting background
The database is 10.2.0.3 and the operating system is windows 2003 service pack2.Today morning the alert log has the following entriesORA-27300: OS system dependent operation:CreateThread failed with status: 8ORA-27301: OS failure message: Not enough storage is available to process this command.ORA-27302: failure occurred at: ssthrddcrUsers complained that they cannot access the applications and so when i restarted the database,the applications are running fine.But how to resolve this error on windows box?
So...I had Windows, Ubuntu and Fedora installed on my laptop. I hardly ever use Fedora...so I formatted that partition to give me some extra space.Anyway, when I try and boot into Ubuntu, it says something about an exit status 8 and something something and then gives me a UUID.I can get passed it by typing exit at the prompt but it's kind of annoying to do every time :-\How can I fix this?
What to do when you run "sudo fsck.reiserfs /dev/hdc4 --rebuild-tree" and get the error ".Not enough allocable blocks, checking bitmap...there are 0 allocable blocks, btw out of disk space"?The partition was originally on /dev/hda7 (mounted as /home) and was 99% full when it had an error. I have bought a new HD and dd'd the partition to a bigger partition (nearly twice the size) then tried to "sudo fsck.reiserfs /dev/hdc4 --rebuild-tree" but it still says it can't allocate blocks...Any ideas?
I have restore Oracle ERP apps R12 & DB11g on Solaris 5.10 by tar the /oracle to&from tape. The 'addbctl.sh start' and 'addlnctl.sh start prod' has return code0, but the './adstrtal.sh', starts by id prodmgr, has a list of errors and with status 8.===$ ./adstrtal.shYou are running adstrtal.sh version 120.15 Enter the APPS username: APPSEnter the APPS password:The logfile for this session is located at /oracle/prod/R12_prod/inst/apps/PROD_psser1/logs/appl/admin/log/adstrtal.logExecuting service control script:/oracle/prod/R12_prod/inst/apps/PROD_psser1/admin/scripts/adopmnctl.sh startsc
I recently upgraded my sister and brother in law's PC to 8.10. All well and good, but I was just about to take it back to her, and turned it on to check a couple of things. I got the above error message.I have hunted around, and I clearly need to change the UUID in fstab. sudo vol_id -u sdb1However, the system will not recognise the drive to give me the correct UUID./dev/sdb1: error opening volumePlease help! My brother in law has developed a facebook addiction and is hassling me to get it back!Edit: The root partition is fine, it is /home on a seperate hard drive that is the problem. I update
I recently upgraded my sister and brother in law's PC to 8.10. All well and good, but I was just about to take it back to her, and turned it on to check a couple of things. I got the above error message.I have hunted around, and I clearly need to change the UUID in fstab.sudo vol_id -u sdb1However, the system will not recognise the drive to give me the correct UUID./dev/sdb1: error opening volumePlease help! My brother in law has developed a facebook addiction and is hassling me to get it back!The root partition is fine, it is /home on a seperate hard drive that is the problem. I updated root
Just thought I would post re solving the fsck problem I was having.I have 7.10 installed on hda and decided to install also on hdb.After installing on the slave drive (hdb) I could not boot into Master (hda). After reinstalling 'Grub' on HDA I could not boot into the slave drive. At various times I got the fsck failure and had no success with the live CD or fsck. In the end I noticed a discrepancy in the UUID of the menu list on hda that was different from the menu list on hdb (slave drive). So I decided to change the UUID on the menulist on hda to correspond with the UUID on the slave drive.
When I tried to boot Ubuntu this morning I got the message below. I searched on these forums and I found a thread with a similar issue, but the person with the problem didn't say if the suggested steps resolved his issue. (Suggested steps: either replace UUID with sda name in /etc/fstab, or run something which produces output to verify against the UUID value in fstab, but no explanation of why to pick one or the other)Should I follow the steps suggested in this thread?THANKS!Here's the "tail end" of the messages I received from Ubuntu during bootup:Quote:
So I upgrade Jaunty Jackalope and when I try and load the deafult kernel it hangs on a black screen.when I try to boot by selecting a recovery version of the kernel.. ubuntu 9.04, kernel 2.6.28-11(generic) (recovery mode)It says :/dev/sda1 contains a file system with errors, check forced.It then does a check, dies with exit status 4, and then asks me for my root password for maintenance. I enter it and then it says that the password is invalid. Is this the same root password that I sudo with?? Is this some mysterious new password that was set up separately. I am unable to get past this point a
Well after a failed upgrade from 8.10 to 9.04 (http://ubuntuforums.org/showthread.php?t=1170648) I went back to 8.10. Now I'm having trouble with hangs on startup. Sometimes fixed by just hitting a key once, but sometimes I'll need to hold it down constantly. When the scheduled FSCK comes up, it hangs and will sometimes pick up if I hit a key. However, if I decide to skip the check it could take up to 10mins for the esc to register. If I run the check from a livecd then it doesn't pick up any issues, and it no longer tries to do one on startup. I'd rather not have to use a livecd everytime the
I've just installed Ubuntu 9.10 64bit on my new server and then built a 32bit image. When I try and boot my thin clients I get the following error on VT7:mount: according to mtab, aufs is already mount on /mountall: mount / [416] terminated with status 1.mount: according to mtab, none is already mounted on /procmountall: mount /proc [409] terminated with status 1.mount: according to mtab, none is already mounted on /sysmountall: mount /sys [410] terminated with status 1.mount: according to mtab, udev is already mounted on /devmountall: mount /dev [411] terminated with status 1.mount: according
My system started to act weird (Thunderbird wouldn't let me compose new mail messages), so I backed up and restarted my system. During the bootup, I was greeted with:/dev/hda1 contains a f ile system with errors, check forced./dev/hda1Inodes that were part of a corrupted orphan linked list found./dev/hda1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)fscked died with exit status 4.[fail]* An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be performed, then the system restarted. The fsck should be performed in maintence mode
Posting this here in the hopes that it might help others who got bitten by this.I just upgraded my workstation in place from gutsy to hardy, and most things went pretty smoothly until the reboot, when I got dumped into a shell with an fsck failure on the partition where I store my nightly backups for all my systems. It turned out that the device where the partition lives had been renamed by Ubuntu. What used to be /dev/hdb was now /dev/sdb. Once I realized what had happened, all I needed to do was edit /etc/fstab and change /dev/hdb4 to /dev/sdb4 and remount the partition.HTH.