On 06/04/10 06:00, sofsof wrote: > > I have a problem after a forced restart, in fact : > status dir return me that my client > "is waiting for a mount request" > in fact status storage return me: > > Device status: > Device "drive" (/dev/st0) is not open. > Device is BLOCKED. User unmounted during wait for media/mount. > ==== > > > How can I unblock this device please ? > > Thank for any help !. >
Then, On 06/04/10 08:02, sofsof wrote: > I have try the mount but it return me: > 3901 open device failed: ERR=dev.c:425 Unable to open device "drive" > (/dev/st0): ERR=No medium found sofsof... I have pasted two of your emails together into this reply. As Thomas mentioned previously, you really should be using /dev/nst0 (non-rewinding tape device) instead of the /dev/st0 that you are currently using. Having said that, you also mentioned a "forced restart" so I am imagining that you mean you may have forcefully rebooted the server. If so, is it also possible that your SCSI controller module or the "st" (SCSI Tape) module is not loaded and therefore /dev/st0 does not even exist? Some things to try: run lsmod and look for the st module (may not even be there is built-in to the kernel, so don't panic yet) run dmesg and look for your SCSI controller and your tape drive, in my case one of several tape drives in this machine shows up in the dmesg output like so: scsi 41:0:4:0: Sequential-Access ECRIX VXA-1 1101 PQ: 0 ANSI: 2 The dmesg output should also show your drive being assigned by the "st" module to a device node "st0" like so: st: Version 20081215, fixed bufsize 32768, s/g segs 256 st 41:0:4:0: Attached scsi tape st0 If you see similar info in your dmesg output, then run: ls -la /dev/st0 /dev/nst0 Which should show you something similar to: crw-rw---- 1 root tape 9, 128 Jun 1 17:21 /dev/nst0 crw-rw---- 1 root tape 9, 0 Jun 1 17:21 /dev/st0 (In his case, you would need to make sure your bacula-sd is running as root, or that the user it is running as is in the tape group) If the devices above do exist, make sure a a tape is in the drive and run: /usr/sbin/mt -f /dev/nst0 status and you should see something similar to: SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 1024 bytes. Density code 0x80 (DLT 15GB uncomp. or Ecrix). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN (key being the File number, and block number both being =0 which means the drive recognizes a tape and that it is at the beginning) Since your storage daemon is currently waiting on a mount command, the drive should be available to access from other programs like "mt" but if it is not and you you see something like: /dev/nst0: Device or resource busy Then it is possible that bacula-sd still has control over the device. You can stop the bacula-sd storage daemon then re-run the "mt" command. If any of those tests fail or there is any indication that your OS does not see your drive, or that there are lower-level SCSI errors of any type then that is where you may need to begin fix the problem. Hope some of this helps some. -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/ ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
