LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   New Devices? (https://www.linuxquestions.org/questions/linux-newbie-8/new-devices-4175439424/)

adol83 11-30-2012 04:27 AM

New Devices?
 
Hello,

Version : Rhel

Problem : I connected via USB an Hard Drive in the back of my computer but I cannot find the device.

What I did :

Code:

[root@localhost home]cat /proc/partitions
major minor  #blocks  name

  8      48  625131864 sdd
  8      49  625129281 sdd1
  8        0  40146624 sda
  8      16  58615704 sdb
  8      17    512000 sdb1
  8      18  58101760 sdb2
  8      32  976762584 sdc
  8      33  976762583 sdc1
 253        0  27697152 dm-0
 253        1  10272768 dm-1
 253        2  20127744 dm-2
 253        3 1048576000 dm-3
 253        4  553312256 dm-4

Then

Code:

[root@localhost home]cat /proc/partitions
Impossibile leggere da /dev/sda

Note : "Impossibile leggere da" it's "Impossible to read from" in english.
Note 2 : I added 2 hard disk inside my computer but looks like i couldn't see them.

I'm having confusion with my devices.

RaviTezu 11-30-2012 04:44 AM

Hi adol83,

First thing you have to do is dmesg as a root.

1.Just type "dmesg"(without quotations) in command line

2.Now connect your USB Hard disk.

3. You should see a message saying the some device has been attached & the name allotted to it.

For Ex: name will be like /dev/sdb or /dev/sdc ..etc.


**Note: If you didn't see any message like this |======>it may imply that your kernel is not having the respective drivers to detect that USB hard disk.

Try updating you kernel. it may help you.

RaviTezu 11-30-2012 04:53 AM

Sorry,

You should try running "dmesg" after connecting the USB Hard disk.

RaviTezu 11-30-2012 04:54 AM

& Make sure your USB port(Computer) is working properly.

RaviTezu 11-30-2012 04:58 AM

FYI:
When i connect my USB drive:

[1823104.846072] usb 7-2: new full-speed USB device number 2 using uhci_hcd
[1823105.001082] usb 7-2: not running at top speed; connect to a high speed hub
[1823105.035083] usb 7-2: New USB device found, idVendor=8564, idProduct=1000
[1823105.035088] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1823105.035093] usb 7-2: Product: Mass Storage Device
[1823105.035097] usb 7-2: Manufacturer: JetFlash
[1823105.035101] usb 7-2: SerialNumber: 13EV167HMH1SDMAV
[1823105.039344] scsi6 : usb-storage 7-2:1.0
[1823106.338148] scsi 6:0:0:0: Direct-Access JetFlash Transcend 4GB 1100 PQ: 0 ANSI: 0 CCS
[1823106.339646] sd 6:0:0:0: Attached scsi generic sg1 type 0
[1823106.344113] sd 6:0:0:0: [sdb] 7913472 512-byte logical blocks: (4.05 GB/3.77 GiB)
[1823106.347099] sd 6:0:0:0: [sdb] Write Protect is off
[1823106.347107] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[1823106.350107] sd 6:0:0:0: [sdb] No Caching mode page present
[1823106.350114] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[1823106.368100] sd 6:0:0:0: [sdb] No Caching mode page present
[1823106.368107] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[1823106.374158] sdb: sdb1
[1823106.387696] sd 6:0:0:0: [sdb] No Caching mode page present
[1823106.387704] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[1823106.387709] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[1823107.518116] SELinux: initialized (dev sdb1, type vfat), uses genfs_contexts
[1823126.128287] sdb: detected capacity change from 4051697664 to 0
[1823128.500127] usb 7-2: USB disconnect, device number 2


Got printed in dmesg.

You should see this kind of messages.When your kernel detects the USB hard disk.

RaviTezu 11-30-2012 04:59 AM

[1823128.500127] usb 7-2: USB disconnect, device number 2

Shows the USB is disconnected.

adol83 11-30-2012 05:21 AM

2 Attachment(s)
Here comes the logs.

I had to size them because of the lenght, since this is a small log (less than 500 kb) i hope moderators let me keep files in this way for you to understand.

I'm beginning to read them now.

RaviTezu 11-30-2012 06:06 AM

Hey,

The messages will be logged at the end(may be in last 10-15 lines).

Just connect your USB disk & check it using dmesg now.

adol83 11-30-2012 07:17 AM

As soon as i'll return at home i will do it.

Sometimes there is a power loss in the district i'm living, that could be an issue.

RaviTezu 11-30-2012 07:30 AM

*******Just check the logs********

-> if you got the device name.,just mount it. & you can play with the device then.


->If not., post the last 20 lines for dmesg here..will help you,if i can. :)

**Note: check with dmesg after connecting the device. make sure the USB port is working(there should be some indicator on the device).

frankbell 11-30-2012 09:07 PM

You could also try running fdisk -l as root with the device connected. If the device is being seen, it will show in the list of partitions.

It should also tell you something about the file system that's on it. That information might be useful.

I got a new USB external drive once and Debian wasn't seeing it; it was formatted NTFS, and Debian does not include NTFS drivers by default (though they can be added).

I don't know off the top of my head whether RHEL and CentOS do include them by default, but it's an avenue to explore.

TobiSGD 12-01-2012 07:28 AM

I have had a look at the logs you attached and it seems that your /dev/sda disk is simply broken. I would recommend to test the disk with the manufacturer's diagnosis tool.

adol83 12-04-2012 06:02 AM

TobiSGD are you sure about that?

/dev/sda is a flash unit and it should be work properly since the entire system is over that and yet CentOs start from that.

I added two disks in the desktop and maybe one of them could get an issue like you said.

I will check as soon as i can since these days i'm a little busy.

Thank you in the meanwhile, i will look forward.

TobiSGD 12-04-2012 06:58 AM

According to the logs you have a 40GB Maxtor disk connectet via IDE, a Corsair Force 3 SSD, a seagate disk and a Western Digital disk, all connected via SATA.
The devices recognized as sda, sdb and sdc doen't seem to have partitions on them, device sdd has two partions, sdb1 and sdb2. There is an USB device that sporadicaly spits out read errors:
Code:

usb 2-1.6: device descriptor read/64, error -32
and the device that the kernel sees as ata1.01 (the Maxtor disk) also spews out failed commands and exceptions. I assume that the kernel sees this disk as /dev/sda, not the Flash device.

I would recommend to test both devices, at least the Maxtor disk seems to be faulty.


All times are GMT -5. The time now is 02:20 AM.