11.3 partitioner not detecting all drives.

Greetings!

I just got OpenSuSe 11.3 installed in a machine with two 160GB drives.

I took all defaults at installation, works fine.
Going to YaST expecting to detect and partition it. Not there.
System Information, however ‘sees’ both disks.

How do I partition and attach this disk?
Have fun,

Paxton

Might be worth us seeing your fdisk info. Please open a terminal, become su -
And post result of

fdisk -l

If you can show us an expanded tree image of what you see in Yast, that will help too.
Paste at:
SUSE Paste
Selecting Image form the ‘Language’ drop box
Never delete

I think it means you installed LVM, where the system sees the one logical volume instead of 2 physical volumes.

If this is the case, you can type : lvdisplay -c

Greetings!
Thanks for the rapid responses. I did not use LVM (not the default).

I did run fdisk -l and, as expected, it shows the one disk:
linux-5epx:/home/paxton # fdisk -l

Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 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: 0x0004c9f5

Device Boot Start End Blocks Id System
/dev/sda1 1 262 2103296 82 Linux swap / Solaris
Partition 1 does not end on cylinder boundary.
/dev/sda2 * 262 2873 20972544 83 Linux
/dev/sda3 2873 19458 133213184 83 Linux
linux-5epx:/home/paxton #

I apologize, but I do not know how to capture an image from the SUSE desktop. I have those sorts of things for my Windoze machines, but not for the Linux machines.
Would appreciate knowing the apps to use for this.

Anyhow, I can report, that the partitioner tree shows only the one disk, sda.

If I look at Yast - Hardware - Hardware Information, I see under ‘DASD Disks’
SP1604N(/dev/sda)
SP1604N(/dev/sdb)

The same data are repeated under ‘Disk’

The Yast hardware scanner finds them both, but the Partitioner only finds the first one.

More info I can get for you?
Other ideas?
Thanks, and
Have fun,
Paxton

On 2011-02-23 16:06, paxton wrote:

> I apologize, but I do not know how to capture an image from the SUSE
> desktop.

The printscreen key. If it doesn’t work, there are several apps than
capture the display, even “gimp”.

Look for clues in /var/log/boot.msg


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Greetings!
Well, nice to know about \var\log\boot.msg. Lots of info there, I always wondered if the boot messages were captured.

Anyhow, I want to note that the two disks passes Samsung’s full testing and then I low level formatted them before I loaded 11.3.
I say this because it looks like the boot process complained about them. Also, the machine has new memory, but I did not run memtest on it, but I will.

try this link to see my boot.msg
http://dev.thedce.com/suse/boot.msg

Have fun, paxton

The link to boot.msg worked fine. Select, copy, paste works for text and images in terminal mode or from your Windows install. You can paste to SUSE Paste that will give you a link to images and code, if you use the forums. If you use USENET, then you should place the output between [foo] and [/foo] replacing the word “foo” with the word “code”.

You shouldn’t need to low level format a drive anymore, just normal format of Ext3/4 for linux or ntfs for Windows partitions.
Your sdb is not getting mounted during the boot process that’s for sure. Both fdisk and partitioner should show both drives.
If you run


su -c "fdisk -l" 
### prompts for root password 
Password: 

do you see both drives?
One thing, maybe you use cable select or both your drives are set to be master on the same IDE cable. I know 2 masters on the same IDE cable throws one offline.

Greetings!

fdisk still shows just the one drive.
(now fdisk from a DOS boot disk does show both drives)

Maybe I forgot to mention the configuration. On ide0 is a single
master (160GB) <this is the one used by the install>
On ide1 is a master (160Gb) and a slave optical drive.

Along the way, I learned linux seems to want to install on the
disk that is a master with no slave even if on ide1.
When doing installs (tried several distros) in this configuration,
the system installs on IDE1, and, apparently leaves it in an
unbootable condition. Never tracked down why.

Moving the slave Optical drive to IDE1 caused a good intall to the disk
at IDE0, but does not recognize the master drive on IDE1.

Would like to mount the second disk to use as a backup storage location.

Thanks for everyone’s attention. it is kind of an old cheap motherboard, maybe that is the culprit. The IDE ports.

Have fun,
Paxton

On 2011-02-23 17:06, paxton wrote:

> try this link to see my boot.msg
> http://dev.thedce.com/suse/boot.msg

Well, that log shows many errors on sdb. I don’t know what they mean, not
exactly, but you could try changing the cable.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

On 2011-02-23 19:36, tararpharazon wrote:

> If you use USENET, then you
> should place the output between and replacing the word
> “foo” with the word “code”.

Between what? :slight_smile:
The gateway eat that. Had to look it up in the web.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I don’t think that’s a case as I’ve installed openSUSE to sdb.
OTOH, you could move your optical drive onto the IDE0 (I’m assuming IDE0 is the first IDE port) and visually check the jumper settings on all your drives.
Or you could make the second drive a slave on IDE0 and the optical drive a master on IDE1, though it sounds better practice to set HDDs as masters on 2 separate IDE cables.
While you’re checking your system BIOS you should check the boot sequence/order.
There’s has to be a simple reason why the second HDD doesn’t register with fdisk -l or partitioner.

Once the second HDD is recognized by fdisk and partitioner, you can format ext4 and assign it any label you want.
Typically, many of us use 3 partitions created out of an extended partition, / (root) 20-30Gb, /home and /swap <= 2Gb to install Linux.
This way your /home remains intact when you upgrade your system or install a different system.
When / (root), /home and /swap are on the same partition, formatting the drive for an upgrade would format your /home.

On 2011-02-23 22:06, tararpharazon wrote:

> There’s has to be a simple reason why the second HDD doesn’t register
> with fdisk -l or partitioner.

Yes, look it up in the boot log. Too many errors, disk is deactivated.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Also, pls post output from


tail -n 30 /var/log/messages

Greetings!

Swapping cables is alwasys a good idea. This time it is new, but did swap anyhow, no
change…everything seems to be strapped correctly, BIOS shows the disks fine, DOS Fdisk shows them
fine. Maybe it is the IDE ports or the chipset, it is a cheap PCChips board (M848A).
Other ideas appreciated. Will examing the boot.msg some more.

Have fun,
Paxton

Greetings,
Happy to post the results of tail -n 30 /var/log/messages
but you should know that a large file transfer job is also running.
I am setting up this machine to replace a current SuSE 9.2 Samba server on my network,
so am transferring files from that machine.
anyhow, here are the results… does not tell me much :slight_smile:
linux-5epx:/home/paxton # tail -n 30 /var/log/messages
Feb 24 08:56:08 linux-5epx smbd[9255]: getpeername failed. Error was Transport endpoint is not connected
Feb 24 08:56:08 linux-5epx smbd[9255]: [2011/02/24 08:56:08.550535, 0] lib/util_sock.c:675(write_data)
Feb 24 08:56:08 linux-5epx smbd[9255]: [2011/02/24 08:56:08.555069, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Feb 24 08:56:08 linux-5epx smbd[9255]: getpeername failed. Error was Transport endpoint is not connected
Feb 24 08:56:08 linux-5epx smbd[9255]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Feb 24 08:56:08 linux-5epx smbd[9255]: [2011/02/24 08:56:08.556139, 0] smbd/process.c:79(srv_send_smb)
Feb 24 08:56:08 linux-5epx smbd[9255]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Feb 24 09:08:26 linux-5epx rsyslogd: – MARK –
Feb 24 09:18:28 linux-5epx smartd[2687]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 121 to 115
Feb 24 09:28:08 linux-5epx smbd[9392]: [2011/02/24 09:28:08.666272, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Feb 24 09:28:08 linux-5epx smbd[9392]: getpeername failed. Error was Transport endpoint is not connected
Feb 24 09:28:08 linux-5epx smbd[9392]: [2011/02/24 09:28:08.674985, 0] lib/util_sock.c:675(write_data)
Feb 24 09:28:08 linux-5epx smbd[9392]: [2011/02/24 09:28:08.675623, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Feb 24 09:28:08 linux-5epx smbd[9392]: getpeername failed. Error was Transport endpoint is not connected
Feb 24 09:28:08 linux-5epx smbd[9392]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Feb 24 09:28:08 linux-5epx smbd[9392]: [2011/02/24 09:28:08.676471, 0] smbd/process.c:79(srv_send_smb)
Feb 24 09:28:08 linux-5epx smbd[9392]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Feb 24 09:48:26 linux-5epx rsyslogd: – MARK –
Feb 24 09:48:29 linux-5epx smartd[2687]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 115 to 121
Feb 24 10:05:41 linux-5epx kernel: [66031.216622] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0)
Feb 24 10:26:16 linux-5epx kernel: [67266.585067] [drm] nouveau 0000:01:00.0: Setting dpms mode 1 on vga encoder (output 0)
Feb 24 10:32:07 linux-5epx kernel: [67617.026969] [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on vga encoder (output 0)
Feb 24 10:32:08 linux-5epx smbd[9690]: [2011/02/24 10:32:08.922015, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Feb 24 10:32:08 linux-5epx smbd[9690]: getpeername failed. Error was Transport endpoint is not connected
Feb 24 10:32:08 linux-5epx smbd[9690]: [2011/02/24 10:32:08.933538, 0] lib/util_sock.c:675(write_data)
Feb 24 10:32:08 linux-5epx smbd[9690]: [2011/02/24 10:32:08.934174, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Feb 24 10:32:08 linux-5epx smbd[9690]: getpeername failed. Error was Transport endpoint is not connected
Feb 24 10:32:08 linux-5epx smbd[9690]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Feb 24 10:32:08 linux-5epx smbd[9690]: [2011/02/24 10:32:08.941215, 0] smbd/process.c:79(srv_send_smb)
Feb 24 10:32:08 linux-5epx smbd[9690]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
linux-5epx:/home/paxton #

Yes this output just shows errors in smbd. Sorry to admit I’m out of ideas if DOS fdisk and BIOS shows both drives but openSUSE only shows one.
Try again


cat /var/log/messages | grep -iv smbd  | tail -n 40 
## and under openSUSE
sudo fdisk  -l

Pls use SUSE Paste or post output between [foo] and [/foo] replacing the word “foo” with “code”.

On 2011-02-24 20:36, tararpharazon wrote:
>
> Yes this output just shows errors in smbd. Sorry to admit I’m out of
> ideas if DOS fdisk and BIOS shows both drives but openSUSE only shows
> one.

Linux does initally see the partitions in sdb, but there are dozens of
errors on sdb and the disk is finally disabled. You people have to
concentrate on solving those errors, looking elsewhere is irrelevant.

<6> 174.341268] ata2: EH complete
<6> 174.341301] sd 1:0:0:0: [sdb] Unhandled error code
<6> 174.341305] sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
<6> 174.341310] sd 1:0:0:0: [sdb] CDB: Read(10): 28 00 00 00 00 00 00 00
08 00
<3> 174.341321] end_request: I/O error, dev sdb, sector 0
<3> 174.341334] Buffer I/O error on device sdb, logical block 0

That msdos sees the drive is irrelevant. Full blown windows would be
different, or another linux version. If those fails, there is a hardware
problem.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

Yes true and I thought we were looking for the reason openSUSE can not mount that drive. Checking cables, BIOS and jumpers is basic trouble shooting, right?
You make an excellent suggestion to use the Windows Partitioner to format sdb NTFS just to see if openSUSE would then recognize the second drive.

Otherwise, its a hardware error in the HDD, m/b or an openSUSE bug.

On 2011-02-24 22:06, tararpharazon wrote:
>
> Yes true and I thought we were looking for the reason openSUSE can not
> mount that drive. Checking cables, BIOS and jumpers is basic trouble
> shooting, right?

Yep.

> You make an excellent suggestion to use the Windows Partitioner to
> format sdb NTFS just to see if openSUSE would then recognize the second
> drive.

I wasn’t thinking of formatting as ntfs, but it would be interesting to see
if it is possible.

> Otherwise, its a hardware error in the HDD, m/b or an openSUSE bug.

I have the suspicion that 11.3 is more delicate, so I would suggest trying
11.2 or 1.4.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)