| Author |
Message |
|
|
|
Post subject: "Checking file systems ..../dev/hdb6: clean" but
 Posted: Jan 01, 2008 - 05:53 PM
|
|
Joined: Dec 29, 2007
Posts: 22
Location: Tyrnävä, Finland
Status: Offline
|
|
I installed sidux 2007-04 200711212102243 Eros KDE full on my ide harddisk hdb. Windows is on hda and I have also a serial ATA harddisk for windows and my linux's.
After editing /boot/grub/menu.lst of an other linux I started sidux. The procedure stoped on the root terminal and I was asked to repair the hard disk. But two other linux's start without any problems. Also the root file system of sidux "/dev/hdb6: clean" but the checking of /dev/hdb1 produced failed (code 9). The logfile
Code:
Log of fsck -C -R -A -a
Tue Jan 1 12:58:08 2008
fsck 1.40.2 (12-Jul-2007)
fsck.ext3: Unable to resolve 'UUID=c775e35f-e9c0-4404-bfca-0264c3703cde'
/dev/hdb1: Adding dirhash hint to filesystem.
/dev/hdb1 was not cleanly unmounted, check forced.
/12: clean, 132990/5124480 files, 3194155/5120718 blocks
/dev/hdb1: 34/26104 files (5.9% non-contiguous), 13590/104388 blocks
/dev/hdb2: clean, 111357/2812544 files, 810919/5614717 blocks
/1: clean, 119597/3204992 files, 867633/6399886 blocks
fsck died with exit status 9
Tue Jan 1 12:58:09 2008
----------------
ukki@ukinminttu:~$
After that checking "/dev/hdb2: clean".
Unfortunately I have not previous experiences of how to repair hard disk. What to do?
I try to include a picture of the display. |
|
|
| |
|
|
|
 |
|
|
|
Post subject: RE: "Checking file systems ..../dev/hdb6: clean" b
Posted: Jan 01, 2008 - 07:54 PM
|
|
Team Member
Joined: Nov 27, 2006
Posts: 1959
Location: underworld
Status: Offline
|
|
| Can you post the output of (as user)
Code:
ls -l /dev/disk/by-uuid
and your fstab |
_________________
Can God be sued for not putting DRM into DNA of people letting them infringe copyright ?
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jan 02, 2008 - 12:20 PM
|
|
Joined: Dec 29, 2007
Posts: 22
Location: Tyrnävä, Finland
Status: Offline
|
|
Now the second attempt to start sidux. The result is the same: "Please repair the file system manually", but this time failed code 8 .
I forgot to save logging but here is "ls -l dev/disk/by-uuid"
Quote:
total 0
lrwxrwxrwx 1 root root 10 Jan 2 2008 12BF-2F9B -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jan 2 2008 2f531cd1-1783-427f-a226-97af278359df -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 2 2008 356b6c6e-8993-430d-be68-a3ccb1518f51 -> ../../hdb7
lrwxrwxrwx 1 root root 10 Jan 2 2008 45eac2df-e608-4a84-aeb3-30d9421c8058 -> ../../hdb2
lrwxrwxrwx 1 root root 10 Jan 2 2008 633a1d87-8d8c-4ad7-bfc2-96e2ed358a4f -> ../../hdb1
lrwxrwxrwx 1 root root 10 Jan 2 2008 6C680A216809EAA2 -> ../../hda1
lrwxrwxrwx 1 root root 10 Jan 2 2008 6E43510937F4BD0C -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 2 2008 78ed7a5d-fc1c-4688-a714-ea5d80c368f3 -> ../../hdb5
lrwxrwxrwx 1 root root 10 Jan 2 2008 b505afca-fd03-4fa1-86d4-9c456b7d4ee9 -> ../../hdb6
lrwxrwxrwx 1 root root 10 Jan 2 2008 df2f89bd-1eb0-4823-9004-8d41ccdebcec -> ../../sda2
and /etc/fstab, I will skip some comments
Quote:
# <filesystem> <mountpoint> <type> <options> <dump> <pass>
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part6, /dev/hdb6
UUID=b505afca-fd03-4fa1-86d4-9c456b7d4ee9 / ext3 defaults,noatime,errors=remount-ro 0 1
# automatically added, /dev/dm-0
UUID=c775e35f-e9c0-4404-bfca-0264c3703cde /media/dm-0 ext3 auto,users,exec,noatime 0 2
# automatically added, /dev/dm-1
UUID=d6562de2-0d29-44d6-98d1-f8b0777c42af none swap sw 0 0
# automatically added, ST380011A_5JVGHWEZ-part1, /dev/hda1
UUID=6C680A216809EAA2 /media/hda1 ntfs auto,users,exec,ro,dmask=0022,fmask=0133,nls=utf8 0 0
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part1, /dev/hdb1
UUID=633a1d87-8d8c-4ad7-bfc2-96e2ed358a4f /media/hdb1 ext2 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part2, /dev/hdb2
UUID=45eac2df-e608-4a84-aeb3-30d9421c8058 /media/hdb2 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part5, /dev/hdb5, LABEL=\x2f1
UUID=78ed7a5d-fc1c-4688-a714-ea5d80c368f3 /media/hdb5 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part7, /dev/hdb7
UUID=356b6c6e-8993-430d-be68-a3ccb1518f51 none swap sw 0 0
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part1, /dev/sda1
UUID=6E43510937F4BD0C /media/sda1 ntfs auto,users,exec,ro,dmask=0022,fmask=0133,nls=utf8 0 0
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part2, /dev/sda2
UUID=df2f89bd-1eb0-4823-9004-8d41ccdebcec none swap sw 0 0
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part3, /dev/sda3, LABEL=\x2f12
UUID=2f531cd1-1783-427f-a226-97af278359df /media/sda3 ext3 auto,users,exec,noatime 0 2
# automatically added, GIGABYTE_GO-W1623A
/dev/cdrom /media/cdrom udf,iso9660 user,noauto 0 0
# automatically added, LTN526
/dev/cdrom1 /media/cdrom1 udf,iso9660 user,noauto 0 0
# automatically added
/dev/fd0 /media/fd0 auto rw,user,noauto 0 0
# temporary filesystem in virtual memory
tmpfs /tmp tmpfs defaults 0 0
I tried to include a photo of the display, 91,2 kt, but did not succeed in it 
I suppose it's best I try to install sidux the second time on an other hard disk, /dev/sda. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jan 02, 2008 - 01:07 PM
|
|
Joined: Jan 16, 2007
Posts: 462
Status: Offline
|
|
| Beore you install, check the md5sum of the cd:
Code:
md5sum -b /dev/cdrom
|
|
|
| |
|
|
|
|
|
|
|
Post subject: "Checking file systems ..../dev/hdb6: clean" but
Posted: Jan 02, 2008 - 03:54 PM
|
|
Joined: Dec 29, 2007
Posts: 22
Location: Tyrnävä, Finland
Status: Offline
|
|
Later I wrote: "... installing sidux on sda4 went well". I also succeeded in dist-upgrading the installation by using smxi. I was happy with my new sidux 
Then I started to test Zenwalk 4.8 and installed it to my computer. It worked well as well ass my other linuxes. I need secure and usable linux's because my hobby is to assemble microcomputers using spare parts and configure them for kids and old persons.
But now again when I started sidux failed (code 8 ) again appeared. The log-listing:
Code:
root@siduxbox:~# cat /var/log/fsck/checkfs
Log of fsck -C -R -A -a
Sun Jan 6 07:46:23 2008
fsck 1.40.3 (05-Dec-2007)
/dev/hdb1: clean, 34/26104 files, 13590/104388 blocks
/dev/hdb2: clean, 111606/2812544 files, 819181/5614717 blocks
/12: clean, 133008/5124480 files, 3194556/5120718 blocksail
/1: clean, 115742/3204992 files, 912449/6399886 blocks
fsck.ext3: Unable to resolve 'UUID=b505afca-fd03-4fa1-86d4-9c456b7d4ee9'
fsck died with exit status 8
Sun Jan 6 07:46:24 2008
----------------
root@siduxbox:~#
Now after starting X and login in:
Code:
root@siduxbox:~# ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 287ef99b-752e-47b3-b153-8834ec5994d9 -> ../../sda2
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 2f531cd1-1783-427f-a226-97af278359df -> ../../sda3
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 45eac2df-e608-4a84-aeb3-30d9421c8058 -> ../../hdb2
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 633a1d87-8d8c-4ad7-bfc2-96e2ed358a4f -> ../../hdb1
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 6C680A216809EAA2 -> ../../hda1
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 6E43510937F4BD0C -> ../../sda1
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 78ed7a5d-fc1c-4688-a714-ea5d80c368f3 -> ../../hdb5
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 793fdbe6-8f13-4d82-9412-e425ed913d45 -> ../../hdb6
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 d56cf48c-2f70-4e51-86d5-c68d501d2063 -> ../../sda4
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 ea7c2ad2-25c8-4a1b-b72b-c4c4b0e7dee7 -> ../../hdb7
root@siduxbox:~#
And the fstab:
Code:
root@siduxbox:~# cat /etc/fstab
# /etc/fstab - static information about the filesystems - fstab(5)
#
# /etc/fstab is only read by programs, and not written; it is the duty of the
# system administrator to properly maintain this file.
#
# Instead of giving the device explicitly, one may indicate the filesystem
# that is to be mounted by its UUID or VOLUME label. This will make the
# system more robust: adding or removing a disk changes the disk device name
# but not the filesystem UUID or VOLUME label.
#
# <filesystem> <mountpoint> <type> <options> <dump> <pass>
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part4, /dev/sda4
UUID=d56cf48c-2f70-4e51-86d5-c68d501d2063 / ext3 defaults,noatime,errors=remount-ro 0 1
# automatically added, ST380011A_5JVGHWEZ-part1, /dev/hda1
UUID=6C680A216809EAA2 /media/hda1 ntfs auto,users,exec,ro,dmask=0022,fmask=0133,nls=utf8 0 0
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part1, /dev/hdb1
UUID=633a1d87-8d8c-4ad7-bfc2-96e2ed358a4f /media/hdb1 ext2 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part2, /dev/hdb2
UUID=45eac2df-e608-4a84-aeb3-30d9421c8058 /media/hdb2 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part5, /dev/hdb5, LABEL=\x2f1
UUID=78ed7a5d-fc1c-4688-a714-ea5d80c368f3 /media/hdb5 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part6, /dev/hdb6
UUID=b505afca-fd03-4fa1-86d4-9c456b7d4ee9 /media/hdb6 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part7, /dev/hdb7
UUID=356b6c6e-8993-430d-be68-a3ccb1518f51 none swap sw 0 0
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part1, /dev/sda1
UUID=6E43510937F4BD0C /media/sda1 ntfs auto,users,exec,ro,dmask=0022,fmask=0133,nls=utf8 0 0
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part2, /dev/sda2
UUID=df2f89bd-1eb0-4823-9004-8d41ccdebcec none swap sw 0 0
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part3, /dev/sda3, LABEL=\x2f12
UUID=2f531cd1-1783-427f-a226-97af278359df /media/sda3 ext3 auto,users,exec,noatime 0 2
# automatically added, GIGABYTE_GO-W1623A
/dev/cdrom /media/cdrom udf,iso9660 user,noauto 0 0
# automatically added, LTN526
/dev/cdrom1 /media/cdrom1 udf,iso9660 user,noauto 0 0
# automatically added
/dev/fd0 /media/fd0 auto rw,user,noauto 0 0
# temporary filesystem in virtual memory
tmpfs /tmp tmpfs defaults 0 0
root@siduxbox:~#
...........................
Is there somewere a config file which I could edit to stop the unnecessary cecking  |
|
|
| |
|
|
|
|
|
|
|
Post subject: Re: "Checking file systems ..../dev/hdb6: clean" b
Posted: Jan 10, 2008 - 07:00 AM
|
|
Joined: Dec 29, 2007
Posts: 22
Location: Tyrnävä, Finland
Status: Offline
|
|
|
fossiili wrote:
(the) config file which I could edit to stop the unnecessary cecking
is probably /etc/fstab. I have a book: "DebianGNU/Linux 3.1 Bible" by Benjamin Mako Hill and others, but I could not find anything about fstab there. Also earlyer I have found that 640 page book useless. Any good book about Debian 4?
Then I looked at "A Practical Guide to RH Linux" by Mark G. Sobell and from there I found a description of the columns of fstab and column 6 deals Fsck:
Quote:
Specifies the order in which fsck checks filesystems. Root (/) should have 1 in this column. Filesystems that are mounted to a directory just below the root directory should have 2 ... Filesystems ... that do not need to be checked ... should have a 0 ,
I suppose I could try to solve the unnecessary fsck problem (a bug?) by editing fstab. A part of it:
Code:
# /etc/fstab - static information about the filesystems - fstab(5)
.......
# <filesystem> <mountpoint> <type> <options> <dump> <pass>
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part4, /dev/sda4
UUID=d56cf48c-2f70-4e51-86d5-c68d501d2063 / ext3 defaults,noatime,errors=remount-ro 0 1
.............
.......
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part5, /dev/hdb5, LABEL=\x2f1
UUID=78ed7a5d-fc1c-4688-a714-ea5d80c368f3 /media/hdb5 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part6, /dev/hdb6
UUID=b505afca-fd03-4fa1-86d4-9c456b7d4ee9 /media/hdb6 ext3 auto,users,exec,noatime 0 2
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part7, /dev/hdb7
UUID=356b6c6e-8993-430d-be68-a3ccb1518f51 none swap sw 0 0
.........
............
I suppose the problematic partitions are on SAMSUNG_SV1604N. I do not have any interest to mount any partition on SAMSUNG_SV1604N to sidux. Can I simply delete those lines in /etc/fstab |
|
|
| |
|
|
|
|
|
|
|
Post subject: Re: "Checking file systems ..../dev/hdb6: clean" b
Posted: Jan 11, 2008 - 02:45 PM
|
|
Joined: Dec 02, 2006
Posts: 1687
Location: Germany / NRW
Status: Offline
|
|
You may delete those lines ( I would not, because there are other options )
1)
You may change "auto" to "noauto" for all partitions you you like. This prevents those partitions from being mounted automaticly but you could access them after mounting them manually.
2)
Alternativly, you may comment the config line, i.e "#UUID=...." instead of "UUID=...." . I this case you can mount those partitions, too, but not as easily as with the first option. |
|
|
| |
|
|
|
|
|
|
|
Post subject: RE: Re: "Checking file systems ..../dev/hdb6: clean&quo
Posted: Jan 12, 2008 - 10:14 PM
|
|
Team Member
Joined: Nov 27, 2006
Posts: 1959
Location: underworld
Status: Offline
|
|
| Your ls -l /dev/disk/by-uuid output says that hdb6 is
Code:
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 793fdbe6-8f13-4d82-9412-e425ed913d45 -> ../../hdb6
your fstab reads it as
Code:
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part6, /dev/hdb6
UUID=b505afca-fd03-4fa1-86d4-9c456b7d4ee9 /media/hdb6 ext3 auto,users,exec,noatime 0 2
so change your fstab to read
Code:
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part6, /dev/hdb6
UUID=793fdbe6-8f13-4d82-9412-e425ed913d45 /media/hdb6 ext3 auto,users,exec,noatime 0 2
Your ls -l /dev/disk/by-uuid output says that hdb7 is
Code:
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 ea7c2ad2-25c8-4a1b-b72b-c4c4b0e7dee7 -> ../../hdb7
so change your fstab to read
Code:
# automatically added, SAMSUNG_SV1604N_0654J1FWB51759-part7, /dev/hdb7
UUID=ea7c2ad2-25c8-4a1b-b72b-c4c4b0e7dee7 none swap sw 0 0
Your ls -l /dev/disk/by-uuid output says that sda2 is
Code:
lrwxrwxrwx 1 root root 10 2008-01-06 09:46 287ef99b-752e-47b3-b153-8834ec5994d9 -> ../../sda2
so change your fstab to read
Code:
# automatically added, Maxtor_6Y120M0-Y46YPKZE-part2, /dev/sda2
UUID=287ef99b-752e-47b3-b153-8834ec5994d9 none swap sw 0 0
Reboot, post any errors |
_________________
Can God be sued for not putting DRM into DNA of people letting them infringe copyright ?
|
| |
|
|
|
|
|
|
|
Post subject: RE: Re: "Checking file systems ..../dev/hdb6: clean&
Posted: Jan 13, 2008 - 06:50 AM
|
|
Joined: Dec 29, 2007
Posts: 22
Location: Tyrnävä, Finland
Status: Offline
|
|
Thank you very much for your kind advice! I'll print it, read it carefully and apply. This installation of sidux is only temporary so I can excperiment freely and learn. Later I will install sidux x86_64 on my computer. Before that I must "reset" the situation in all of my 3 hard disks. Recently I have WindowsXP
and 3 linuxe's beside sidux: Fedora 8, Linux Mint 4, and Mandriva 8. Already Mandriva refused to start for the sake of some confusion on the hard disks.
But first I try to proceed with the recent installations andf I tell later what happens. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jan 13, 2008 - 07:33 AM
|
|
Joined: Dec 05, 2006
Posts: 1022
Location: Wiesbaden, Germany
Status: Offline
|
|
|
fossiili wrote:
I tried to include a photo of the display, 91,2 kt, but did not succeed in it :oops:
Please be aware that attaching files is file size limited and for graphics files also max. pixel limited. So when you try to attach a graphics file and it does not work you can see an error message (not visible directly as it is displayed on top of the response page) and the file is not attached.
Limits see below. |
_________________
Viele Grüße
mylo
sidux [Έρως]@2.6.27-6.slh.4-686 Intel Core2 Duo E6550 @ Cache/Ram 4MB/4GB nVidia G72 7300 2*250GB
scroogle.org: an alternate web search?
|
| |
|
|
|
|
|
|
|
Post subject: Re: "Checking file systems ..../dev/hdb6: clean" b
Posted: Jan 14, 2008 - 06:11 PM
|
|
Joined: Dec 29, 2007
Posts: 22
Location: Tyrnävä, Finland
Status: Offline
|
|
Now I think I understand the file /etc/fstab much better than earlyer! I also learned to use the vi-editor 
Unfortunately nothing else than "brute force" solution worked at the end:
michaa wrote:
You may delete those lines ( I would not, because there are other options )
But now I can start sidux to KDE without first typing Ctrl-D in terminal. Thank you for the advice! |
|
|
| |
|
|
|
|
|
|
|
