Welcome, Guest. Please login or register.
Did you miss your activation email?
Friday 27 December 2024, 11:46:39 pm

Login with username, password and session length

Visit the Official Endian Bug tracker  HERE
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  Installation Support
| | |-+  Endian on HP DL380 G3 install error (community edition)
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Endian on HP DL380 G3 install error (community edition)  (Read 49703 times)
bodie
Full Member
***
Offline Offline

Posts: 10


« on: Thursday 29 October 2009, 06:18:58 pm »

Have beeb running Endian Community on a HP DL380 g3 for a while now .. and decided to reinstall to the new version 2.3
however the install just gets past the partitioning stage then errors

Unable to make root file system

hitting F2 and looking at the logs states

Running Command: /bin/mkfs.ext3 -b 4096 /dev/cciss/c0d0p5
mke2fs 1.39 (29-may-2006)
Could not stat /dev/cciss/c0d0p5 --- no such file or directory

the device apparently does not exist; did you specify it correctly.


only option is to reboot.

Checking /dev/c0d0p5 - and correct it doesn't exist - checked install on a standard HP (HP d51, IDE/PATA drives) and install works.

system did work with 2.2 but 2.3 rc and 2.3 both have the same error

can someone help??

bodie
Logged
bodie
Full Member
***
Offline Offline

Posts: 10


« Reply #1 on: Saturday 31 October 2009, 11:05:39 am »

OK checked out the partitons created and all partitions are there.

however looking through looks like no FS is on the extended partitoons (ext3)
any one know the loading sequence and where to locate the installation scripts?
Logged
bodie
Full Member
***
Offline Offline

Posts: 10


« Reply #2 on: Thursday 05 November 2009, 08:57:38 pm »

ok anyone with a DL360 or DL380 - or similar issue try the following

ok the work around ...
boot as normal with the Endian Firewall 2.3 CD

once booted up to blue screen on Endian 2.3 press alt f3 - to get to the shell
type the following

mknod -m660 /dev/cciss/c0d0p5 b 104 5
mknod -m660 /dev/cciss/c0d0p6 b 104 6
mknod -m660 /dev/cciss/c0d0p7 b 104 7

then press alt F1 and continue

looks like a small bug but hope this helps someone.

bodie
Compaq ProLiant DL380
Integrated Smart Array Controller ver 1.50
2 x 18 GB SCSI in RAID 1 configuration
Logged
bramfm
Jr. Member
*
Offline Offline

Posts: 1


« Reply #3 on: Friday 13 November 2009, 08:48:42 pm »

ok anyone with a DL360 or DL380 - or similar issue try the following

ok the work around ...


Bodie,

thanks, it works flawlessly. Thank you!

Marco
Logged
marcos
Jr. Member
*
Offline Offline

Posts: 2


« Reply #4 on: Wednesday 25 November 2009, 01:04:27 am »

ok anyone with a DL360 or DL380 - or similar issue try the following

ok the work around ...
boot as normal with the Endian Firewall 2.3 CD

once booted up to blue screen on Endian 2.3 press alt f3 - to get to the shell
type the following

mknod -m660 /dev/cciss/c0d0p5 b 104 5
mknod -m660 /dev/cciss/c0d0p6 b 104 6
mknod -m660 /dev/cciss/c0d0p7 b 104 7

then press alt F1 and continue

looks like a small bug but hope this helps someone.

bodie
Compaq ProLiant DL380
Integrated Smart Array Controller ver 1.50
2 x 18 GB SCSI in RAID 1 configuration


hi bodie,

i have a similar issue with Compaq ML 370 RAID 1 and EFW 2.3, but your workaround don't work for me!

My disks are recognized as /dev/ida/c0d0. I have created the partitions with mknod command

mknod -m660 /dev/ida/c0d0p5 b 104 5
mknod -m660 /dev/ida/c0d0p6 b 104 6
mknod -m660 /dev/ida/c0d0p7 b 104 7

but when i continue installation process, it fails

Running command: /bin/mkfs.ext3 -b 4096 /dev/ida/c0d0p5
mkfs.ext3: No such device or address while trying to determine filesystem size

and i can only reboot...

can you help me?

many thanks

marco
Logged
timupci
Full Member
***
Offline Offline

Posts: 34


« Reply #5 on: Thursday 28 January 2010, 08:48:22 am »

Thank you, this help me out quite a bit. Rolling out 7 DL380 and 1 ML530 with Endian 2.3 for OpenVPN configuration.

Just to confirm that this did work on the ML530 also.
Logged
FontanaChris
Jr. Member
*
Offline Offline

Posts: 1


« Reply #6 on: Wednesday 10 March 2010, 11:47:40 am »

Worked perfectly on a DL360 G5 with the P400i controller. Thanks for the tip.
Logged
sandoz
Jr. Member
*
Offline Offline

Posts: 4


« Reply #7 on: Tuesday 15 June 2010, 08:40:04 pm »

Using the above workaround, Endian installs on a DL360 G2 but fails to boot throwing a kernel panic.
See: efwsupport.com/index.php?topic=1798.0
Logged
ccline19
Jr. Member
*
Offline Offline

Posts: 9


« Reply #8 on: Monday 28 June 2010, 11:34:28 pm »

2.4 & DL 360
Has anyway come up with a solution for DL 360 that uses /dev/ida/c0d0 ?

I got the "unable to partition error" when tring to install. Looking at the logs it appears it created the 3 partitions...

/dev/ida/c0d0p1
/dev/ida/c0d0p2
/dev/ida/c0d0p3
/dev/ida/c0d0p4 - Empty

Successfully wrote the new partition table

Re-reading the partition table...
Running Command: modprobe dm-mod
Running Command: /bin/pvcreate --force --force --yes -- zero y /dev/ida/c0d03
file descriptor 3 left open
file descriptor 4 left open
file descriptor 5 left open
file descriptor 6 left open
file descriptor 7 left open
 Device /dev/ida/c0d03 not found

any ideas?
Logged
ccline19
Jr. Member
*
Offline Offline

Posts: 9


« Reply #9 on: Thursday 15 July 2010, 07:41:46 am »

I was able to figure out what was wrong. not sure why it worked but here is what I did.

DL 360 Server Raid Drives

Following brodies information I was able to make it work by changing the value 104 to match what was on the drives(72) already.
Before I performed the mknod command I changed to the /dev/ida/ dir and did a ls -l. This reported the dives where 72, not 104.
I modified the mknod with the new information and the continued the installation.

So,

mknod -m660 /dev/ida/c0d0p5 b 72 5
mknod -m660 /dev/ida/c0d0p6 b 72 6
mknod -m660 /dev/ida/c0d0p7 b 72 7

I hope this helps others,

Chris

Logged
elcid89
Jr. Member
*
Offline Offline

Posts: 1


« Reply #10 on: Sunday 19 September 2010, 12:09:47 pm »

Looking at the log, it is still trying to partition c0d03, which is a non-existent device. It should be accessing c0d0p3.

I saw a bug report on this which indicated that it had been fixed, but the iso I downloaded a few hours ago still has the error.
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.141 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com