Fsck logs in Mint?

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read this

Fsck logs in Mint?

Postby yuri21 on Wed Aug 15, 2007 1:48 am

Hmmm... does anyone know where to check for fsck logs in Linux-mint? So far, I've only found a small handful under /var/log/fsck

The reason I'm looking for them is 'cos Linux-mint seems to die whenever I boot up into Linux with my eSata external hdd turned off. It seems to die after fsck runs and fails, kicking me to bash.

I never had this issue under Ubuntu so I'm a little worried.
yuri21
Level 2
Level 2
 
Posts: 68
Joined: Wed Jul 25, 2007 4:11 am

Linux Mint is funded by ads and donations.
 

Postby yuri21 on Wed Aug 15, 2007 3:02 am

Okay, I found the logs but I still have no idea why this issue keeps happening. Shouldn't Mint be able to auto-detect if a hdd was removed and not complain about it?

Checkfs logs:
Log of fsck -C -R -A -a
Wed Aug 15 15:02:29 2007

fsck 1.40-WIP (14-Nov-2006)
/dev/sda2: clean, 28089/5128192 files, 9262798/10239429 blocks
/dev/sda3: clean, 75128/2562240 files, 2943116/5120718 blocks
/dev/sdc6: clean, 136959/3759264 files, 4382404/7503872 blocks
/dev/sdb1: clean, 13/9781248 files, 367367/19537040 blocks
fsck.ext3: Unable to resolve 'UUID=b340d62d-5908-48e3-bb52-79bcdcaf8892'

fsck.ext3: Unable to resolve 'UUID=2426e230-e6c1-4577-aec6-bb343a6350fe'

fsck died with exit status 8

Wed Aug 15 15:02:29 2007
----------------


Fstab:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sdd7
UUID=1250bfbf-0a1c-467e-9abe-0433ce068c99 / ext3 defaults,errors=remount-ro 0 1
# /dev/sdd6
UUID=c46971c0-dc7f-4447-9a8a-0f79eae92242 /home ext3 defaults 0 2
# /dev/sda1
UUID=5C4823D34823AB2A /media/sda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sda2
UUID=818924b7-0379-47ba-b116-c8a4c8c736f9 /media/sda2 ext3 defaults 0 2
# /dev/sda3
UUID=40e6aec7-192d-4e29-b1aa-0ab6419c0314 /media/sda3 ext3 defaults 0 2
# /dev/sda4
UUID=2E54B5B654B5815F /media/sda4 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/sdb1
UUID=b340d62d-5908-48e3-bb52-79bcdcaf8892 /media/sdb1 ext3 defaults 0 2
# /dev/sdb2
UUID=2426e230-e6c1-4577-aec6-bb343a6350fe /media/sdb2 ext3 defaults 0 2
# /dev/sdc1
UUID=04188596-bf72-4175-a32e-66788620fabb /media/sdc1 ext3 defaults 0 2
# /dev/sdd5
UUID=47cf4074-3968-4aa2-8ddd-67d39f19d6e3 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0


/dev/disk output:

hidan@asami:~$ sudo ls -al /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 240 2007-08-15 23:05 .
drwxr-xr-x 6 root root 120 2007-08-15 23:05 ..
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 04188596-bf72-4175-a32e-66788620fabb -> ../../sdc1
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 1250bfbf-0a1c-467e-9abe-0433ce068c99 -> ../../sdd7
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 2426e230-e6c1-4577-aec6-bb343a6350fe -> ../../sdb2
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 2E54B5B654B5815F -> ../../sda4
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 40e6aec7-192d-4e29-b1aa-0ab6419c0314 -> ../../sda3
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 47cf4074-3968-4aa2-8ddd-67d39f19d6e3 -> ../../sdd5
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 5C4823D34823AB2A -> ../../sda1
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 818924b7-0379-47ba-b116-c8a4c8c736f9 -> ../../sda2
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 b340d62d-5908-48e3-bb52-79bcdcaf8892 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2007-08-15 23:05 c46971c0-dc7f-4447-9a8a-0f79eae92242 -> ../../sdd6
yuri21
Level 2
Level 2
 
Posts: 68
Joined: Wed Jul 25, 2007 4:11 am

Postby Husse on Wed Aug 15, 2007 1:11 pm

I don't know which i s your external disk, but I don't need to know that to see what's wrong
It's UUID :(
UUID is supposed to be a Universal IDentifier, and it is, but it has some serious drawbacks. The UUID of a disk can change if the disk/partition changes in some respect - and if that happens to a disk/partition in fstab - which does not change correspondingly you get your problem
Change
Code: Select all
# /dev/sdb1
UUID=b340d62d-5908-48e3-bb52-79bcdcaf8892 /media/sdb1 ext3 defaults 0 2
to
Code: Select all
# /dev/sdb1
/dev/sdb1 /media/sdb1 ext3 defaults 0 2
and in the same way change
Code: Select all
# /dev/sdb2
UUID=2426e230-e6c1-4577-aec6-bb343a6350fe /media/sdb2 ext3 defaults 0 2
to
Code: Select all
# /dev/sdb2
/dev/sdb2 /media/sdb2 ext3 defaults 0 2

The long UUID is just another way of saying /dev/sdb2 or /dev/sdb1 or whatever...
It is irritating, but on the other hand you don't change your partitions too often - and it does not happen just because you remove an external hdd connected by USB. If you use E-SATA and the disk is in fstab it's another story - I'm actually uncertain as to what happens and cannot test
If these partitions are your external disk connected by E-SATA and you still get the problem after the change above you have tested :)
Image
Don't fix it if it ain't broken, don't break it if you can't fix it
Husse
Level 21
Level 21
 
Posts: 19710
Joined: Sun Feb 11, 2007 7:22 am
Location: Near Borås Sweden

Postby yuri21 on Thu Aug 16, 2007 1:54 am

Yay!!!! That worked!!!:D

Yes ... sdb1 and sdb2 were my ext partitions. :)

Now, I just need to figure out how to get eSata hotplugging working and it should be fine. :)
yuri21
Level 2
Level 2
 
Posts: 68
Joined: Wed Jul 25, 2007 4:11 am


Return to Newbie Questions

Who is online

Users browsing this forum: Bing [Bot], dasWindmill, Google Feedfetcher, Interest, jloyzaga, myedroid and 22 guests