Operating System - Linux
1753808 Members
7029 Online
108805 Solutions
New Discussion юеВ

Re: Debian Linux in DL380 G3

 
Andres Valentin Lopez
Occasional Advisor

Debian Linux in DL380 G3

Hi

I installed Debian Linux Sarge r3.1 in a Proliant DL380 Server G3, I have 2 disk, one of them has 8gb the other 146gb, the o.s. is installed in the first disk, all is ok. the 2nd disk has a ntfs partition that I want to delete but when I try to use sfdisk to delete/make a partition this is the result:

sfdisk /dev/cciss/c0d1 << EOF
> ;
> EOF
Checking that no-one is using this disk right now ...
OK

Disk /dev/cciss/c0d1: 35139 cylinders, 255 heads, 32 sectors/track
read: Input/output error

sfdisk: read error on /dev/cciss/c0d1 - cannot read sector 0
/dev/cciss/c0d1: unrecognized partition table type
Old situation:
No partitions found
New situation:
Units = cylinders of 4177920 bytes, blocks of 1024 bytes
read: Input/output error

sfdisk: read error on /dev/cciss/c0d1 - cannot read sector 0
Re-reading the partition table ...

Any suggestion

Thanks
3 REPLIES 3
Bruno Facca
Advisor

Re: Debian Linux in DL380 G3

Are both disks attached to the same controller? Do you have any logical volumes created for disk 2? Was the NTFS partition created on the server you're working on or the disk was on another server?

Bruno Facca
Wouter Jagers
Honored Contributor

Re: Debian Linux in DL380 G3

# fdisk -l
--> error ?

# parted
--> any more luck ? (another partition editor)

If the disk is not used now and it can be scratched completely, you could try wiping the current partition table first, the hard way:

# dd if=/dev/zero of= bs=512 count=1

(ANY DATA ON THIS DISK WILL BE GONE)

This should provide you with a 'virgin' disk which you could then partition from scratch.

Cheers,
Wout
an engineer's aim in a discussion is not to persuade, but to clarify.
Steven E. Protter
Exalted Contributor

Re: Debian Linux in DL380 G3

Shalom,

Try the partprobe command.

Then try again.

Try booting the system and then try again.

What may have happened though is the volume group was built based on one disk and there aren't enough extents to permit the second disk to be added to the volume group.

That leaves you the choice of putting the second disk in its own volume group or rebuilding a new, bigger capacity volume group, which will require downtime and a full backup. It might be easier to rebuild the entire system.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com