[이현철]님이 남기신 글:

> 산이님 답변 감사합니다.
>
>>스왑파티션이
 없는것 자체가 이상하군요. 이 문제 확인해보세요.
> 산이님 말씀 처럼.. 스왑이 없네요..틀림없이
 잡았는데 말이죠..
> 어디 가버렸는지.....
 저도 모르겠습니다.ㅋㅋㅋ

> 
> 그런데 스왑이 중요한지요?.. 제가 이부분을 이해
못해서..
>
>
> 그리고 아래는 dmesg 부분인데..마지막에
 부분에 에러가
> 신경이 쓰이는데요...
>
>
># dmesg
>__________________중략_______________________________________

>EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,5), internal journal
>kjournald starting.  Commit interval 5 seconds
>EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
>EXT3-fs: mounted filesystem with ordered data mode.
>kjournald starting.  Commit interval 5 seconds
>EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,3), internal journal
>EXT3-fs: mounted filesystem with ordered data mode.
>ext3: No journal on filesystem on sd(8,2)
>ip_tables: (C) 2000-2002 Netfilter core team
>Intel(R) PRO/100 Network Driver - version 2.3.43-k1
>Copyright (c) 2004 Intel Corporation
>
>PCI: Found IRQ 11 for device 00:10.0
>PCI: Sharing IRQ 11 with 00:07.2
>divert: allocating divert_blk for eth0
>e100: selftest OK.
>e100: eth0: Intel(R) PRO/100 Network Connection
>  Hardware receive checksums enabled
>  cpu cycle saver enabled
>
>e100: eth0 NIC Link is Up 100 Mbps Full duplex
>via-rhine.c:v1.10-LK1.1.19  July-12-2003  Written by Donald Becker
>  http://www.scyld.com/network/via-rhine.html
>PCI: Assigned IRQ 5 for device 00:11.0
>divert: allocating divert_blk for eth1
>eth1: VIA VT6102 Rhine-II at 0xc800, 00:90:cc:08:bb:a6, IRQ 5.
>eth1: MII PHY found at address 8, status 0x7829 advertising 01e1 Link
45e1.
>eth1: Setting full-duplex based on MII #8 link partner capability of
45e1.
>ext3: No journal on filesystem on sd(8,2)
>EXT3-fs error (device sd(8,6)): ext3_check_descriptors: Block bitmap for group
0
> not in group (block 2553887680)!
>EXT3-fs: group descriptors corrupted !
>EXT3-fs error (device sd(8,6)): ext3_check_descriptors: Block bitmap for group
0
> not in group (block 2553887680)!
>EXT3-fs: group descriptors corrupted !
>EXT3-fs error (device sd(8,6)): ext3_check_descriptors: Block bitmap for group
0
> not in group (block 2553887680)!
>EXT3-fs: group descriptors corrupted !
>----------------------------------------------------------

제생각에는 /dev/sda6 가 스왑파티션이었던것
 같은데 지금 파티션이
뒤죽박죽되어 있는것 같습니다.

umount /dev/sda6 명령어 내리고 /home 안에 data 가 있는지 확인해
보세요.

그리고 스왑파티션은 반드시 꼭 필요하지는 않지만 대부분
시스템은 스왑파티션이 절대적으로 필요합니다. 설치시에 아마
99% 스왑파티션을 잡았을 겁니다.

>
>그리고 /usr/은 있는데 /usr/bin이 없네요...
>

이 파티션도 위의 내용과 비슷해 보이네요. ㅠㅠ

제 생각에는 다른 시스템 하드를 붙여서 파티션 하나하나씩
마운트해봐서
어떤 내용의 데이터가 들어가 있는지 확인하고 마운트
포인트를 잡으면
될것 같네요. 다른 시스템이 없다면 Linux Linux CD 를 만들어서
하면됩니다.

http://www.frozentech.com/content/livecd.php

에 가면 Live CD 이미지를 받아서 CD로 만들면 됩니다.




>
>
>
>[산이]님이 남기신 글:
>
>>
>>[이현철]님이 남기신 글:
>>
>>>-----------------------------------------
>>>답변자가 기본적으로 참고할 내용입니다.
>>>- 배포판(옵션)    : 
>>>- 커널버전(옵션)
  : 
>>>- 데몬버전(예:apache
 1.3.27) : 
>>>- 데몬설치유형(RPM/컴파일/기타)
 : 
>>>-----------------------------------------
>>>갑자기　어제．　다른　엔지니어가　실수로

>>>움직이는　레드햇　９．０서버에서　

>>>ｆｓｃｋ를　실시한　모양입니다．

>>>그것도．　마운트　되어　있는　파티션을

>>>아래와　같이　말이죠．

>>>
>>># fsck
>>>fsck 1.32 (09-Nov-2002)
>>>e2fsck 1.32 (09-Nov-2002)
>>>
>>>check aborted.
>>>e2fsck 1.32 (09-Nov-2002)
>>>/dev/sda1 is mounted.
>>>
>>>WARNING!!!  Running e2fsck on a mounted filesystem may cause
>>>SEVERE filesystem damage.
>>>
>>>Do you really want to continue (y/n)? yes
>>>
>>>/boot: recovering journal
>>>/boot: clean, 45/130560 files, 36080/522081 blocks
>>>e2fsck 1.32 (09-Nov-2002)
>>>/dev/sda6 is mounted.
>>>
>>>WARNING!!!  Running e2fsck on a mounted filesystem may cause
>>>SEVERE filesystem damage.
>>>
>>>Do you really want to continue (y/n)? yes
>>>
>>>/home: recovering journal
>>>
>>>Group descriptors look bad... trying backup blocks...
>>>fsck.ext3: Invalid argument while checking ext3 journal for /home
>>>e2fsck 1.32 (09-Nov-2002)
>>>/dev/sda3 is mounted.
>>>
>>>WARNING!!!  Running e2fsck on a mounted filesystem may cause
>>>SEVERE filesystem damage.
>>>
>>>Do you really want to continue (y/n)? yes
>>>
>>>/usr: recovering journal
>>>fsck.ext3: Bad magic number in super-block while trying to re-open
/usr
>>>e2fsck: io manager magic bad!
>>>e2fsck 1.32 (09-Nov-2002)
>>>/dev/sda2 is mounted.
>>>
>>>WARNING!!!  Running e2fsck on a mounted filesystem may cause
>>>SEVERE filesystem damage.
>>>
>>>Do you really want to continue (y/n)? yes
>>>
>>>/var: recovering journal
>>>fsck.ext3: Bad magic number in super-block while trying to re-open
/var
>>>e2fsck: io manager magic bad!
>>>
>>>
>>>위　내용을　보면，　／ｖａｒ　랑　／ｈｏｍｅ　두개의�
�파티션에

>>>문제가　발생한것　같아　보이는데요．

>>>
>>>이후에　갑자기　유저들에게서　서버　접속이　안된다고�
�해서보니

>>>／ｖａｒ，　／ｈｏｍｅ　umount
 된　상태였던　모양입니다．

>>>
>>>그래서　그대로　ｒｅｂｏｏｔ을　한것　같은데，

>>>제가　가서보니．　리부팅　후에　ｂｏｏｔ과정에서　파�
�시스템　

>>>체크　부분에

>>>Give root password for maintenance
>>>
>>>(Type Ctrl-d to proceed with normal startup)
>>>
>>>위와　같은　메세지가　나와서．root　패스워드로　로그인�
�에

>>>
>>>(Repair filesystem) 1 #
>>>
>>>상태에서　파티션　정보를　　확인해본　결과

>>>
>>># df -h
>>>Filesystem            Size  Used Avail Use% Mounted on
>>>/dev/sda5             494M  102M  367M  22% /
>>>/dev/sda1             494M   20M  450M   5% /boot
>>>none                  252M     0  252M   0% /dev/shm
>>>/dev/sda3             4.9G  1.5G  3.2G  32% /usr
>>>
>>>
>>># fdisk -l
>>>
>>>Disk /dev/sda: 17.9 GB, 17968398336 bytes
>>>255 heads, 63 sectors/track, 2184 cylinders
>>>Units = cylinders of 16065 * 512 = 8225280 bytes
>>>
>>>   Device Boot    Start       End    Blocks   Id  System
>>>/dev/sda1   *         1        65    522081   83  Linux
>>>/dev/sda2            66       702   5116702+  83  Linux
>>>/dev/sda3           703      1339   5116702+  83  Linux
>>>/dev/sda4          1340      2184   6787462+   f  Win95 Ext'd (LBA)
>>>/dev/sda5          1340      1404    522081   83  Linux
>>>/dev/sda6          1405      2184   6265318+  83  Linux
>>>
>>>
>>
>>swap 파티션이 없네요... 원래 없나요? 없으면
곤란할텐데..
>>
>>
>>># cat /proc/partitions
>>>major minor  #blocks  name     rio rmerge rsect ruse wio wmerge wsect wuse
runni
>>>ng use aveq
>>>
>>>   8     0   17547264 sda 1784 7980 27976 8360 594 1240 5922 63060 0 12350
71420
>>>   8     1     522081 sda1 23 71 188 100 8 3 22 660 0 760 760
>>>   8     2    5116702 sda2 19 58 196 100 0 0 0 0 0 100 100
>>>   8     3    5116702 sda3 442 1068 11426 2360 152 222 2976 13090 0 5850
15450
>>>   8     4          1 sda4 0 0 0 0 0 0 0 0 0 0 0
>>>   8     5     522081 sda5 1282 6693 15950 5660 434 1015 2924 49310 0 9280
54970
>>>   8     6    6265318 sda6 11 49 120 60 0 0 0 0 0 60 60
>>>
>>>파티션은　다　살아　있더군요．

>>>
>>>
>>>마운트를　했을때

>>># mount /dev/sda6 /home
>>>mount: wrong fs type, bad option, bad superblock on /dev/sda6,
>>>       or too many mounted file systems
>>>
>>>
>>>ｆｓｃｋ를　했을때

>>># fsck.ext3 /dev/sda6
>>>e2fsck 1.32 (09-Nov-2002)
>>>Group descriptors look bad... trying backup blocks...
>>>fsck.ext3: Invalid argument while checking ext3 journal for /home
>>>
>>>어느것을　해도　콘솔에서　안돼서　어쩔수　없이　

>>>ｆｓｔａｂ를　아래와　같이　수정후에

>>>
>>>＊수정한　내용으　／ｈｏｍｅ을　코멘트　처리했습니다．

>>>
>>># more /etc/fstab
>>>LABEL=/                 /                       ext3    defaults        1
1
>>>LABEL=/boot             /boot                   ext3    defaults        1
2
>>>none                    /dev/pts                devpts  gid=5,mode=620  0
0
>>>#LABEL=/home             /home                   ext3    defaults        1
2
>>>none                    /proc                   proc    defaults        0
0
>>>none                    /dev/shm                tmpfs   defaults        0
0
>>>LABEL=/usr              /usr                    ext3    defaults        1
2
>>>LABEL=/var              /var                    ext3    defaults        1
2
>>>
>>
>>LABEL 대신 디바이스 이름을 직접 입력해 보세요. 예를
들어
>>LABEL=/usr 를 /dev/sda3 로 고침/
>>
>>
>>>어째든　위와　같이　조치후에　ｒｅｂｏｏｔ해서．

>>>서버를　기동은　어떻게　했습니다．물론　무수한　에러�
�메세지가　

>>>나왔지만요．

>>>
>>>그리고　원격지에서　ｓｓｈ를　통해　작업　할려고　

>>># /etc/init.d/sshd start
>>>하니　／ｖａｒ　안에　필요한　폴더　및　파일이　없다�
�　해서

>>>강제로　만들었습니다．

>>># ls -al /var
>>>total 5
>>>drwxr-xr-x    5 root     root         1024 12月 19 20:52 .
>>>drwxr-xr-x   21 root     root         1024 12月 20 19:15 ..
>>>drwxr-xr-x    2 root     root         1024 12月 19 20:52 empty
>>>drwxr-xr-x    3 root     root         1024 12月 19 20:16 lib
>>>drwxr-xr-x    3 root     root         1024 12月 19 20:52 lock
>>>
>>>기존에　／ｖａｒ　파티션을　별도로　나누어서　사용했�
�데

>>>／ｖａｒ　파티션도　마운트　안되더군요．．

>>>
>>>어째든　제가　필요한　테이타는　／ｈｏｍｅ　안에　테�
�타만　중요해서말이죠．

>>>
>>>ｅ２ｆｓｃｋ를　실행했을경우

>>># e2fsck /dev/sda6
>>>e2fsck 1.32 (09-Nov-2002)
>>>Group descriptors look bad... trying backup blocks...
>>>e2fsck: Invalid argument while checking ext3 journal for /home
>>>
>>># e2fsck /dev/sda2
>>>e2fsck 1.32 (09-Nov-2002)
>>>/var: clean, 1384/640000 files, 25001/1279175 blocks
>>>
>>>＊／ｖａｒ는　괜찮은것　같은데．마운트　해도　아무　�
�이타가　없네요

>>>
>>># mount /dev/sda2 /var1
>>># df -h
>>>Filesystem            Size  Used Avail Use% Mounted on
>>>/dev/sda5             494M  102M  367M  22% /
>>>/dev/sda1             494M   20M  450M   5% /boot
>>>none                  252M     0  252M   0% /dev/shm
>>>/dev/sda3             4.9G  1.5G  3.2G  32% /usr
>>>/dev/sda2             4.9G   20M  4.6G   1% /var1
>>>
>>>
>>># ls -al /var1/
>>>total 29
>>>drwxr-xr-x    3 root     root         4096 12月 19 18:43 .
>>>drwxr-xr-x   21 root     root         1024 12月 20 19:15 ..
>>>drwx------    8 root     root        24576 12月 19 18:43 lost+found
>>>
>>>
>>>
>>>
>>>
>>>슈퍼　블록으로　복구　테스트

>>># e2fsck -b 8193 /dev/sda6
>>>e2fsck 1.32 (09-Nov-2002)
>>>e2fsck: Bad magic number in super-block while trying to open
/dev/sda6
>>>
>>>The superblock could not be read or does not describe a correct ext2
>>>filesystem.  If the device is valid and it really contains an ext2
>>>filesystem (and not swap or ufs or something else), then the
superblock
>>>is corrupt, and you might try running e2fsck with an alternate
superblock:
>>>    e2fsck -b 8193 <device>
>>>
>>>배트불록　체크

>>># e2fsck -cv  /dev/sda6
>>>e2fsck 1.32 (09-Nov-2002)
>>>Group descriptors look bad... trying backup blocks...
>>>e2fsck: Invalid argument while checking ext3 journal for /home
>>>
>>>강제복구　
>>># e2fsck -f  /dev/sda6
>>>e2fsck 1.32 (09-Nov-2002)
>>>Group descriptors look bad... trying backup blocks...
>>>e2fsck: Invalid argument while checking ext3 journal for /home
>>>
>>>
>>>
>>>제가　한것은　여기　까지　인데요．．다　안되더군요．

>>>혹　　복구　가능한　방법이나　제가　놓치것이　있으면�
�말씀　부탁드립니다．

>>>／ｖａｒ　어떻게　될것　같아　보이는데　잘　안되네요�
�쩝．

>>>산이님께　여쭈어　보고　안되면　업체쪽으로　알아볼까�
�하는데요．

>>>
>>
>>스왑파티션이
 없는것 자체가 이상하군요. 이 문제 확인해보세요.
>>/dev/sda6 가 혹시 스왑?
>>
>>/var 디렉토리 구조.
>>
>>cache  db  empty  lib  local  lock  log  mail->spool/mail  nis  opt  preserve  run
 spool  tmp  www  yp
>>
>>퍼미션은 모두 755 이고, /var/tmp 은 1777(drwxrwxrwt)
>>
>>시간이 된다면 다른 서버의 RH9 /var 구조를 그때로 따라서
디렉토리를 만들어 보세요.
>>
>>
>>>
>>>하나　더　여쭈어　볼께요．

>>>현재　아래와　같은　파일이　서버에　있는데　삭제가　�
�되네요．

>>> ls -al
>>>合計 282408
>>>-rw-r--r--    1 root     root            0  5月 15  2006
??暼???????-
>>>
>>>rw-r--r--    1 root     root          191  2月 22  2006 -v
>>>
>>># rm -rf "-v"
>>>
>>>이렇게　해도　삭제　안되고　？？？형태로　생긴파일은�
�삭제해볼려고　해도

>>>
>>># ls  -al 　?*　
>>>형태로　먼저　확인해보면　？　자체가　임이의문자　하�
�로　인식해버리니　다른　파일까지　삭제　되버리니．．

>>>
>>>어떤　좋은　방법이　있을까요？

>>>
>>
>>rm -rf -- "-v"
>>
>>이렇게 옵션이 끝났다는 의미의 하이픈 두개(--)를 넣어주고
지워보세요.
>>
>>
>>
>>
>>>긴　내용　읽어　주셨서　감사합니다．
 
>>
>>======================================== 
>
>======================================== 

========================================