, Maybe you missed it....

2011-11-18 Thread Michael Havens
I just installed a new hard drive and it isn't showing up What do you think is wrong? I tried mount /dev/hd1 /mnt/hd1 but the reply was 'mount point does not exist' -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix

Re: , Maybe you missed it....

2011-11-18 Thread Stephen
Data drives are /dev/sda1 or /dev/hda1 for first drive of first partition increment a to b for 2nd drive and 1 to 2 for second partition. On Nov 18, 2011 4:29 PM, "Michael Havens" wrote: > I just installed a new hard drive and it isn't showing up What do you > think is wrong? I tried mount /dev/h

Re: , Maybe you missed it....

2011-11-18 Thread Michael Havens
same response after I added the 'a' On Fri, Nov 18, 2011 at 11:40 PM, Stephen wrote: > Data drives are /dev/sda1 or /dev/hda1 for first drive of first partition > increment a to b for 2nd drive and 1 to 2 for second partition. > On Nov 18, 2011 4:29 PM, "Michael Havens" wrote: > >> I just insta

Re: , Maybe you missed it....

2011-11-18 Thread Lisa Kachold
fdisk -l Will list all the drives seen by the system. If your drive is not there, check your cabling. Check your bios to see if it's there. If not there might be a power cable issue? On Fri, Nov 18, 2011 at 4:46 PM, Michael Havens wrote: > same response after I added the 'a' > > > On Fri, Nov

Re: , Maybe you missed it....

2011-11-18 Thread Michael Havens
I mis spoke it is a new-used drive. I've had it a while. 'fdisk' returns with an empty set and 'fdisk -l' returns an empty set too. 'fdisk /dev/hda1' returns with 'no such file or directory'. How do I check my bios? As for the possibility of there being a cabling issue, I've opened the cabinet an

Re: , Maybe you missed it....

2011-11-19 Thread Lisa Kachold
You have to be root to run fdisk -l # sudo fdisk -l On Fri, Nov 18, 2011 at 9:27 PM, Michael Havens wrote: > I mis spoke it is a new-used drive. I've had it a while. 'fdisk' returns > with an empty set and 'fdisk -l' returns an empty set too. 'fdisk > /dev/hda1' returns with 'no such file or d

Re: , Maybe you missed it....

2011-11-19 Thread Michael Havens
yeah, same response. blank line On Sat, Nov 19, 2011 at 2:31 PM, Lisa Kachold wrote: > You have to be root to run fdisk -l > > # sudo fdisk -l > > > On Fri, Nov 18, 2011 at 9:27 PM, Michael Havens wrote: > >> I mis spoke it is a new-used drive. I've had it a while. 'fdisk' returns >> with an emp

Re: , Maybe you missed it....

2011-11-19 Thread James Crawford
su - fdisk -l or sudo fdisk -l Should return the partition table of "ALL" drives that are visible to your system that includes the drive you are booting from. blank line implies you are not running fdisk with root permissions. James C. yeah, same response. blank line On Sat, Nov 19, 2011 at

Re: , Maybe you missed it....

2011-11-19 Thread Michael Havens
ubuntu@ubuntu:~$ sudo fdisk -l ubuntu@ubuntu:~$ It gives me nothing! On Sun, Nov 20, 2011 at 1:11 AM, James Crawford wrote: > su - > > fdisk -l or sudo fdisk -l Should return the partition table of "ALL" > drives that are visible to your system that includes the drive you are > booting from. >

Re: , Maybe you missed it....

2011-11-20 Thread Dazed_75
Try this Mike. Since you seem to be running on a live CD, you probably will not have the enter a password for the sudo. But enter the following commands cd ~/Desktop sudo lshw -short -C storage > lshw.txt sudo lshw -short -C disk >> lshw.txt sudo lshw -short -C volume >> lshw.txt and tell us what

Re: , Maybe you missed it....

2011-11-20 Thread Michael Havens
Okay buddy, I got a big nothing! ubuntu@ubuntu:~/Desktop$ cd ~/Desktop ubuntu@ubuntu:~/Desktop$ sudo lshw -short -C storage > lshw.txt ubuntu@ubuntu:~/Desktop$ sudo lshw -short -C disk >> lshw.txt ubuntu@ubuntu:~/Desktop$ sudo lshw -short -C volume >> lshw.txt ubuntu@ubuntu:~/Desktop$ On Sun, Nov

Re: , Maybe you missed it....

2011-11-20 Thread Dazed_75
You did not finish reading the instructions. The goal was to make a file called lshw.txt containing the results. Are you saying the file was not created (not possible) or that it was empty (I am guessing you did not look) or that you saw no output on the screen (which is what would be expected)?

Re: , Maybe you missed it....

2011-11-20 Thread Michael Havens
nothing returned was I supposed to enter something besides what you told me? I tried: ubuntu@ubuntu:~/Desktop$ print lshw.txt Error: no "print" mailcap rules found for type "text/plain" ubuntu@ubuntu:~/Desktop$ type lshw.txt bash: type: lshw.txt: not found ubuntu@ubuntu:~/Desktop$ and got the

Re: , Maybe you missed it....

2011-11-20 Thread Dazed_75
The text file lshw.txt should have been on your desktop. Just double click it to open it and see the contents. If you are doing email on that system, you can either copy the contents and paste them into the email, or add the files as an attachment to the email. On Sun, Nov 20, 2011 at 5:27 PM, M

Re: , Maybe you missed it....

2011-11-20 Thread Michael Havens
lshw was not to be found. I even tried 'find lshw.txt /' On Sun, Nov 20, 2011 at 5:33 PM, Dazed_75 wrote: > The text file lshw.txt should have been on your desktop. Just double > click it to open it and see the contents. If you are doing email on that > system, you can either copy the contents

Re: , Maybe you missed it....

2011-11-20 Thread Dazed_75
What live CD are you running? I thought someone had provided you with an ubuntu CD. lshw has been on every ubuntu disk since before dirt. if you were unable to run lshw, then obviously there would be no lshw.txt to look at. Several emails ago, you said you did: Okay buddy, I got a big nothing!

Re: , Maybe you missed it....

2011-11-20 Thread Michael Havens
I'm running ubuntu 11.10 On Sun, Nov 20, 2011 at 6:30 PM, Dazed_75 wrote: > What live CD are you running? I thought someone had provided you with an > ubuntu CD. lshw has been on every ubuntu disk since before dirt. if you > were unable to run lshw, then obviously there would be no lshw.txt t

Re: , Maybe you missed it....

2011-11-20 Thread R P Herrold
On Sun, 20 Nov 2011, Michael Havens wrote: lshw was not to be found. I even tried 'find lshw.txt /' clearly not valid "find" syntax ... find / -name lshw.txt would be one proper one -- Russ herrold --- PLUG-discuss mailing list - PLUG-di

Re: , Maybe you missed it....

2011-11-20 Thread Michael Havens
thanks for the correction still no dice On Sun, Nov 20, 2011 at 8:05 PM, R P Herrold wrote: > On Sun, 20 Nov 2011, Michael Havens wrote: > > lshw was not to be found. I even tried 'find lshw.txt /' >> > > clearly not valid "find" syntax ... >find / -name lshw.txt > would be one prop