Re: Partição Sumiu
use o testdisk e tente recuperar ela....
2007/11/12, Adriano <aeuclides@yahoo.com.br>:
> Pessoal
>
> Não sei o q ocorreu, mas tenho um servidor com 4
> partições. Por obra do divino uma partição sumiu.
> Notem que a partição /apl não consta e estava definida
> em /dev/sdb1 Como pode ser constatado no fstab.
>
> Como está agora:
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda3 2.4G 1.7G 653M 73% /
> /dev/sda1 15M 3.5M 10M 26% /boot
> /dev/sda4 1.4G 591M 736M 45% /home
>
> FSTAB
>
> /dev/sda1 /boot ext2 defaults
> 1 1
> /dev/sda2 swap swap defaults
> 0 0
> /dev/sda3 / ext3 defaults
> 0 0
> /dev/sda4 /home ext3 defaults
> 0 0
> /dev/sdb1 /apl ext3 defaults
> 0 0
> /mnt/cdrom /mnt/cdrom supermount
> ro,dev=/dev/cdrom,fs=iso9660 0 0
> /mnt/floppy /mnt/floppy supermount
> rw,dev=/dev/fd0,fs=vfat 0 0
> none /proc proc defaults
> 0 0
> none /dev/pts devpts
> gid=5,mode=620 0 0
> /dev/cdrom /mnt/cdrom
> iso9660 noauto,owner,kudzu,ro 0 0
>
> O que pode ter ocorrido? Que soluções posso executar
> para identificar o que ocorreu e traze-la de volta?
>
> Ah, coloco um trecho do DMESG pra analise.. notei que
> o segundo disco nao respondeu.
>
>
>
>
>
> scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER,
> Rev 6.2.4
> <Adaptec aic7880 Ultra SCSI adapter>
> aic7880: Ultra Wide Channel A, SCSI Id=7,
> 16/253 SCBs
>
> Vendor: HP Model: 4.26GB A 80-LXY4 Rev: LXY4
> Type: Direct-Access ANSI SCSI
> revision: 02
> Vendor: HP Model: 4.26GB A 80-LXY4 Rev: LXY4
> Type: Direct-Access ANSI SCSI
> revision: 02
> Vendor: ARCHIVE Model: Python 02779-XXX Rev: 6500
> Type: Sequential-Access ANSI SCSI
> revision: 02
> scsi0:A:0:0: Tagged Queuing enabled. Depth 8
> scsi0:A:1:0: Tagged Queuing enabled. Depth 8
> Attached scsi disk sda at scsi0, channel 0, id 0, lun
> 0
> Attached scsi disk sdb at scsi0, channel 0, id 1, lun
> 0
> (scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset
> 8, 16bit)
> SCSI device sda: 8330543 512-byte hdwr sectors (4265
> MB)
> Partition check:
> sda: sda1 sda2 sda3 sda4
> (scsi0:A:1): 40.000MB/s transfers (20.000MHz, offset
> 8, 16bit)
> sdb: Spinning up
> disk...........................................................
> ............................................not
> responding...
> SCSI device sdb: 8330543 512-byte hdwr sectors (4265
> MB)
> sdb:SCSI disk error : host 0 channel 0 id 1 lun 0
> return code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 0
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 2
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 4
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 6
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 0
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 2
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 4
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 6
> unable to read partition table
> Journalled Block Device driver loaded
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Freeing unused kernel memory: 228k freed
> Adding Swap: 128512k swap-space (priority -1)
> EXT3-fs warning: maximal mount count reached, running
> e2fsck is recommended
> EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,3), internal
> journal
> LVM version 1.0.1-rc4(ish)(03/10/2001) module loaded
> loop: loaded (max 8 devices)
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 0
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 2
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 4
> SCSI disk error : host 0 channel 0 id 1 lun 0 return
> code = 8000002
> Info fld=0x300d0101, Current sd08:10: sense key
> Hardware Error
> I/O error: dev 08:10, sector 6
> kjournald starting. Commit interval 5 seconds
> EXT3-fs warning: maximal mount count reached, running
> e2fsck is recommended
> EXT3 FS 2.4-0.9.17, 10 Jan 2002 on sd(8,4), internal
> journal
> EXT3-fs: mounted filesystem with ordered data mode.
> st: Version 20020205, bufsize 32768, wrt 30720, max
> init. bufs 4, s/g segs 16
> Attached scsi tape st0 at scsi0, channel 0, id 3, lun
> 0
> eepro100.c:v1.09j-t 9/29/99 Donald Becker
> http://www.scyld.com/network/eepro100.
> html
> eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by
> Andrey V. Savochkin <saw@sa
> w.sw.com.sg> and others
> PCI: Found IRQ 11 for device 00:08.0
> eth0: OEM i82557/i82558 10/100 Ethernet,
> 00:A0:C9:B1:5E:E9, IRQ 11.
> Receiver lock-up bug exists -- enabling work-around.
> Board assembly 690106-001, Physical connectors
> present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x49caa8d6).
> Receiver lock-up workaround activated.
>
>
> Grato,
>
>
>
>
>
>
>
>
> Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
> http://br.mail.yahoo.com/
>
>
> --
> To UNSUBSCRIBE, email to debian-user-portuguese-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--
André O Moura
http://andrem.wordpress.com
Reply to: