Fita DAT DDS4 nao monta!!??
Boa tarde pessoal.
Seguinte tenho uma servidor Itautec aqui no qual estou querendo fazer backup dos seus arquivos, pois este 'e o servidor de arquivos da rede e nele roda o Slackware 10.2, ele tem um drive de fita DAT DDS4 de marca Quantum/Seagate, quando tento fazer o backup por exemplo :
tar -cv -T /home -f /dev/st0
ou
tar cvf /dev/st0 /home
Da esse erro:
tar: /dev/st0: Cannot open: No such device
tar: Error is not recoverable: exiting now
Ja tentei montar o dispositivo mas nao monta, e tb nao tem referencia ao drive DDS na fstab como podem ver abaixo.
/dev/sda1 swap swap defaults 0 0
/dev/sda2 / reiserfs defaults 1 1
/dev/sda3 /home reiserfs defaults 1 2
/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
O Drive de fita esta funcionando, pois tinha o win03 instalado aqui neste server e funcionava, mas
quero manter o Linux nele.
Acrecento que ele possui HD SATA e na instalacao do Slack usei o kernel SATA.i, portanto nao sei se tem suporte a SCSI.
Por favor alguem tem ideia do que pode ser ??
Desde ja agradeco.
Re: Fita DAT DDS4 nao monta!!??
Cara, roda um dmesg e verifica se tem alguma referencia ao tape. Caso não exista (e pelo que eu entendi ela é ligada pelo scsi) procure saber se existe no dmesg algo referente ao SCSI. Quando ao sata.i, em geral ele tem suporte básico a scsi, ou seja, partes do protocolo, pq é o mesmo que é usado para acesso a dispositivos sata.
qq coisa é só perguntar.
Re: Fita DAT DDS4 nao monta!!??
Nao achei nenhuma referencia ao drive DAT na saida do dmesg, mas por favor se puder dar uma olhada agradeco ...
Linux version 2.4.31 (root@tree) (gcc version 3.3.5) #21 Sun Jun 5 19:19:51 PDT 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009cc00 (usable)
BIOS-e820: 000000000009cc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000ea070 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003ffc0000 (usable)
BIOS-e820: 000000003ffc0000 - 000000003ffcf000 (ACPI data)
BIOS-e820: 000000003ffcf000 - 000000003fff0000 (ACPI NVS)
BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec86000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
On node 0 totalpages: 229376
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=Linux ro root=802
Initializing CPU#0
Detected 3200.260 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 6383.20 BogoMIPS
Memory: 904316k/917504k available (1873k kernel code, 12788k reserved, 621k data, 120k init, 0k highmem)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: After generic, caps: bfebfbff 20000000 00000000 00000000
CPU: Common caps: bfebfbff 20000000 00000000 00000000
CPU: Intel(R) Xeon(TM) CPU 3.20GHz stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch ([email protected])
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=4
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge
PCI: Using IRQ router PIIX/ICH [8086/25a1] at 00:1f.0
PCI: Found IRQ 10 for device 00:02.0
PCI: Sharing IRQ 10 with 00:03.0
PCI: Sharing IRQ 10 with 00:1d.0
PCI: Found IRQ 11 for device 00:1f.1
PCI: Sharing IRQ 11 with 00:1f.2
PCI: Found IRQ 11 for device 00:1f.3
PCI: Sharing IRQ 11 with 04:05.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Journalled Block Device driver loaded
vesafb: framebuffer at 0xfd000000, mapped to 0xf880d000, size 3072k
vesafb: mode is 1024x768x16, linelength=2048, pages=4
vesafb: protected mode interface info at c000:4a7e
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:5:5, shift=0:10:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10f
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 7777K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 00:1f.1
PCI: Found IRQ 11 for device 00:1f.1
PCI: Sharing IRQ 11 with 00:1f.2
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio
hda: LITE-ON CD-RW SOHR-5239S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-cdrom driver.
hda: ATAPI 52X CD-ROM CD-R/RW drive, 1536kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
SCSI subsystem driver Revision: 1.00
libata version 1.10 loaded.
ata_piix version 1.03
PCI: Found IRQ 11 for device 00:1f.2
PCI: Sharing IRQ 11 with 00:1f.1
PCI: Setting latency timer of device 00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xD400 irq 11
ata2: SATA max UDMA/133 cmd 0xDC00 ctl 0xD802 bmdma 0xD408 irq 11
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4673 85:7c69 86:3e21 87:4663 88:207f
ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata1: dev 0 configured for UDMA/133
ata2: SATA port has no device.
scsi0 : ata_piix
scsi1 : ata_piix
Vendor: ATA Model: Maxtor 6L160M0 Rev: BACE
Type: Direct-Access ANSI SCSI revision: 05
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB)
Partition check:
sda: sda1 sda2 sda3 sda4
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
8regs : 3500.000 MB/sec
32regs : 2286.400 MB/sec
pIII_sse : 5540.000 MB/sec
pII_mmx : 3448.800 MB/sec
p5_mmx : 3467.200 MB/sec
raid5: using function: pIII_sse (5540.000 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.8(17/11/2003)
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device sd(8,2)) ...
for (sd(8,2))
sd(8,2):Using r5 hash to sort names
VFS: Mounted root (reiserfs filesystem) readonly.
Freeing unused kernel memory: 120k freed
Adding Swap: 289128k swap-space (priority -1)
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: no supported devices found.
NTFS driver v1.1.22 [Flags: R/O MODULE]
scsi2 : SCSI host adapter emulation for IDE ATAPI devices
reiserfs: found format "3.6" with standard journal
reiserfs: checking transaction log (device sd(8,3)) ...
for (sd(8,3))
sd(8,3):Using r5 hash to sort names
Re: Fita DAT DDS4 nao monta!!??
Olha, qual é a versão do kernel q vc tá usando? pode ser que seja interessante usar um kernel da série 2.6, de preferência compilado por vc mesmo para tentar saber como a controladora scsi é identificada. Sugiro que vc tente dar boot na máquina com o slax, que vem com um kernel 2.6 para verificar qual é o módulo necessário (rodando novamente o dmesg e lspci ) já que vc está usando o kernel 2.4.31 padrão. rode o slax e verifique.
Re: Fita DAT DDS4 nao monta!!??
Blz .. vou baixar o slax e ver no que da ..
Posto aqui depois...
Bom final de semana.
[]'s