Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory Problem with accessing my 2nd hard drive Post 302423833 by Donald Spauldin on Saturday 22nd of May 2010 05:28:32 PM
Old 05-22-2010
Problem with accessing my 2nd hard drive

Hello
I am having a problem with being able to use my 2nd hard drive as my new os doesn't recognize it. it is /dev/hdb2 and it shows as It is still in my system. it is a 73 gb hard drive and it is useless to me now. I used to have windows XP and had no problem with it,I have since changed to freespire and as of now the Os does not recognize that i ever had it in my system and i would like to have the operating system recognize that i still have the 73 gb drive in the system and can be able to use it.also i have no permissions to read ,change delete or add anything to it .that I would like to be able to do.any information will be appreciated thank you.
I usually use exectec as my username but I am Donald Spaulding or just Don thanks again
Don
!I hope this was better information than when first posted here.

Last edited by Scott; 05-22-2010 at 06:47 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Trying to copy old hard drive to new hard drive.

:confused: ........I have a new hard drive and I need to copy ALL info from the old to the new. I would like to use the dd command. I know the command is as follows...... dd if=/dev/rdsk/c1t1d0s0 of=/dev/rdsk/???????? Where I have the question marks is the problem. How do I find out what the... (4 Replies)
Discussion started by: shorty
4 Replies

2. Filesystems, Disks and Memory

The best partitioning schem for a 250GB Sata hard drive & a 75GB SCSI hard drive

Hi I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies

3. SCO

USB hard drive problem

I have a USB hard drive attached to my SCO OSR6 machine I accidently powered it off while it was mounted and now the OS complains when you try to re-mount it and it appears that it is complaining because it has a new device number so it isn't at the original device location anymore. does anyone... (1 Reply)
Discussion started by: garycrow
1 Replies

4. Ubuntu

Accessing all of the hard drive...

Hi, I just downloaded and installed Ubuntu yesterday. It's the first time I have used it, so bear with me. I think I figured out how to get my sound drivers to work (X-Fi)... I had downloaded some OSS drivers, bout to go test them. But what I really want to know is... I have 2 hard drive,... (2 Replies)
Discussion started by: blind melon
2 Replies

5. SCO

I need a help with accessing the hard drive

Hello guys, I have got from a friend a hard disk which was used in the SCO OpenServer. He needs some data from it. I have no clue how to copy its content with Linux or Windows-I have tried few Linux distros but the result is always the same-the file system is not recognized so can't be mounted.... (4 Replies)
Discussion started by: kataro
4 Replies

6. Solaris

routing problem after replacing hard drive

Need to replace hard drive on Ultra 10 running Solaris 2.6. Bought new drive about the same size. Partitioned it differently to solve a space problem. After newfs used tar commands to copy most of the files to the new drive. Installboot took care of the boot file. ufsdump copied /dev and... (3 Replies)
Discussion started by: snorkack59
3 Replies

7. Solaris

mounting 2nd hard drive

Sun 280R, Solaris 5.8.... I have inserted a 2nd hard drive on my system. 'format' recognized the disk, but I cannot figure out how to access the disk. Any help is appreciated! (3 Replies)
Discussion started by: jalburger
3 Replies

8. SCO

Booting problem due to adding hard drive incorrectly

I have tried to (unsuccessfully) add an old drive to get drivers (for the 3Com network card) onto a Sco Openserver 5.1 server. Now it wont boot: I used Sco Admin to do this. It have 3 scuzzi drives I added an IDE I think what I did wrong was add the IDE to existing space, and I should not have... (6 Replies)
Discussion started by: lappies67
6 Replies

9. UNIX for Dummies Questions & Answers

Problem with damaged hard drive during bootup

Hello, I have a problem with the hard drive connected to my setup. When I connect the HDD which is damaged, and try to bring up my system, I get some error messages continuously on my console saying ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 frozen ata2.01: failed command:... (4 Replies)
Discussion started by: sai2krishna
4 Replies

10. UNIX for Beginners Questions & Answers

Problem setting path to external hard drive as a variable

Hello all, I am EXTREMELY new to using bash and I have a bit of a problem: I'm trying to set up a shell script that can 1.) take one of several giant files off of an external hard drive 2.) use it as input for scripts on my laptop's hard drive ... (3 Replies)
Discussion started by: machine_spirit
3 Replies
HDDTEMP(8)						      System Manager's Manual							HDDTEMP(8)

NAME
hddtemp - Utility to monitor hard drive temperature SYNOPSIS
hddtemp [options] [type:]disk... DESCRIPTION
hddtemp will give you the temperature of your hard drive by reading Self-Monitoring Analysis and Reporting Technology (S.M.A.R.T.) infor- mation on drives that support this feature. Only modern hard drives have a temperature sensor. hddtemp supports reading S.M.A.R.T. information from SCSI drives too. hddtemp can work as simple command line tool or as a daemon. You can specify one or more device drive path, where each path can be prefixed with a type like PATA, SATA or SCSI to force hddtemp too use one of these type (because detection can fail). OPTIONS
The program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. -b, --drivebase Display the database file that allows hddtemp to recognize a supported drive. -D, --debug Display various S.M.A.R.T. fields and their values. Useful for finding a value that seems to match the temperature and/or to send a report. (done for every drive supplied) -d, --daemon Execute hddtemp in TCP/IP daemon mode (port 7634 by default). -f, --file=file Specify the database file to use. -F, --foreground Don't fork into the background even in daemon mode. This is useful when running under a process supervisor. -l, --listen=addr Listen on a specific address. addr is a string containing a host name or a numeric host address string. The numeric host address string is a dotted-decimal IPv4 address or an IPv6 hex address. -n, --numeric Print only the temperature (without the unit). -p, --port=# Port number to listen to (in TCP/IP daemon mode). -s, --separator=char Separator to use between fields (in TCP/IP daemon mode). The default separator is `|'. -S, --syslog=s Switch to daemon mode and log temperatures to syslog every s seconds. -q, --quiet Don't check if the drive is supported. -u, --unit=C|F Force output temperature either in Celsius or Fahrenheit. -v, --version Display hddtemp version number. -w, --wake-up Wake-up the drive if needed (ATA drives only). -4 Listen on IPv4 sockets only. -6 Listen on IPv6 sockets only. DRIVE DATABASE
If you know your drive has a temperature sensor but it is being reported unsupported, tell me which model and which manufacturer it is, and/or just add a new entry in /etc/hddtemp.db. Each line of hddtemp.db is either a comment, a blank line or a line containing: - a regular expression that allow hddtemp to recognize a drive or a set of drives from its model name or from a generic model name, - a value (ATTRIBUTE_ID from S.M.A.R.T.), - a C or an F to set the unit to Celsius or Fahrenheit, - a description. Feedback is welcome (see the REPORT section below). TCP
/IP DAEMON MODE Example of type forcing: # hddtemp SATA:/dev/sda PATA:/dev/hda To test hddtemp in daemon mode, start it like this: # hddtemp -d /dev/hd[abcd] and use telnet or netcat (which is known as nc on some systems) to get a reply: # netcat localhost 7634 The drive database is read only once at startup, so hddtemp must be restarted if the database is updated for the changes to take effect. REPORT
As I receive a lot of reports, things must be clarified. When running hddtemp with debug options, hddtemp will show sort of a dump of S.M.A.R.T. data. Each field corresponds to an information field. The standard field for drive temperature is 194. But this is not always the case (mostly for older drives). Even if your drive has S.M.A.R.T. capabilities, it doesn't necessarily mean that it can report its temperature. So, things must be determined through experimentation. So, you can try to guess which field by is the good one by running hddtemp at regular intervals: - just after starting up your PC/server/station, - after opening a window (a physical window :), - after opening the case, - whatever you can think of... and looking for a field's value that would increase or decrease depending on what effect you want to induce. Be careful, fields 4, 9, and 12 are often reported to match a temperature field but after some investigation they do not. But fields 194 (which is the standard field for temperature) and 231 are good candidates. Then, you can send me a report with outputs from `hddtemp --debug ...', `smartctl' or `hdparm -i ...', and/or add an entry in hddtemp.db yourself. BUGS
If hddtemp crashes (yes, it might) for some unknown reasons, look for a file named hddtemp.backtrace.<PID>.XXXXXX (where XXXXXX is a random number generated at runtime) in /tmp. Then, you can then send me this file and the hddtemp binary. The backtrace functionality is cur- rently supported on i386 architectures only. SEE ALSO
smartctl(8), syslog(3), syslogd(8). AUTHOR
Emmanuel Varagnat (hddtemp@guzu.net). This manual page was originally written by Aurelien Jarno <aurel32@debian.org>, for the Debian GNU/Linux system (but may be used by oth- ers). July 21, 2003 HDDTEMP(8)
All times are GMT -4. The time now is 03:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy