Prev: Tar to another computer follow up: The semaphore timeout periodhas expired
Next: I don't get ssh.. more secure? Making better passwords.
From: Stuart Gall on 19 Jun 2010 12:46
On 2010-06-18 21:58:32 +0300, "David W. Hodgins"
<dwhodgins(a)nomail.afraid.org> said:

> On Fri, 18 Jun 2010 10:02:41 -0400, Stuart Gall <stuart(a)otenet.gr> wrote:
>
>> Some sata disks connected to the system do not get their partition
>> device created.
>> So say SDB
>> /dev/sdb exists
>> /dev/sdb1 is missing
>
> Has the drive ever been used as part of a raid cluster? It may
> be necessary to overwrite the raid signature, which may be near
> the start of the partition, or the end, depending on which raid
> version was used.
>
> http://www.linuxquestions.org/questions/linux-general-1/proc-partitions-showing-wrong-partitions-264602/

Regards,
>
> Dave Hodgins
>
> -- Change nomail.afraid.org to ody.ca to reply by email.
> (nomail.afraid.org has been set up specifically for
> use in usenet. Feel free to use it yourself.)


No(*) but this is a good idea. Unfortunately it did not fix the issue.

(*) One system has 5 identical drives in a raid 5 array.
2 of the drives do not get their partition device links created the other 3 do.

The other system is new with a new previously NTFS file system.

On system 1 I removed a dosk from the array
Erased the first 300MB
Recreated the partition table.
Addedd the drive back, resynched
AND IT STILL DOES NOT GET UDEVED RIGHT !

Same on the new system (its new) I erased 300M fdisk, mkfs
No good.

The first system is an old Debian dist the new is Mandriva.

This is so strange.

I think I must try swapping the disks, maybe hardware.


--
TIA
Stuart
--
There are three kinds of mathematician
Those that can count and those that cant.

From: David W. Hodgins on 19 Jun 2010 14:04
On Sat, 19 Jun 2010 12:46:20 -0400, Stuart Gall <stuart(a)otenet.gr> wrote:

> On system 1 I removed a dosk from the array
> Erased the first 300MB
> Recreated the partition table.
> Addedd the drive back, resynched
> AND IT STILL DOES NOT GET UDEVED RIGHT !

https://raid.wiki.kernel.org/index.php/Superblock

The superblock may be near the end of the device.

Regards, Dave Hodgins

-- Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)
From: Jerry Peters on 19 Jun 2010 16:17
Stuart Gall <stuart(a)otenet.gr> wrote:
> Hello,
> I have a strange issue and I have it on two unrelated systems.
> One system has been working fine for over a year. (Debian 4.1.1-21) but
> after a power failure started misbehaving
>
> The other is a new system installed a few days ago. (Mandriva 2010.0 x86_64)
>
> Some sata disks connected to the system do not get their partition
> device created.
> So say SDB
> /dev/sdb exists
> /dev/sdb1 is missing
>
> I do
> fdisk /dev/sdb
> w
>
> i.e. just rewrite the partition table with no changes.
>
> Then the /dev/sdb1 is created, and can be mounted. But reboot and its
> gone again.
>
>
> I see no diferance on dmesg
>
> scsi 0:0:0:0: Direct-Access ATA WDC WD2502ABYS-0 02.0 PQ: 0 ANSI: 5
> sd 0:0:0:0: [sda] 490350672 512-byte logical blocks: (251 GB/233 GiB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >
> sd 0:0:0:0: [sda] Attached SCSI disk
> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata2.00: ATA-8: WDC WD1002FBYS-02A6B0, 03.00C06, max UDMA/133
> ata2.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32)
> ata2.00: configured for UDMA/133
> scsi 1:0:0:0: Direct-Access ATA WDC WD1002FBYS-0 03.0 PQ: 0 ANSI: 5
> sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
> sd 1:0:0:0: [sdb] Write Protect is off
> sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sdb: sdb1
> sd 1:0:0:0: [sdb] Attached SCSI disk
>
>
>
> NB
> sdb:sdb1
> But /dev/sdb1 is not created.
>
> Any ideas on when the /dev/sdxx links are created and/or how I can
> debug this further ???

I have the same problem with one USB flash drive, a Sandisk Cruzer 8G.
A Sandisk Cruzer 4GB drive works correctly.

What I think is happening is that the drive becomes partly ready,
enough to get its id, but doesn't respond to the partition probe, or
responds with an empty block as nothing shows up in /proc/partitions
for the drive, blkid fails to find it & mount by label fails with
"label not found".

I have a static device entry for sdb*, so I can mount the partition by
"mount /dev/sdb1 /mnt" and it works.

Fdisk is forcing a reread of the partition table for the device, which
is why the partition shows up after the 'w'. If you have the partprobe
utility, it will do the same thing.

Jerry
From: Stuart Gall on 22 Jun 2010 10:32
On 2010-06-19 21:04:03 +0300, "David W. Hodgins"
<dwhodgins(a)nomail.afraid.org> said:

> On Sat, 19 Jun 2010 12:46:20 -0400, Stuart Gall <stuart(a)otenet.gr> wrote:
>
>> On system 1 I removed a dosk from the array
>> Erased the first 300MB
>> Recreated the partition table.
>> Addedd the drive back, resynched
>> AND IT STILL DOES NOT GET UDEVED RIGHT !
>
> https://raid.wiki.kernel.org/index.php/Superblock
>
> The superblock may be near the end of the device.
>
> Regards, Dave Hodgins
>
> -- Change nomail.afraid.org to ody.ca to reply by email.
> (nomail.afraid.org has been set up specifically for
> use in usenet. Feel free to use it yourself.)


Thank you!
With this in mind and also possible disk hardware problems. I ran

badblocks -s -w /dev/sdb

To check and completely erase the disk. No bad blocks.

After that, reformatted and it works fine.?!!?

Must have got some data somewhere which confused udev.

--
TIA
Stuart
--
There are three kinds of mathematician
Those that can count and those that cant.

From: J G Miller on 22 Jun 2010 11:13
On Tue, 22 Jun 2010 17:32:35 +0300, Stuart Gall wrote:

> With this in mind and also possible disk hardware problems. I ran
>
> badblocks -s -w /dev/sdb
>
> To check and completely erase the disk. No bad blocks.
>
> After that, reformatted and it works fine.?!!?
>
> Must have got some data somewhere which confused udev.

Is this in fact because it has forced the hard drive firmware
to remap the bad block as being unusable so they OS no longer
tries to use them?

So your available disk space will be just slightly less
than it was before?
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Tar to another computer follow up: The semaphore timeout periodhas expired
Next: I don't get ssh.. more secure? Making better passwords.