Re: Dead brand new SCSI drive?

From: Edward Alfert (ealfert_at_rootmode.com)
Date: 02/14/04 

Date: 14 Feb 2004 19:32:29 GMT

Steve Schreiber <sschreibATTmagmaDOTTca> wrote in
news:ncydnRO9s7ef7LPdRVn-vA@magma.ca:

> I noticed the error you posted in your first email:
>
> Feb 14 12:11:02 blue kernel: Device 08:30 not ready.
> Feb 14 12:11:02 blue kernel: I/O error: dev 08:30, sector 0
>
>
> I am not certain (maybe someone could verify) if this is the maj/min
> number this error is refering to 8:30, on my system, 8,30 is sdb14.
>
>
> brw-rw---- 1 root disk 8, 30 Jan 30 2003 sdb14
>
>
> Your :
> 8 48 143666192 sdd 7 21 56 0 0 0 0 0 0 0 0
>
> line matches up to my device files. Is there anyway your devices files
> are mucked up? Unless someone can verify that is what the error is,
> this may not be of much help... but you can take a look at it and
> maybe determine for yourself.
>

I'm not sure what all that means, but here is a dump of relevant files
in /dev. Maybe they will mean something to you. I will in the mean
time search the internet for the keywords "maj" "min" "scsi" and see
what I come up with. I have no knowledge on this topic.

[root@blue dev]# ls -al | grep sd | grep 8 | grep 30
brw-rw---- 1 root disk 8, 30 Apr 11 2002 sdb14
brw-rw---- 1 root disk 68, 30 Apr 11 2002 sdbn14
brw-rw---- 1 root disk 68, 130 Apr 11 2002 sdbu2
brw-rw---- 1 root disk 68, 230 Apr 11 2002 sdca6
brw-rw---- 1 root disk 8, 130 Apr 11 2002 sdi2
brw-rw---- 1 root disk 8, 230 Apr 11 2002 sdo6
[root@blue dev]# ls -al | grep sdd
brw-rw---- 1 root disk 8, 48 Apr 11 2002 sdd
brw-rw---- 1 root disk 8, 49 Apr 11 2002 sdd1
brw-rw---- 1 root disk 8, 58 Apr 11 2002 sdd10
brw-rw---- 1 root disk 8, 59 Apr 11 2002 sdd11
brw-rw---- 1 root disk 8, 60 Apr 11 2002 sdd12
brw-rw---- 1 root disk 8, 61 Apr 11 2002 sdd13
brw-rw---- 1 root disk 8, 62 Apr 11 2002 sdd14
brw-rw---- 1 root disk 8, 63 Apr 11 2002 sdd15
brw-rw---- 1 root disk 8, 50 Apr 11 2002 sdd2
brw-rw---- 1 root disk 8, 51 Apr 11 2002 sdd3
brw-rw---- 1 root disk 8, 52 Apr 11 2002 sdd4
brw-rw---- 1 root disk 8, 53 Apr 11 2002 sdd5
brw-rw---- 1 root disk 8, 54 Apr 11 2002 sdd6
brw-rw---- 1 root disk 8, 55 Apr 11 2002 sdd7
brw-rw---- 1 root disk 8, 56 Apr 11 2002 sdd8
brw-rw---- 1 root disk 8, 57 Apr 11 2002 sdd9
brw-rw---- 1 root disk 70, 128 Apr 11 2002 sdda
<snip> It keeps going for many more lines until the last line which
follows: <snip>
brw-rw---- 1 root disk 71, 249 Apr 11 2002 sddx9

> To zero a disk with `dd` issue: `dd if=/dev/zero of=/dev/<device>
> bs=512 count=(x)` <device> in your case would be /dev/sdd, and (x) is
> pretty much whatever you want...

I just tried your suggestion and I still cannot fdisk. Following is the
result:

[root@blue root]# dd if=/dev/zero of=/dev/sdd bs=512 count=1
1+0 records in
1+0 records out
[root@blue root]# fdisk /dev/sdd
Unable to read /dev/sdd

> As for putting in a disklabel, I am not
> certain how to do it on Linux. fdisk should have (?) a 'default'
> disklabel it can put to the disk. Some Unix equivs. have problems
> with disk with no disklabeling on them, so have this feature (although
> I would assume that Linux would not have these problems since it is
> not brain-damaged as most propriatary Unix flavours). Something else
> to look at.

When I do an fdisk -l it does not list the Maxtor drive, but it does
list the new Fujitsu (which I still have not formatted or partitioned).

[root@blue root]# fdisk -l

Disk /dev/sda: 255 heads, 63 sectors, 8924 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 fd Linux raid autodetect
/dev/sda2 14 78 522112+ fd Linux raid autodetect
/dev/sda3 79 8924 71055495 fd Linux raid autodetect

Disk /dev/sdb: 255 heads, 63 sectors, 8924 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 13 104391 fd Linux raid autodetect
/dev/sdb2 14 78 522112+ fd Linux raid autodetect
/dev/sdb3 79 8924 71055495 fd Linux raid autodetect

Disk /dev/sdc: 255 heads, 63 sectors, 8936 cylinders
Units = cylinders of 16065 * 512 bytes

Disk /dev/sdc doesn't contain a valid partition table

> The only other problem I have had with SCSI drives that really
> screwed me up was the Adaptec built-in low level format tool. I
> canceled out of it once about half way though (an hour in) and I
> couldn't do anything with the disk until I went through the whole
> process again-but letting it finish! I don't suppose you formatted it
> with this tool did you?
 
I have not gone into any scsi utilities and messed with the drives. So
I do not believe this is the cause.

Thanks for all your help so far. I'm learning. 

-- 
Edward Alfert - http://www.rootmode.com/
Coupon Code (Recurring $5/month Discount): newsgroup
Multiple Domain Hosting * Private Label Nameservers

Relevant Pages

  • Re: Error 16: Inconsistent filesystem structure
    ... My preference would be a /home partition to protect my data ... Here is a copy of the output of fdisk -l and fdisk /dev/sdb with x then ... I used the Negus Fedora 7 book's Live cd. ... Disk /dev/sdb: 200.0 GB, 200049647616 bytes ...
    (Fedora)
  • Re: Samba and RAID 1 using gmirror on 2 new disks
    ... This resolved the SCSI parity error. ... fdisk: ... I also want to have the server run scheduled backups of the mirror disk. ... I am not able to initialize da1 and da2 successfully. ...
    (freebsd-questions)
  • Re: Physical Disk Size
    ... I have just found the info in dmesg when i do a "dmesg |grep SCSI", ... The fdisk -l does not come back with anything, ... The dmesg does not give me the disk size in the output either. ... This transmission is confidential and must not be used or disclosed by ...
    (RedHat)
  • Re: dual booting (installed ubuntu then windows 2003 serv)
    ... The number of cylinders for this disk is set to 14593. ... (e.g., DOS FDISK, OS/2 FDISK) ... hda2 that there's reference to /dev/hda1 in grub menu.lst, ...
    (comp.os.linux.misc)
  • Re: need help repairing this system... mount issues
    ... > i am able to boot, but i'm having some issues now. ... Uh -- which sort of disk drive do you have? ... driver, SCSI use 'da'. ... the device files are missing, you can generate them from single user ...
    (freebsd-questions)