I have been running 3.6 for about a year on my server. I have a backup
solution that writes to an ide-cdrw 4 times a day. A month ago I
installed a scsi card to hook up a newly acquired tape drive. My cdrw
backups have been failing since.
I did not change any kernel settings (that I
I have been running 3.6 for about a year on my server. I
have a backup
solution that writes to an ide-cdrw 4 times a day. A month ago I
installed a scsi card to hook up a newly acquired tape drive.
My cdrw
backups have been failing since.
I did not change any kernel settings (that
On Thu, 3 Nov 2005, Marc L'Heureux wrote:
I have been running 3.6 for about a year on my server. I have a backup
solution that writes to an ide-cdrw 4 times a day. A month ago I installed a
scsi card to hook up a newly acquired tape drive. My cdrw backups have been
failing since.
I did
I have been running 3.6 for about a year on my server. I
have a backup
solution that writes to an ide-cdrw 4 times a day. A month ago I
installed a scsi card to hook up a newly acquired tape drive.
My cdrw
backups have been failing since.
I did not change any kernel
From: Marc L'Heureux [mailto:[EMAIL PROTECTED]
I used to have dev=/dev/cd0c:0,0,0 but looking at my dmesg
I thought I might
have to change it to dev=/dev/cd0c:0,1,1. Providing
different options to
cdrecord does not help, it still bails
It should be dev=/dev/rcd0c:$BUS,0,0 -
5 matches
Mail list logo
