not seeing the second disk
Robert Freeman-Day
presgas at gmail.com
Sun Aug 15 15:16:23 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 14 Aug 2010, Asif Iqbal wrote:
> Date: Sat, 14 Aug 2010 13:35:47 -0400
> From: Asif Iqbal <vadud3 at gmail.com>
> To: ubuntu-server at lists.ubuntu.com
> Subject: not seeing the second disk
>
> Hi
>
> I am running Ubuntu 10.04.1 LTS generic 64 bit on sun fire x4100. I do
> not see the second disk. Looks like it might have
> broken?!
>
> dm says this
>
> [ 31.785274] device-mapper: table: 252:0: multipath: error getting device
> [ 31.869735] device-mapper: ioctl: error adding target to table
> [ 40.751675] device-mapper: table: 252:0: multipath: error getting device
> [ 40.845887] device-mapper: ioctl: error adding target to table
> [ 41.400427] device-mapper: table: 252:0: multipath: error getting device
> [ 41.535076] device-mapper: ioctl: error adding target to table
>
>
> fdisk does not see it either
>
> $ fdisk -l
>
> Disk /dev/sdb: 73.0 GB, 72999763968 bytes
> 255 heads, 63 sectors/track, 8875 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0001d510
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 * 1 8508 68340478+ 83 Linux
> /dev/sdb2 8509 8875 2947927+ 5 Extended
> /dev/sdb5 8509 8875 2947896 82 Linux swap / Solaris
>
>
> diskstats only showing zeros for sda
>
> 8 16 sdb 89933 2366 2289639 458150 4216664 19869512 193144976
> 923094710 0 19996710 924689040
> 8 17 sdb1 89779 2105 2286343 457060 4216564 19867923 193131464
> 923090560 0 19995320 924683810
> 8 18 sdb2 4 0 8 90 0 0 0 0 0 90 90
> 8 21 sdb5 100 245 2760 360 100 1589 13512 4150 0 4150 4500
> 8 0 sda 0 0 0 0 0 0 0 0 0 0 0
>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
Asif,
Love the signature!
I would say it is likely it is dead, but something to confirm would be to
look at the output of "dmesg". There is also a logfile with similar data
called "/var/log/dmesg". Otherwise, you could see if it is OS related by
trying out a live CD...see if that OS can work with the drive.>
- ---Robert Freeman-Day
- ---------------
I would really like you to be on my side,
but the side you show me isn't what I had in mind.
- -Judybats
GPG Public Key:
http:keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0xBA9DF9ED3E4C7D36
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkxoBMcACgkQup357T5MfTanAwCdGoG9B0q1Idr5q0frvrlsIL8F
mDcAoJyV0PTV15tBftbDNofxnQZDPyPN
=5WTI
-----END PGP SIGNATURE-----
More information about the ubuntu-server
mailing list