Ubuntu This forum is for the discussion of Ubuntu Linux. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-05-2006, 11:53 AM
|
#1
|
Senior Member
Registered: Mar 2006
Location: India
Distribution: Fedora
Posts: 1,562
Rep:
|
fsck trouble on Edgy
Hi guys,
I had FC5,Debian Etch and Ubuntu 6.10 and was booting from the grub of ubuntu. Then i installed FC6 over debian and now boot from fedora grub. But whenever i boot ubuntu, i get an fsck error asking me to give root password for maintenance or hit Ctrl-D to continue. After i hit Ctrl-D it boots and works normal.
The log from /var/log/fsck/checkfs
Code:
Log of fsck -C -R -A -a
Sun Nov 5 20:40:35 2006
fsck 1.39 (29-May-2006)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
430:4e/52, 431:54/65, 432:4c/6d, 433:44/6f, 434:52/76, 435:20/65, 436:69/20
, 437:73/64, 438:20/69, 439:6d/73, 440:69/6b, 442:73/20, 443:69/6f
, 444:6e/72, 445:67/20, 446:ff/6f, 447:0d/74, 448:0a/68, 449:44/65
, 450:69/72, 451:73/20, 452:6b/6d, 453:20/65, 454:65/64, 455:72/69
, 456:72/61, 457:6f/2e, 458:72/ff, 459:ff/0d, 460:0d/0a, 461:0a/44
, 462:50/69, 463:72/73, 464:65/6b, 465:73/20, 466:73/65, 467:20/72
, 468:61/72, 469:6e/6f, 470:79/72, 471:20/ff, 472:6b/0d, 473:65/0a
, 474:79/50, 475:20/72, 476:74/65, 477:6f/73, 478:20/73, 479:72/20
, 480:65/61, 481:73/6e, 482:74/79, 483:61/20, 484:72/6b, 485:74/65
, 486:0d/79, 487:0a/20, 488:00/74, 489:00/6f, 490:00/20, 491:00/72
, 492:00/65, 493:00/73, 494:00/74, 495:00/61, 496:00/72, 497:00/74
, 498:00/0d, 499:00/0a, 506:bf/cb, 507:cc/d8
Not automatically fixing this.
/dev/sda1: 24827 files, 894368/1309017 clusters
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/sda5: 49140 files, 876161/1309017 clusters
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/sda6: 3421 files, 1247194/1310160 clusters
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/sda7: 8439 files, 1242863/1310160 clusters
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/dev/sda8: 1258 files, 1849419/1902842 clusters
/dev/sdb14: Superblock last write time is in the future. FIXED.
/dev/sdb14: clean, 33148/1291808 files, 1031729/2580432 blocks
/: Superblock last write time is in the future. FIXED.
/: clean, 17540/2621440 files, 773202/2620595 blocks
fsck.ext3: Unable to resolve 'UUID=3610b796-07ff-40b0-9184-3634e2385648'
fsck.ext3: Unable to resolve 'UUID=1d597f44-f70d-4760-b372-f314447c8b2f'
/home: Superblock last write time is in the future. FIXED.
/home: clean, 122650/2621440 files, 1778694/2620595 blocks
/usr: Superblock last write time is in the future. FIXED.
/usr: clean, 237729/2621440 files, 1889647/2620595 blocks
fsck.ext3: Unable to resolve 'UUID=9dfd61e0-eb02-4220-9a53-51ae894f24b5'
fsck died with exit status 8
Sun Nov 5 20:34:21 2006
----------------
My fstab details
Code:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdb13
UUID=a0e99ce0-ea09-4a50-a610-381c7a55fbd0 / ext3 defaults,errors=remount-ro 0 1
# /dev/sdb14
UUID=49840b47-a6c3-43b5-9aed-a83eea8c69c0 /home ext3 defaults 0 2
# /dev/sda1
UUID=A04B-70FA /media/sda1 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda5
UUID=1C3C-1D99 /media/sda5 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda6
UUID=98D7-8F3D /media/sda6 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda7
UUID=64E8-3636 /media/sda7 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sda8
UUID=94F3-062B /media/sda8 vfat defaults,utf8,umask=007,gid=46 0 1
# /dev/sdb1
UUID=18f8301f-df7e-4a02-b814-99cf62306c98 /media/sdb1 ext3 defaults 0 2
# /dev/sdb10
UUID=3610b796-07ff-40b0-9184-3634e2385648 /media/sdb10 ext3 defaults 0 2
# /dev/sdb11
UUID=1d597f44-f70d-4760-b372-f314447c8b2f /media/sdb11 ext3 defaults 0 2
# /dev/sdb6
UUID=305985a2-c26d-4ce3-b6d1-975c97587bca /media/sdb6 ext3 defaults 0 2
# /dev/sdb7
UUID=2bff2bee-21cf-4bd8-b77d-8d9358959079 /media/sdb7 ext3 defaults 0 2
# /dev/sdb8
UUID=9dfd61e0-eb02-4220-9a53-51ae894f24b5 /media/sdb8 ext3 defaults 0 2
# /dev/sdb12
UUID=da4ae250-29ed-47f9-ad9a-8d3749e8163f none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hdc /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/ /media/floppy0 auto rw,user,noauto 0 0
Why has my fstab changed ??  I don't understand a thing here. Shall i remove these UUID's and proceed as normal?
Also why does ubuntu fsck everytime the system starts? It did even when i had debian.
HELP
Thanks
|
|
|
11-05-2006, 12:05 PM
|
#2
|
Member
Registered: Feb 2004
Posts: 489
Rep: 
|
The thing is, since you formatted it with Fedora, the UUID changed. In fact, I've done just the same you did. To fix it, I disabled fsck from Ubuntu by changing the last number (a 2 in this case) to a 0.
You could also substitute the UUID with the partition and try to see if it works.
|
|
|
11-11-2006, 07:51 PM
|
#3
|
Member
Registered: Jan 2006
Location: Colorado USA
Distribution: Debian AMD 64 Testing, Sabayon Linux x86-64 3.4, and Ubuntu AMD 64 7.04
Posts: 235
Rep:
|
You are correct. If I edit /etc/fstab to remove the UUID entries and change to device [ie. /dev/hdaX] then it boots normally while still running fsck on the other partitions. My current /etc/fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda2 -- converted during upgrade to edgy
# /dev/hda1 -- converted during upgrade to edgy
/dev/hda1 /media/hda1 ext3 defaults 0 2
# /dev/hda6 -- converted during upgrade to edgy
/dev/hda6 /media/hda6 ext2 defaults 0 2
# /dev/hda7 -- converted during upgrade to edgy
/dev/hda7 /media/hda7 reiserfs defaults 0 2
# /dev/hda5 -- converted during upgrade to edgy
/dev/hda5 none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
UUID=4f326857-460c-4ad7-990d-921916a9e719 / ext3 defaults 1 1
I have also learned that changing the last default # from 2 to 0 means that it then WILL NOT run fsck oin the other partitions. I have not found a way to get it to not run fsck on my primary OS which is currently /dev/hda2.

Last edited by Red Knuckles; 11-11-2006 at 07:55 PM.
|
|
|
All times are GMT -5. The time now is 05:29 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|