• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu

samba server problems with eCS 20rc4...

Started by NNYITGuy, 2008.05.05, 19:17:09

Previous topic - Next topic

NNYITGuy

Hi Everyone,

I installed and configured eCS 2.0RC4 and everything worked fine.  I then decided to install Samba server v3.0.28 WPI package.  The installer reported a successful install.  I then rebooted.  The boot process stopped at "Installing OS2LVM.DMD" and never progressed further.

I rebooted several times and the same result.  I even tried to boot to ALT + F1 and F2 to get to a command prompt.  That stopped at the same spot of "Installing OS2LVM.DMD".

I then re-installed again eCS v2.0RC4 successfully, then installed Samba v3.0.28 WPI successfully and rebooted.  The same boot stop as mentioned above.

On the first attempt above I had originally installed and then removed the PEER components as per prescribed in eCS based docs for samba installation.  The second eCS install did not have PEER installed and I confirmed the config.sys entries to make sure that it was clear of the eCS PEER items that needed to be removed prior to Samba install.

Is this an ACPI issue? Is this a boot with JFS issue? Should I be looking to other resources and documentation for eCS v2.0RC4 for assistance?

Thank you,
Todd
Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)

Pete

Hi Todd

You only mention ACPI at the end and it is not clear if you have that installed - also what chipset is involved?

My experience of eCS2.0rc4 is that the supplied ACPI should be binned - read updated - immediately; although it could be the best ACPI to date for other systems...

I have an Asus M2N mainboard using nForce430/MCP61 chipset.

After running the "ACPI Wizard" and *Correcting* the suggested configuration line I still had a non-booting system - Yes, ACPI could well be the cause of your non-booting system.

Updating to ACPI v3.09 (available in the betazone) at least gets me a booting system that - mainly - works.

The config.sys line working for the mainboard with ACPI v3.08 is:-

PSD=ACPI.PSD /SMP /TMR /APIC /CD /!NOD


The only real problem I have noticed is a USB drive attachment problem: it is not possible to attach more than 1 USB drive at a time. Attach a drive, USB drive 1, then any other USB Drive that I attach is totally ignored. To use USB drive 2 it is necessary to eject USB drive 1 and then attach USB drive 2 .

That seems to be an ACPI problem in that it did not happen like that until ACPI was installed.

Hope the above is of some help.

Pete

RobertM

Hey Todd,

I had a similar problem with an ASUS board - every hard boot worked. Soft boots did not. Dunno if it is related. The problem was an issue in the nForce chipset for the drive support - which they thought they had fixed in a BIOS update, and another BIOS update, and another... turns out some of the boards had defective chipsets - and recall or suit (for that problem - dont recall which) attached as well.

Eventually, nothing would properly run on the board (not Windows or OS/2) for that same reason. On reboots, the BIOS would not properly recognize the drive size (with the new BIOS, it would, but still would do something weird).

No idea if it is related (and if it is, it's the reboot stage after installing Samba that is the issue). To test if it is though, with eCS running, install Samba, do the reboot - but when it gets back to the BIOS screen, shut down (power off) the machine and then power it back on and see if it boot successfully.

Robert


|
|
Kirk's 5 Year Mission Continues at:
Star Trek New Voyages
|
|


herwigb

Just for the records: I thought about your problem, but I cannot really imagine a scenario where Samba would stop your boot process.

Not a single component of Samba runs while the system is booting.

Kind regards,
Herwig
Kind regards,
HerwigB.

warpcafe

#4
Hey all,

Quote from: herwigb on 2008.05.06, 11:21:26
Just for the records: I thought about your problem, but I cannot really imagine a scenario where Samba would stop your boot process.

Not a single component of Samba runs while the system is booting.

I thought about it too... and Herwig is correct.
However - there is indeed something about Samba that runs while the system is booting:
Network!
To be more specific: (Multi-)protocol bindings, etc.

I suspect that it is something networking-related... unfortunately, I have not made my fingers dirty so far in matters of Samba. What I can imagine too is something that is required by Samba regarding file systems ("must support long filenames", etc.) but I'm lacking knowledge of its detailed requirements.

Can you mail/attach you protocol.ini file? Maybe this gets us started... what file system(s) are you using? HPFS, JFS, bootable JFS? Perhaps it's just something very simple like a missing "netbios over tcp/ip" or whatever... I cannot tell but I'm pretty sure there is a lot of implications regarding Samba/2 and networking :)

Cheers
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

herwigb

Kind regards,
HerwigB.

warpcafe

Quote from: herwigb on 2008.05.07, 09:06:36
No you are wrong, there is nothing Samba specific in that, you just have to be sure that NetBIOS over TCP/IP is removed.

Ouch!
I didn't know that... now that's quite interesting, I thought Samba = SMB = Netbios/TCPIP... hmm... you live and you learn... :) and perhaps the wording wasn't exact. What I meant to say was that of all the things that "booting" and "Samba" have in common, it can be only networking... thus, I suspect the networking settings to be somehow "wrong".

Thanks for the heads-up and the links, Herwig.

regards,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

NNYITGuy

Sorry Everyone,

I have been so busy.  No time to get back to this until now.  This message has to be short.

eCS 2.0 RC4 clean install to fresh hard disk with JFS boot partition.

Install completes and system is completely usable.  Reboots and cold boot are are perfect.  Install Warpin v1.0.17 as per Samba v3.0.28 WPI package.  Set UNIXROOT=C: as per Samba WPI install package request.  Samba WPI exits and wants a reboot before proceeding.

Reboot is good.  Also cold boot is good too.  Reboot again for good measure.  Everything still is good.

Install Samba WPI package.  Samba WPI requests a reboot.  I reboot.  System always hangs and last message at bottom left of screen is "Installing OS2LVM.DMD".  System never gets any farther.

ALT+F1 then F2 gets me to the same thing, "Installing OS2LVM.DMD".

I start the eCS installer from CD and get to CMD prompt.  Find current config.sys, copy it to *.samba, then copy a pre Samba config.??? to config.sys and exit CMD prompt.  Select reboot from Maintenance Menu.

System reboots to the same "Installing OS2LVM.DMD".

So, my belief is that something has possibly happened to JFS partition during install of Samba WPI or that something in the needed networking config somehow does not either work with JFS boot or something in the base code of eCS v2.0RC4.

My next step is to install to eCS v2.0RC4 to fresh hard disk on a HPFS partition exactly like I have installed to JFS.  That will not happen until this weekend.

Wow, it is so easy to get carried away with this stuff.  I constantly loose track of time... LOL HA HA HA  Good thing I really like what I do for living, or this would be really painful.

Best regards,
Todd
Todd J Simpson (IT Consultant)
Business Automation Technologies
(Professional Products and Services.  Business to Business...)

warpcafe

Quote from: NNYITGuy on 2008.05.08, 20:05:47
Sorry Everyone,
I have been so busy.  No time to get back to this until now.
Oh, no problem... it's your issue, not ours. ;)
In the meanwhile we've been busy with all our very own problems with ECS. :)
Good you're back.

Quote from: NNYITGuy on 2008.05.08, 20:05:47
eCS 2.0 RC4 clean install to fresh hard disk with JFS boot partition.
Just to make sure: The JFS boot partition is indeed having the drive letter C: ...correct?

Quote from: NNYITGuy on 2008.05.08, 20:05:47
Samba WPI exits and wants a reboot before proceeding.
Reboot is good.  Also cold boot is good too.  Reboot again for good measure.  Everything still is good.
Ehh... you mean it asks for 1 reboot and you give it 3 in a row?

Quote from: NNYITGuy on 2008.05.08, 20:05:47
Install Samba WPI package. 
Pardon? I thought you already did that in the step above?
Now, heck... does it require 2 reboots during setup?
Does it require to run the installer again in order to finish?

I don't get the picture I guess... I will have to check the install docs I suppose.

Quote from: NNYITGuy on 2008.05.08, 20:05:47
ALT+F1 then F2 gets me to the same thing, "Installing OS2LVM.DMD".
That's because either config.sys and config.x load the same stuff or (what I rather suspect) it has nothing to do with config.sys. Damn, I will have to install Samba to provide further assistance... isn't there someone here using Samba and can enlighten us with the internals of what is loaded when/where?? ;)

Cheers,
Thomas
"It is not worth an intelligent man's time to be in the majority.
By definition, there are already enough people to do that"
- G.H. Hardy

obiwan

I was dual-booting eCS and Linux successfully on my notebook for about a year and a half, until the day I installed and used Samba on eCS, and on that day, after my next boot, my partition table was corrupted.

Coincidence? I have no idea. Doesn't make much sense to me that running Samba would hurt the partition table. Now I read someone else has LVM trouble after installing Samba. More coincidence. I don't understand it, but it gives me pause.

herwigb

Gents,

as the one who created and currently maintains the Samba WPI I am really amazed to see your messages.

First off all, if you have set UNIXROOT properly prior to starting the WPI there is no need to reboot your machine at all.

- The Samba WPI does not modify your config.sys.
- The Samba WPI does not register new classes.
- The Samba WPI does not modify the systems INI files.

What Samba actually does:

- Create the baselayout as suggested in %UNIXROOT%
- Unpack the Samba files and utilities
- Create a bunch of directories for Samba in %ETC%
- Create initial master.passwd including guest account.
- Create a basic smb.conf which shares all drives (except bootdrive) and printers (although user can choose which drives/printers to share).
- Create a folder populated with some essential Samba objects

To summarize: It copies files, creates files and directories, and some WPS objects.

That's it, not more not less.

Kind regards,
Herwig
Kind regards,
HerwigB.

herwigb

Hi,

one thing comes to my mind:

Do you guys who see these problems have the EVFS filesystem (eComStation Virtual Filesystem for SMB) installed, which comes with eCS 2.0rc4?

Kind regards,
Herwig
Kind regards,
HerwigB.

obiwan

#12
Hi HerwigB,

I didn't use the WPI package. I unzipped the zip package from Paul Smedley's site and just used smbclient to copy files around. I did not reboot for the sake of Samba. I only noticed the problem the next time I tried to reboot to Linux, at which time it could not finish booting because some of my partitions were gone. Linux's fdisk says the partition table is corrupted. I am able to boot to eComStation, but when I run the LVM Manager, it says, too, the partition table is corrupted, but some of the partitions are still visible and working, so far.

I do not have EVFS installed. My notebook has eCS 2.0rc1.