Sponsored Content
Operating Systems Solaris Recovering DATA from sparc classic Post 302931566 by fpmurphy on Tuesday 13th of January 2015 11:33:56 PM
Old 01-14-2015
Does the drive spin up when you apply power to the drive enclosure? If the drive does not spin up, you are not going to be able to recover the data without specialist help.
 

6 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Filesystems: Hiding and recovering data

Here is a very interesting article on not only hiding data on filesystems (the article deals mainly with the ext2 filesystem, which should also work with etx3), but also recovering, including from slack space on raw blocks, and even deleted data! ... (0 Replies)
Discussion started by: LivinFree
0 Replies

2. UNIX for Dummies Questions & Answers

Recovering lost folders/files data

Hello, Is there a way to recover data from a SCO UNIXWARE 7.4 operating system without using a tape backup device? We believe there is some data in some directories that was there once; but not anymore, we don't have a backup on tape. So, is there any other solution to recover? Hope... (0 Replies)
Discussion started by: Yorgy
0 Replies

3. UNIX for Dummies Questions & Answers

Flash drive recovering data.

I have a flash drive which contained very important docs. But somebidy accidently dleted those files. I want to recover these files anyhow. I have listened the Linux have best possible chances of recovering it. Can anybody tell me how to recover that? (1 Reply)
Discussion started by: nixhead
1 Replies

4. Solaris

Unable to login Solaris 10 Sparc - Data Access Error

Hello everyone, This is the first time I am installing Solaris. I have SunBlade 1500 Wrkstn. I installed Solaris 10 Sparc. The installation went successfully but I don't get the login screen. I get the following error message: Boot device: disk:a File and agrs:- Data Access Error Ok ... (4 Replies)
Discussion started by: mfsaeed
4 Replies

5. Solaris

SPARC, data sectors/track

when I try to enter the value 424 for "data sectors/track" in format menu, it returns this error: `424' is out of range. is that hard drive parameter important? what to enter? thanks. (2 Replies)
Discussion started by: orange47
2 Replies

6. Linux

Recovering corrupted LVM data: No readable superblocks

Hi all. Not sure where to post this, so figured I'd start here. I have a LVM2 partition that has become unreadable. I've scoured dozens of threads about the topic and have hit a wall, so any advice is appreciated. Below is what I think shows what my major problem is: First, a simple mount... (3 Replies)
Discussion started by: dargason
3 Replies
scsi-spin(8)						      System Manager's Manual						      scsi-spin(8)

NAME
scsi-spin - spin up and down a SCSI device SYNOPSIS
scsi-spin [-options...] [device] DESCRIPTION
scsi-spin let the user to manually spin up and down a SCSI device. This command is particularly useful if you've got noisy (or hot) drives in a machine that you rarely need to access. This is not the same as the kernel patch that's floating around that will automatically spin down the drive after some time. scsi-spin is completely manual, and spinning down a drive that's in use, especially the one containing the scsi-spin binary, is probably a really bad idea. To avoid running in trouble with such cases, scsi-spin verifies that the device to work on is not currently in use by scanning the mounted file system description file for a partition living on it and issue an error if this the case. OPTIONS
-u, --up spin up device. -d, --down spin down device. -e, --loej load or eject medium from drive (use along with -u or -d ) -w, --wait=[n] wait up to n seconds for the spin up/down command to complete. Default is to return immediately after the command was sent to the device. Either repeat -w n times or set n to define the time to wait before to report a timeout. -l, --lock prevent removal of medium from device. -L, --unlock allow removal of medium from device. -I, --oldioctl use legacy ioctl interface instead of SG_IO to dialog with device (could not be supported on all platforms). -e and -w are not allowed with this option. -v, --verbose=[n] verbose mode. Either repeat -v or set n accordingly to increase verbosity. 1 is verbose, 2 is debug (dump SCSI commands and Sense buffer). -f, --force force spinning up/down the device even if it is in use. -n, --noact do nothing but check if the device is in use. -p, --proc use /proc/mounts instead of /etc/mtab to determine if the device is in use or not. device the device is any name in the filesystem which points to a SCSI block device (sd, scd) or generic SCSI device (sg). See section below. SCSI devices naming convention Old kernel naming convention It is typically /dev/sd[a-z] , /dev/scd[0-9]* or /dev/sg[0-9]*. scsidev naming convention It is typically /dev/scsi/s[rdg]h[0-9]*-e????c?i?l? or /dev/scsi/<aliasname>. devfs naming convention It is typically /dev/scsi/host[0-9]/bus[0-9]/target[0-9]/lun[0-9]/disc (same for cd and generic devices) or short name /dev/sd/c[0-9]b[0-9]t[0-9]u[0-9] when devfsd "new compatibility entries" naming scheme is enabled. SEE ALSO
scsiinfo(8), sg_start(8), sd(4), proc(5), AUTHORS
Eric Delaunay <delaunay@debian.org>, 2001 Rob Browning <rlb@cs.utexas.edu>, 1998 03 September 2001 scsi-spin(8)
All times are GMT -4. The time now is 05:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy