Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 23 Nov 2017, 03:41
All times are UTC - 4
 Forum index » Advanced Topics » Hardware
Need a driver for SCSI DLT/DAT Tape Drive (Solved)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [20 Posts]   Goto page: 1, 2 Next
Author Message
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Thu 24 Sep 2009, 16:04    Post subject:  Need a driver for SCSI DLT/DAT Tape Drive (Solved)  

Has anyone seen a driver that would allow the use of a DLT or DAT SCSI drive with Puppy?

And if so could it be added to Puppy-4.3.0-SCSI perhaps not recompling the Kernel but as a loadable driver if necessary.

I have two SCSI machines with those drives (Dell DLT-1, HP DAT24) and still use them under M$ Windows XP and would like to use them under Puppy. Referenced as /dev/rmt0 .

There was a time when tape was the ultimate backup/restore medium.

Think of the origins of "tar" and uses of "cpio".

See: http://www.washington.edu/computing/unix/tar.html

Last, I would like to be able to read some of my old "tar'd" Unix tapes.

-Thanks

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Fri 25 Sep 2009, 14:13    Post subject:  

Puppy 430-SCSI

Have some additional information. Dmesg reports the following:

ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 18 (level, low) -> IRQ 18
scsi3 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0
<Adaptec aic7880 Ultra SCSI adapter>
aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs

scsi 3:0:5:0: Sequential-Access BNCHMARK DLT1 391B PQ: 0 ANSI: 2
target3:0:5: Beginning Domain Validation
target3:0:5: wide asynchronous
target3:0:5: FAST-10 WIDE SCSI 20.0 MB/s ST (100 ns, offset 8)
target3:0:5: Domain Validation skipping write tests
target3:0:5: Ending Domain Validation

Does this mean the kernel saw the DLT drive and if so how would I add a sequential device for it?

It's attached to the 7880 chip with ID 5.

Thanks.

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Sat 26 Sep 2009, 11:30    Post subject:  

Does this help?

Hello,

you can not mount a tape like a hard disk because it is a sequential device.
Use commands like
# tar -xf /dev/st0
# tar -tf /dev/st0
# tar -cf /dev/st0 <files,directories>
to get access to the tape (read, read inventory, write)

Another helpfully tape command is mt.
for example:
# mt -f /dev/st0 status
# mt -f /dev/st0 eject

Use man mt or man tar for more information.
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Sat 26 Sep 2009, 17:39    Post subject:  

This could be the source code you needed for the missing commands in Puppy for use with tape drives.
I'm working in the dark here as I do not have a scsi tape drive to test this on. But it compiled fine just using make.
I did not use a make install and just ran the compiled files from a terminal using ./mt and ./stinit
mt gave me feedback of usage and stinit wanted a configuration file.
I downloaded the examples of each if you need them.
mt-st-1.1.tar.gz
Description  Source for mt, stinit
gz

 Download 
Filename  mt-st-1.1.tar.gz 
Filesize  34.91 KB 
Downloaded  401 Time(s) 
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Sat 26 Sep 2009, 18:19    Post subject:  

I should also state that I compiled them under Puppy 43 scsi beta3 with the 2.6.30.5 kernel.
I have been using that version now along with Puppy 421 and even installed the SeaMonkey 2.0 b2 pet on it. All is good.
Back to top
View user's profile Send private message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Sat 26 Sep 2009, 18:20    Post subject:  

8-Bit,

Are you running Puppy SCSI 430-k2.6.25.16-SCSI?

Did you use devx-SFS3_430.sfs from:

ftp://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/special-puppies/

If they compiled OK can you upload the compiled versions
of mt and stinit? That would save me from having to download
the dev package and messing around with it.

Lets keep future messages on this thread OK?

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Sat 26 Sep 2009, 20:19    Post subject:  

Ok, I did a quick frugal install of Puppy 43 scsi kernel 2.6.25.16 and compiled the source.
I then made a Pet that puts the commands in the appropriate directories as well as including the man pages in their respective directories.
So all you have to do is install the Pet package.
If for some reason it does not work, just uninstall the Pet package.
mt-stinit-1.1.pet
Description  SCSI tape commands with man pages compiled under Puppy 43 kernel 2.6.25.16. Although it might work with other versions.
pet

 Download 
Filename  mt-stinit-1.1.pet 
Filesize  22.71 KB 
Downloaded  428 Time(s) 
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Sat 26 Sep 2009, 20:39    Post subject:  

Ok, a glitch with Puppy and man pages in text format.
The man pages for the commands are in /usr/share/man/man1/mt.1
and /usr/share/man/man8/stinit.8.
I found this out when typing 'man mt' in a terminal.
Back to top
View user's profile Send private message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Sun 27 Sep 2009, 12:59    Post subject:  

8-Bit,

I will download it and try it. Thanks.

By the way did you use devx-SFS3_430.sfs from

ftp://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3/special-puppies/

to compile it?

Thanks

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Sun 27 Sep 2009, 15:10    Post subject:  

8-Bit,

Your binaries worked fine! Thanks...

Wanting to get a handle on this for myself I downloaded
devx-SFS3_430.sfs renamed it to devx-430.sfs rebooted
unziped and un-tar'd the source and was able to compile.

Thinking back in my time machine I have to look at the
source because if you issue a command I.E.
"mt -f /dev/st0 rewind" and no tape is present you don't
get an error. Rather the program sits until Ctrl/C is pressed.
I think there used to be a timeout on ioctl under Unix.

I also changed the default device from /dev/tape to /dev/st0
which more comes in line with (Puppy) Linux.

So now after installing Puppy 430 k2.6.25.16 SCSI you simply
create the device. For the first tape mknod -m 666 /dev/st0 c 9 0
If you want no rewind then mknod -m 666 /dev/nst0 c 9 128
for the first tape drive. I plan on adding a SCSI DAT drive as
a second drive to see how it works. That will require two more
devices. That way I can test DLT and DAT tapes drives.

So if Barry keeps module "st" in the SCSI kernel this should
be fine. Once I get the fixes into 'mt' to exit on errors I then
have to figure out how to make a 'pet' file. Also, when the
'pet' file is installed if /dev/st0 or /dev/st1 does not exist create
then as above.

By the way where should the 'man' pages go? Using man errors
out to default bringing up a WEB page.

-Kenny-M

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Sun 27 Sep 2009, 16:53    Post subject:  

8-bit wrote:
Ok, a glitch with Puppy and man pages in text format.
The man pages for the commands are in /usr/share/man/man1/mt.1
and /usr/share/man/man8/stinit.8.
I found this out when typing 'man mt' in a terminal.

I quoted myself as to not have to retype some stuff.
If you move mt.1 and stinit.8 to /usr/share/doc/ and rename them giving them a txt extension (ex. mt.txt stinit.txt ) they will come up in a text editor when you type 'man mt' or 'man stinit' at the command prompt..
I do not know what the guy used to make the man pages, but I thought it was a poor choice.
Also, for a quick idea of commands for mt, type 'mt man' at the command prompt It will give an error, but will show you a more complete list of the commands.
I guess we sill like Puppy even though the directory structure sometimes seems to leave you out in left field.
Back to top
View user's profile Send private message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Sun 27 Sep 2009, 17:27    Post subject:  

8-Bit

The format of the "man" pages go way, way back to the late 1960's.

They are created with "nroff" commands within the document. This was way before mice and windows. Documents were generally preparred using dumb CRT terminals like a DEC VT-100 using vi. However in a pinch you could edit files from a DECWriter or a TTY using ed.

See DECWriters:
http://www.flickr.com/photos/rick_melick/639762231/
and Teletypes:
http://www.flickr.com/photos/dancentury/3916969051/

Example to see the man page for mt.1 where ever it is
located you would type in:

cd <directory with mt.1>
nroff -man mt.1

Then you should see a pretty formatted output.

nroff -man mt.1 | more (only use the space bar to advance)

Gosh, up to a decade or two ago lots of documents were done in nroff.

Nroff example:
http://www.rfc-editor.org/nroff.html

There is also troff which was used with typesetters to print manuals.

Real old school. But it still works when used.

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Tue 29 Sep 2009, 09:30    Post subject:  

I stumbled across a GUI tape backup package that I thought you might want to check out.
I have no tape drive, so I have no means of checking it out.
Lnx-Bkp-Util-v1.21gc.tar.gz
Description  A GUI type Linux tape backup utility
gz

 Download 
Filename  Lnx-Bkp-Util-v1.21gc.tar.gz 
Filesize  86.18 KB 
Downloaded  427 Time(s) 
Back to top
View user's profile Send private message 
Kenny-M


Joined: 15 May 2009
Posts: 147
Location: United States

PostPosted: Tue 29 Sep 2009, 10:56    Post subject:  

8-Bit,

Thanks so much for your time. Unfortunately that package uses 'old' pre-compiled code and can not do "full" backups.

Please keep up the good work!

Thoughts.

If I do a straight: dd if=/dev/sdb of=/dev/st0 the entire disk is dumped to tape which is fine. The only real problem is if replacing the disk the new disk is ever so slightly smaller DD will fail.

It appears to me one solution would be to get the current partition layout on the disk in question and get the boot sector/partition table layout.

Write the boot sector/partition table to tape.
Write each partition appearig the partition table to tape.

In theory I can write boot sector to tape as:
dd if=/dev/sdb of=/dev/nst0 bs=512 count=1 (nst0=no rewind)
dd if=/dev/sdb1 of=/dev/nst0 bs=1M (nst0=no rewind)
dd if=/dev/sdb2 of=/dev/st0 bs=1M (st0=rewind tape on last write)

That still leaves the problem of lost space if the target drive is larger then the source drive. The partition table from the source drive dosen't take this into account. One solution might be to get the current partition table extracting all necessary information. Partitions, sizes, types. Save that to tape. Then at restore read the first block from tape (nst0) and using fdisk create the partitions fresh then read sucessive entries on tape to data fill those new partitions. On the last read use st0 to rewind the tape.

We still need the boot sector restored.

I think sticking with DD is a good idea as it does not care about file system, directories, etc. It just copies blocks. While on the surface tar looks nice you are left with file system oddities and the tape still won't restore a bootable system.

This is getting complicated! Any thoughts?

By the way did you see my remarks on "I do not know what the guy used to make the man pages, but I thought it was a poor choice"?

_________________
Puppy 4.2.1 SeaMonkey on 160GB Ext USB Disk on Dell 745 SFF.
Puppy 4.3.0-SCSI on Dell Precision 610 workstation.
Puppy 4.2.1 running on Windows XP under Qemu.
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3425
Location: Oregon

PostPosted: Tue 29 Sep 2009, 18:33    Post subject:  

Yes, I saw your remarks on man pages.
After using the 'nroff -man [program]' I tried to use the same command in Puppy 4.2.1. Puppy 4.2.1 gives me "command not found", but typing "man [program] brings up the man page nicely formated. Also, I can see the search for the man file in the terminal to where it is looking in man directories.
But Puppy 4.3 seems to be doing it's search in /usr/share/doc and ignores the man directories completely. So even if the man page is local, it is ignored and one is taken to die.net on the internet.
What got changed between the two versions I do not know, but it seems to me that the man command works more correctly in Puppy 4.2.1.
Of course Puppy leaves out a lot of man files to keep size down.
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [20 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Hardware
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1100s ][ Queries: 12 (0.0205s) ][ GZIP on ]