Topic: Iomega Rev Drive

[Matt]

Can anyone help,  I have been trying to setup a rev drive for backup,  the drive is installed on my e-smith server and appears to be working, but am need help trying to send backups to it,  I have been trying to use 'backup to workstation'  which works ok on my shared PC's but what should I put in the destination section?  

I have created a mount point for the rev drive and trying putiing that in without any success.

Thanks in advance

[Buddha_Joe]

Disclaimer: new to Linux and SME

I am pretty sure that the backup scripts look for specific devices. In order to use it you'll porbably have to identify what the actuall device name is under /dev and edit the scripts to point to it. There is also the issue of flexbackup. it may not work with that drive. Just a guess hope it helps.

[cyberjuls]

Is anyone interrested to write a contrib to get Iomega rev working on sme?

[Buddha_Joe]

I just thought of a possible tmporary solution. You could always setup the REV drive on one of your workstations then backup to desktop saving the backup to the rev drive. Not perfect but at least you will be getting the sata backed up.

[elorenz]

Hi all,
I have succeded in getting my internal REV 35 drive to work with SME 6.0.1.
Just follow the instructions at
http://iomrrdtools.sourceforge.net/
You'll need devtools as the kernel source, make and the compiler are needed to build the rev & udffs modules.

This is an ATAPI REV drive and is found at /dev/hdb in my server.
I have for now read/written succesfully to the drive.

I would like to know if anyone has experience with arkeia-light since i would like to run backups against this drive.
Any suggestions in this respect will be much appreciated.
Regards,
Ernesto

[chrisw]

As you have the iomega rev drive working
perhaps you could post a simple how to.
I have tried to get the rev drive working but am a bit lost on how to patch the 2.4 kernel
any help would be appreciated

   

[elorenz]

Hi Chris,
I'll be glad to post the how-to.
I remember a form for posting how-to's back in the past.
Can anyone point me to this form so I can create a standard looking how-to?

BTW: I'm testing the REV drive with rsnapshot and it seems to work ok. Haven't found a manager panel for this. Maybe someone in this forum thread might want to work on this with me (I have very little knowledge of the server-manager forms system).
Arkeia turned out to be a pain in the neck so I droped trying to get it running with REV.
Regards,

[mrjhb3]

Hi Chris,
I'll be glad to post the how-to.
I remember a form for posting how-to's back in the past.
Can anyone point me to this form so I can create a standard looking how-to?

BTW: I'm testing the REV drive with rsnapshot and it seems to work ok. Haven't found a manager panel for this. Maybe someone in this forum thread might want to work on this with me (I have very little knowledge of the server-manager forms system).
Arkeia turned out to be a pain in the neck so I droped trying to get it running with REV.
Regards,

http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/5.x/howto/
DL the howto-template.htmlJB

[chrisw]

Hi Elorenz thanks for starting the how to on the Rev Drive, How long will it be before you can finish it? Don't mean to sound pushy but the sooner the better would be greatly appreciated, As I still haven't got mine working, regards, chris  

[elorenz]

Hi Chris,
I'm allready working on it.
Preliminary is online in the how-to's section.
I'll be completing it today is possible since I have to reinstall everthing again on my test server due to a HD failure.
BTW: I'll try an install of both IDE-ATA and USB drives since I got lucky and borrowed both units from a friend .

Check the how-to on Monday!

Regards,
Ernesto

[chrisw]

Hi

Have managed to get my Rev Drive working on my test server and have used Rsync to backup to the rev drive. Thanks for the how to, it is much appreciated.  Had a problem with the uname -p command my pc came back with "unknown" but I copied a 686 config file to .config and it seems to work ok.  I am new to the Rsync set up and was interested to know how you have/are going to set up your backups, do you put a new disk in everynight or what?  any help on this would be great.  And again thanks for the how to.

Regards
Chris

[elorenz]

Hi Chris,

I'm glad to read you're faring ok with the REV device.
I currently use rsnapshot as a backup app and am very happy with the results. I created a samba share that points to /mnt/rev so the network admin group can recover any files that have been backed up. The cartridge holds a los of backups ans rsnapshot keeps daily (7), weekly (4) and mothly (??) folders of all the backup files.
I'm working on a mod to the server-manager backup panel so the admin can see the status of the REV device, mount and eject cartridges. I'm having a hard time understanding the documentation on FormMagick and have noticed that the backup panel was created using an older method.
Any help in this respect will be much appreciated and will peed my wotk up.
Best regards to all,
Ernesto

[chrisw]

Hi

have now got the rev drive working on my production server, dungog.net have a server manager panel for backup and rsynch, but you have to join dungog. The rev drive works well with the rsynch but it won't work with the tgz file option of the backup panel.  I will email dungog about this and see if they can do anything about it.

Chris

[elorenz]

Hi,

I'm getting a weird failiure from the rev module that is intermittent.
Here is the messages log extract:
Jun 19 12:36:52 servidor kernel: rev: module being loaded
Jun 19 12:36:52 servidor kernel: rev: device sr0 supports random write.
Jun 19 12:36:52 servidor kernel: rev: device /dev/hda is not supported by ide-cd
Jun 19 12:36:52 servidor kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000003c
Jun 19 12:36:52 servidor kernel:  printing eip:
Jun 19 12:36:52 servidor kernel: cc8bf4ac
Jun 19 12:36:52 servidor kernel: *pde = 00000000
Jun 19 12:36:52 servidor kernel: Oops: 0000
Jun 19 12:36:52 servidor kernel: rev sr_mod appletalk sis900 ide-scsi scsi_mod ide-cd cdrom ehci-hcd usb-ohci usbcore ext3 jbd  
Jun 19 12:36:52 servidor kernel: CPU:    0
Jun 19 12:36:52 servidor kernel: EIP:    0010:[scsi_mod:scsi_hosts_R206fd08d+122988/232688108]    Not tainted
Jun 19 12:36:52 servidor kernel: EIP:    0010:[<cc8bf4ac>]    Not tainted
Jun 19 12:36:52 servidor kernel: EFLAGS: 00010292
Jun 19 12:36:52 servidor modprobe: modprobe: pre-install udffs failed
Jun 19 12:36:52 servidor kernel:
Jun 19 12:36:52 servidor modprobe: modprobe: insmod udffs failed
Jun 19 12:36:52 servidor kernel: EIP is at rev_ide_get_configuration_feature_0x0020 [rev] 0x64 (2.4.20-18.7)
Jun 19 12:36:52 servidor kernel: eax: 00000000   ebx: c17ccd28   ecx: 00000000   edx: c3887e70
Jun 19 12:36:52 servidor kernel: esi: 00000000   edi: c3887e7c   ebp: c3887eb8   esp: c3887e50
Jun 19 12:36:52 servidor kernel: ds: 0018   es: 0018   ss: 0018
Jun 19 12:36:52 servidor kernel: Process modprobe (pid: 2085, stackpage=c3887000)
Jun 19 12:36:52 servidor kernel: Stack: c17ccd28 c3887e70 00000008 00000000 0000000a c3887e70 00000000 00000000
Jun 19 12:36:52 servidor kernel:        20000246 00000000 00000008 c3887e68 00000008 00000000 00000000 00000002
Jun 19 12:36:52 servidor kernel:        00000000 000001f4 00000000 00001e7e c01182cb 00001e7e 00001e7e c0378894
Jun 19 12:36:52 servidor kernel: Call Trace:   [call_console_drivers+235/256] call_console_drivers [kernel] 0xeb (0xc3887ea0))
Jun 19 12:36:52 servidor kernel: Call Trace:   [<c01182cb>] call_console_drivers [kernel] 0xeb (0xc3887ea0))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+123105/232687991] rev_ide_test_cdrom_drive [rev] 0x5d (0xc3887ebc))
Jun 19 12:36:52 servidor kernel: [<cc8bf521>] rev_ide_test_cdrom_drive [rev] 0x5d (0xc3887ebc))
Jun 19 12:36:52 servidor kernel: [printk+256/272] printk [kernel] 0x100 (0xc3887ecc))
Jun 19 12:36:52 servidor kernel: [<c0118450>] printk [kernel] 0x100 (0xc3887ecc))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+123227/232687869] rev_ide_initialize [rev] 0x43 (0xc3887edc))
Jun 19 12:36:52 servidor kernel: [<cc8bf59b>] rev_ide_initialize [rev] 0x43 (0xc3887edc))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+134976/232676120] sr_attach [rev] 0x0 (0xc3887ef4))
Jun 19 12:36:52 servidor kernel: [<cc8c2380>] sr_attach [rev] 0x0 (0xc3887ef4))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+121914/232689182] init_rev [rev] 0x1a (0xc3887f0c))
Jun 19 12:36:52 servidor kernel: [<cc8bf07a>] init_rev [rev] 0x1a (0xc3887f0c))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+131151/232679945] .rodata.str1.1 [rev] 0xf (0xc3887f10))
Jun 19 12:36:52 servidor kernel: [<cc8c148f>] .rodata.str1.1 [rev] 0xf (0xc3887f10))
Jun 19 12:36:52 servidor kernel: [sys_init_module+1333/1520] sys_init_module [kernel] 0x535 (0xc3887f2c))
Jun 19 12:36:52 servidor kernel: [<c01192b5>] sys_init_module [kernel] 0x535 (0xc3887f2c))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+133512/232677584] .kmodtab [rev] 0x0 (0xc3887f30))
Jun 19 12:36:52 servidor kernel: [<cc8c1dc8>] .kmodtab [rev] 0x0 (0xc3887f30))
Jun 19 12:36:52 servidor kernel: [scsi_mod:scsi_hosts_R206fd08d+121888/232689208] init_rev [rev] 0x0 (0xc3887f58))
Jun 19 12:36:52 servidor kernel: [<cc8bf060>] init_rev [rev] 0x0 (0xc3887f58))
Jun 19 12:36:52 servidor kernel: [system_call+51/56] system_call [kernel] 0x33 (0xc3887fc0))
Jun 19 12:36:52 servidor kernel: [<c01088c3>] system_call [kernel] 0x33 (0xc3887fc0))
Jun 19 12:36:52 servidor kernel:
Jun 19 12:36:52 servidor kernel:
Jun 19 12:36:52 servidor kernel: Code: ff 56 3c 89 c2 83 c4 10 31 c0 85 d2 0f 95 c0 8d 65 f4 5b 5e
Jun 19 12:36:52 servidor modprobe: modprobe: Can't locate module freeudffs
Jun 19 12:36:52 servidor kernel:  <4>Unable to identify CD-ROM format.
Jun 19 12:36:53 servidor atalk: papd startup succeeded
Jun 19 12:36:53 servidor papd[2117]: restart (1.5.5)
Jun 19 12:36:53 servidor atalk: afpd startup succeeded
Jun 19 12:36:59 servidor afpd[2122]: servidor:AFPServer@* started on 65280.218:128 (1.5.5)
Jun 19 12:36:59 servidor afpd[2122]: ASIP started on 192.168.1.20:548(2) (1.5.5)
Jun 19 12:36:59 servidor afpd[2122]: uam: loading (/usr/lib/uams_dhx.so)
Jun 19 12:36:59 servidor afpd[2122]: uam: uams_dhx.so loaded
Jun 19 12:36:59 servidor afpd[2122]: uam: loading (/usr/lib/uams_pgp.so)
Jun 19 12:36:59 servidor afpd[2122]: uam: uams_pgp.so loaded
Jun 19 12:36:59 servidor afpd[2122]: uam: "PGPuam 1.0" available
Jun 19 12:36:59 servidor afpd[2122]: uam: "DHCAST128" available
Jun 19 12:37:21 servidor kernel: udf: registering filesystem
Jun 19 12:37:29 servidor kernel: Unable to identify CD-ROM format.
Jun 19 12:38:20 servidor kernel: Unable to identify CD-ROM format.

I suspect a hardware bug on the motherboard, but as my experience debugging at this level is short of nill I'm asking for anyones help to untangle this mistery.

The failure started last night after the server crashed. I turned it off over night and this morning every thing was working OK. I transported the server with my car to the customer site and the failure reapeared. ???
This starts when I mount the cartridge with mount /mnt/rev
and get an error message on the terminal screen stating the format is unidentifiable.

I just checked remotely a moment ago and the device seems to be working OK ???

I'm confused!!
Help! anyone.

[rf131]

Hi Ernesto,

Have you considered downloading the Ultimate Boot CD?  This CD is chock-full of utilities, and the nice thing it boots and gives you an easy-to-navigate menu system.  There are several hardware checking utilities included.

Be careful what you run; there is a lot of power in this CD and you can get in trouble quick.  The disk and file system utilities, while they can be useful, have some functionality that can wipe out your data so beware!

URL is:  http://ultimatebootcd.com

Good luck,
Kevin

P.S.  I'm probably going to get a Rev here in a week or so and will try your howto.  Thanks for the effort!