Programming &/Server & OS

아....하드 디스크 오류 ㅡ.ㅡ;;; EXT3-fs error (device sdb1)

마법눈 2010. 2. 11. 10:35
훔...
이건 뭥미..ㅡ.ㅡ
뭐가 에러가 주루륵 떴다 ㅡ.ㅡ

Feb  5 09:24:26 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:24:26 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:24:26 intsamba kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0
Feb  5 09:24:26 intsamba kernel: Aborting journal on device sdb1.
Feb  5 09:24:26 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:24:26 intsamba kernel: end_request: I/O error, dev sdb, sector 16519
Feb  5 09:24:26 intsamba kernel: Buffer I/O error on device sdb1, logical block 2057
Feb  5 09:24:26 intsamba kernel: lost page write due to I/O error on sdb1
Feb  5 09:24:26 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:24:26 intsamba kernel: end_request: I/O error, dev sdb, sector 63
Feb  5 09:24:26 intsamba kernel: Buffer I/O error on device sdb1, logical block 0
Feb  5 09:24:26 intsamba kernel: lost page write due to I/O error on sdb1
Feb  5 09:24:26 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:24:26 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:24:26 intsamba kernel: ext3_abort called.
Feb  5 09:24:26 intsamba kernel: EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted journal
Feb  5 09:24:26 intsamba kernel: Remounting filesystem read-only
Feb  5 09:30:52 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:30:52 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:30:52 intsamba kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0
Feb  5 09:30:52 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:30:52 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:30:53 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:30:53 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:30:53 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:30:53 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:30:55 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:30:55 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:31:00 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:31:00 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:31:02 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:31:02 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:32:09 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:32:09 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:32:13 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:32:13 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:33:16 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:33:16 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:33:30 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:33:30 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:35:26 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:35:26 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:35:26 intsamba kernel: EXT3-fs error (device sdb1): ext3_find_entry: reading directory #2 offset 0
Feb  5 09:35:26 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:35:26 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:35:29 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:35:29 intsamba kernel: end_request: I/O error, dev sdb, sector 16471
Feb  5 09:37:41 intsamba kernel: sd 0:0:1:0: SCSI error: return code = 0x00040000
Feb  5 09:37:41 intsamba kernel: end_request: I/O error, dev sdb, sector 16471

혹시나해서 
$ ls
ls: reading directory .: I/O error

뭐라는건지...ㅡ.ㅡ

umount 하고 다시 마운트 시도

$ mount -t ext3 /dev/sdb1 /data1
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

갈수록 태산이다 ㅡ.ㅡ

오잉

$ fdisk -l

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   83  Linux
/dev/sda2              14        9729    78043770   8e  Linux LVM

Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           1       60801   488384001   83  Linux

Disk /dev/sdd: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *           1       60801   488384001   83  Linux

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *           1      121601   976760001   83  Linux

Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *           1      121601   976760001   83  Linux

Disk /dev/sdg: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1               1       77825   625129281    7  HPFS/NTFS


sdb1 이 어디갔냐 ㅡ.ㅡ

미쳐

훔...참 이상한일도 다 있다...

먼가 에러가 생기면서 인식오류가 발생한것으로 보인다.

서버 가이드쪽에 먼가 연결부분이 안 좋았나보다

다시 확인하고 재부팅하니 인식이 됐다 ㅡ.ㅡ