Problems with 3.0.5 installer

Discussion:

Morten Johansen

2007-04-06 16:15:17 UTC

Guys, I ran into a minor problem while installing TSL 3.0.5 on a HP
DL320 G3 server.

The server had a SCSI controller with one blank (brand new) SCSI disk on
it (not CCISS controller).
Choosing "autopartition" caused the installer to crap out with the error
message "program anaconda is using a deprecated SCSI ioctl", and some
other good stuff. The installer couldn't get the kernel to re-read the
partition table after partitioning.

I have a few screen shots that I made, I was also going to try to
reproduce the problem in VMware, but I wanted to check with the list
first. Is this a known problem? If not, where do I send the more
detailed info and debug data?

Cheers :)

- --
Morten Johansen <***@monet.no>
+47 900 61 494

Randal T. Rioux

2007-04-07 02:44:03 UTC

Permalink

Post by Morten Johansen
Guys, I ran into a minor problem while installing TSL 3.0.5 on a HP
DL320 G3 server.
The server had a SCSI controller with one blank (brand new) SCSI disk on
it (not CCISS controller).
Choosing "autopartition" caused the installer to crap out with the error
message "program anaconda is using a deprecated SCSI ioctl", and some
other good stuff. The installer couldn't get the kernel to re-read the
partition table after partitioning.
I have a few screen shots that I made, I was also going to try to
reproduce the problem in VMware, but I wanted to check with the list
first. Is this a known problem? If not, where do I send the more
detailed info and debug data?

Morten Johansen

2007-04-07 10:00:30 UTC

Permalink

Post by Randal T. Rioux
I think Compaq/HP intentionally made the DLxxx series considerably
un-Linux friendly. I always have a Hellish time installing any distro.

Ivan Brunello

2007-04-10 08:34:14 UTC

Permalink

I had several problems w/ DL360 integrated RAID & kernel 2.6, due to
high-performance sheduler settings on latest kernel.

I ended up installing TSL2.2, and everything went fine.

Not tested on latest 2.6 kernels: meanwhile I switched work, and now I work
on IBM xSeries (and it's quite well supported ips driver) only.

Ivan

Send tsl-discuss mailing list submissions to
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.trustix.org/mailman/listinfo/tsl-discuss
or, via email, send a message with subject or body 'help' to
You can reach the person managing the list at
When replying, please edit your Subject line so it is more specific
than "Re: Contents of tsl-discuss digest..."
1. Problems with 3.0.5 installer (Morten Johansen)
2. Re: Problems with 3.0.5 installer (Randal T. Rioux)
3. Re: Problems with 3.0.5 installer (Morten Johansen)
----------------------------------------------------------------------
Message: 1
Date: Fri, 06 Apr 2007 18:15:17 +0200
Subject: Problems with 3.0.5 installer
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Guys, I ran into a minor problem while installing TSL 3.0.5 on a HP
DL320 G3 server.
The server had a SCSI controller with one blank (brand new) SCSI disk on
it (not CCISS controller).
Choosing "autopartition" caused the installer to crap out with the error
message "program anaconda is using a deprecated SCSI ioctl", and some
other good stuff. The installer couldn't get the kernel to re-read the
partition table after partitioning.
I have a few screen shots that I made, I was also going to try to
reproduce the problem in VMware, but I wanted to check with the list
first. Is this a known problem? If not, where do I send the more
detailed info and debug data?
Cheers :)
- --
+47 900 61 494
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGFnIVyHoz+xzINgsRArwSAJ9mApBDU1+BeirkaNWtlouamy3XmwCaA6ks
mpnOS0PQ+hMW8QL1C9kYYCA=
=WR9Y
-----END PGP SIGNATURE-----
------------------------------
Message: 2
Date: Fri, 06 Apr 2007 22:44:03 -0400
Subject: Re: Problems with 3.0.5 installer
Content-Type: text/plain; charset=ISO-8859-1

I think Compaq/HP intentionally made the DLxxx series considerably
un-Linux friendly. I always have a Hellish time installing any distro.
There are some tricks, mostly involving SCSI driver module
experimentation. Fedora seems to handle it well. I have luck configuring
the drive(s) with Fedora and then installing another. I haven't tried
3.0.5 on my DL360 though.
Randy
------------------------------
Message: 3
Date: Sat, 07 Apr 2007 12:00:30 +0200
Subject: Re: Problems with 3.0.5 installer
Content-Type: text/plain; charset=ISO-8859-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Post by Morten Johansen
I think Compaq/HP intentionally made the DLxxx series considerably
un-Linux friendly. I always have a Hellish time installing any distro.

Not agreeing with you here. We are running 10 different HP servers and
all install linux just fine. TSL 3.0 and 2.2 work just fine on that same
box.
This particular error seems to be relatively simple. The partitioner
can't get the kernel to re-read the partition table. After I restarted
the install process, the partitions from the last run were all there,
and the install went just fine.
- --
+47 900 61 494
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGF2u+yHoz+xzINgsRAhiIAKDQU1usNrdWCixmKhs31CC8Ae6+aACbBrpe
oVTTL4iphiySHYxAp+1Mwvs=
=aBJx
-----END PGP SIGNATURE-----
------------------------------
_______________________________________________
tsl-discuss mailing list
http://lists.trustix.org/mailman/listinfo/tsl-discuss
End of tsl-discuss Digest, Vol 44, Issue 6
******************************************

Morten Nilsen

2007-04-10 10:05:11 UTC

Permalink

Post by Morten Johansen
other good stuff. The installer couldn't get the kernel to re-read the
partition table after partitioning.

I have reported this issue in the past.. It happens to me just about
every single time I install TSL 3.0.5

I think it is caused by the "checking for prior installations of tsl"
step leaving something open..

Nived Gopalan

2007-04-10 19:25:36 UTC

Permalink

I already did, back in November 2006;
https://bugs.trustix.org/show_bug.cgi?id=2032
It has been marked as fixed, but clearly is still an issue.. I'm
reopening it.

As far as I can see, the bug is listed as a Viper bug. Isn't Anaconda
the installer in 3.0.5?

Yes, it is. Are you facing the same issue as the one in Bug #2032?

-Nived

Morten Johansen

2007-04-10 19:30:32 UTC

Permalink

Post by Nived Gopalan

I already did, back in November 2006;
https://bugs.trustix.org/show_bug.cgi?id=2032
It has been marked as fixed, but clearly is still an issue.. I'm
reopening it.

As far as I can see, the bug is listed as a Viper bug. Isn't Anaconda
the installer in 3.0.5?

Yes, it is. Are you facing the same issue as the one in Bug #2032?

I'm not entirely sure.

I experienced this problem while installing on a entirely new,
uninitialized harddisk on the HP DL320 G3 using the aic7xxx SCSI
driver (no RAID on this server).
If I recall correctly, I installed using "autopartition", and didn't
change anything on the suggested partitioning scheme.
The debug on vt 3 or 4 said something about an deprecated ioctl (got
screenshots), but no debug floppy.

A couple of quick attempts in VMware during easter could not
reproduce the problem.

Sound like the same problem?
To me, reading the #2032 report, it sounds like a (slightly)
different one.

--
Morten Johansen
***@monet.no

Morten Nilsen

2007-04-10 13:31:47 UTC

Permalink

https://bugs.trustix.org/show_bug.cgi?id=2032

As far as I can see, the bug is listed as a Viper bug. Isn't Anaconda
the installer in 3.0.5?

It's listed as an "installer" bug.
The default asignee for installer bugs just happened to be "Viper Dev"
at the time of filing.

--
Cheers,
Morten
:wq

Nived Gopalan

2007-04-10 18:47:27 UTC

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Guys, I ran into a minor problem while installing TSL 3.0.5 on a HP
DL320 G3 server.
The server had a SCSI controller with one blank (brand new) SCSI disk on
it (not CCISS controller).
Choosing "autopartition" caused the installer to crap out with the error
message "program anaconda is using a deprecated SCSI ioctl", and some
other good stuff. The installer couldn't get the kernel to re-read the
partition table after partitioning.
I have a few screen shots that I made, I was also going to try to
reproduce the problem in VMware, but I wanted to check with the list
first. Is this a known problem? If not, where do I send the more
detailed info and debug data?

Hi Morten,

Could you file a detailed report at https://bugs.trustix.org .

Thank you.

Regards,
Nived

Morten Nilsen

2007-04-10 13:17:01 UTC

Permalink

Post by Nived Gopalan

Post by Morten Johansen
other good stuff. The installer couldn't get the kernel to re-read the
partition table after partitioning.

Hi Morten,
Could you file a detailed report at https://bugs.trustix.org .
Thank you.

I already did, back in November 2006;
https://bugs.trustix.org/show_bug.cgi?id=2032

It has been marked as fixed, but clearly is still an issue.. I'm
reopening it.

--
Cheers,
Morten
:wq

Morten Johansen

2007-04-10 13:26:04 UTC

Permalink

I already did, back in November 2006;
https://bugs.trustix.org/show_bug.cgi?id=2032
It has been marked as fixed, but clearly is still an issue.. I'm
reopening it.

As far as I can see, the bug is listed as a Viper bug. Isn't Anaconda
the installer in 3.0.5?

--
Morten Johansen
***@monet.no