Re: [Bug 1026450] Re: Pangolin installer problem

[Rich Duzenbury]

Certainly.  Thank you for your assistance.

On 6:11am, Mon, Feb 1, 2016 Pander <1026...@bugs.launchpad.net> wrote:

> I agree. Can it be set to won't fix?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1026450
>
> Title:
>   Pangolin installer problem
>
> Status in debian-installer package in Ubuntu:
>   Incomplete
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I'm attempting to install precise pangolin on an HP BL35P blade using
>   an ubuntu server x86-64 CD.  HP BL35P blades have broadcomm nics that
>   need restricted firmware, which I have placed on a USB key.  The USB
>   key must be inserted prior to booting the installer CD or it doesn't
>   seem readable.  That in itself is no big deal, however, the USB key
>   becomes /dev/sda.  The internal hard disk is assigned to /dev/sdb.
>
>   During installation, the installer lets me choose which drive to
>   install the operating system onto.  It shows a selection for the 1GB
>   USB key, and the 140GB raid array.  I choose the raid array, and the
>   installed files are written there with no difficulty.
>
>   The problem comes when attempting to do the grub installation.  The
>   installer defaults to writing the master boot record to /dev/sda,
>   which in this case, is the USB stick with the restricted firmware on
>   it.  After a couple tries at re-installing I do finally notice the
>   issue, but I don't think a novice would see it at all.  Of course, I
>   have to override the installer so it will write the MBR to /dev/sdb
>   and then the system will boot correctly, and the installer does
>   support that cause of action.
>
>   What I expect to happen: The installer should default to writing grub
>   to the disk that was chosen for the server install.
>
>   What happened: The installer rather blindly chooses /dev/sda by
>   default.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1026450/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026450

Title:
  Pangolin installer problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1026450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1026450] Re: Pangolin installer problem

[Rich Duzenbury]

Thanks for trying to help me.  The installer can certainly _default_ to the
chosen disk particularly if thats the drive where the installer is running
from.  Perhaps warn the user? Or force a choice?

Also this bug report is some years old and seems to now have activity and
I'm not sure why.  I don't know if newer installers have the same issue or
not and I don't have the capability to test them out at this time.

Perhaps it would be best to let this issue die and spend time on more
recent items?

On 3:31pm, Wed, Jan 27, 2016 Phillip Susi  wrote:

> It can't just install to the disk chosen to install Ubuntu to since in a
> dual disk situation, the system still boots from the first disk.  I
> believe the issue of the usb stick being detected as sda instead of the
> first hard disk was fixed some time ago, but precise is ancient and you
> should not be putting into new systems.  Please try with 14.04.
>
>
> ** Changed in: debian-installer (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Changed in: ubiquity (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1026450
>
> Title:
>   Pangolin installer problem
>
> Status in debian-installer package in Ubuntu:
>   Incomplete
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I'm attempting to install precise pangolin on an HP BL35P blade using
>   an ubuntu server x86-64 CD.  HP BL35P blades have broadcomm nics that
>   need restricted firmware, which I have placed on a USB key.  The USB
>   key must be inserted prior to booting the installer CD or it doesn't
>   seem readable.  That in itself is no big deal, however, the USB key
>   becomes /dev/sda.  The internal hard disk is assigned to /dev/sdb.
>
>   During installation, the installer lets me choose which drive to
>   install the operating system onto.  It shows a selection for the 1GB
>   USB key, and the 140GB raid array.  I choose the raid array, and the
>   installed files are written there with no difficulty.
>
>   The problem comes when attempting to do the grub installation.  The
>   installer defaults to writing the master boot record to /dev/sda,
>   which in this case, is the USB stick with the restricted firmware on
>   it.  After a couple tries at re-installing I do finally notice the
>   issue, but I don't think a novice would see it at all.  Of course, I
>   have to override the installer so it will write the MBR to /dev/sdb
>   and then the system will boot correctly, and the installer does
>   support that cause of action.
>
>   What I expect to happen: The installer should default to writing grub
>   to the disk that was chosen for the server install.
>
>   What happened: The installer rather blindly chooses /dev/sda by
>   default.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1026450/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026450

Title:
  Pangolin installer problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1026450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1026450] Re: Pangolin installer problem

[Rich Duzenbury]

** Package changed: ubuntu = debian-installer (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026450

Title:
  Pangolin installer problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1026450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1026450] [NEW] Pangolin installer problem

[Rich Duzenbury]

Public bug reported:

I'm attempting to install precise pangolin on an HP BL35P blade using an
ubuntu server x86-64 CD.  HP BL35P blades have broadcomm nics that need
restricted firmware, which I have placed on a USB key.  The USB key must
be inserted prior to booting the installer CD or it doesn't seem
readable.  That in itself is no big deal, however, the USB key becomes
/dev/sda.  The internal hard disk is assigned to /dev/sdb.

During installation, the installer lets me choose which drive to install
the operating system onto.  It shows a selection for the 1GB USB key,
and the 140GB raid array.  I choose the raid array, and the installed
files are written there with no difficulty.

The problem comes when attempting to do the grub installation.  The
installer defaults to writing the master boot record to /dev/sda, which
in this case, is the USB stick with the restricted firmware on it.
After a couple tries at re-installing I do finally notice the issue, but
I don't think a novice would see it at all.  Of course, I have to
override the installer so it will write the MBR to /dev/sdb and then the
system will boot correctly, and the installer does support that cause of
action.

What I expect to happen: The installer should default to writing grub to
the disk that was chosen for the server install.

What happened: The installer rather blindly chooses /dev/sda by default.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: installer pangolin precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026450

Title:
  Pangolin installer problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1026450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

Cruncher, see comment 11.  I think mlocate is working according to my
test.  I believe that hardy, if it is still using slocate, is still
broken, or was at the time of previous tests.  I don't have a hardy
system to test with anymore, so I cannot say.

-- 
slocate doesn't always locate on remote smbfs share
https://bugs.launchpad.net/bugs/71962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

This is lucid, 10.04.1, I no longer have a hardy system to test with.

updatedb reports version as: updatedb (mlocate) 0.22.2

The /etc/fstab line looks like:
//bintls5/c$ /mnt/bintls5 smbfs defaults,credentials=/etc/.smbpasswd 0 0

find /mnt/bintls5 | wc -l
915201

sudo updatedb -v -U /mnt/bintls5  updatedb.txt
cat updatedb.txt | wc -l
915206

I'd say those numbers are close enough, since the share is active for a
number of users.  I did a few locate commands and they seem to work
fine.   I'd say that Lucid has taken care of this issue.

-- 
slocate doesn't always locate on remote smbfs share
https://bugs.launchpad.net/bugs/71962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: [Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
 Daniel T Chen
 Sent: Thursday, September 18, 2008 6:08 PM
 To: Duzenbury, Rich
 Subject: [Bug 71962] Re: slocate doesn't always locate on remote smbfs
 share

 Is this symptom still reproducible in 8.10 alpha?  (Note that 8.04 and
 8.10 use mlocate instead of slocate.)

 ** Changed in: slocate (Ubuntu)
Status: New = Incomplete

 --
 slocate doesn't always locate on remote smbfs share
 https://bugs.launchpad.net/bugs/71962
 You received this bug notification because you are a direct subscriber
 of the bug.

Hello,

Thank you for writing.

I don't have 8.10 alpha loaded, but 8.04 seems to still be problematic.

I added a large share to my /etc/fstab and mounted it.  Then, I removed
'smbfs' from the PRUNEFS line of /etc/updated.conf.  Said volume has
never been mounted to this machine before.

find /mnt/bintls5 | wc -l returns 895752

Then, I ran updatedb -v | wc -l returns 283384.   I would expect at
least one line of output per file with -v.

Thank you for your interest in this matter.

Regards,
Rich

-- 
slocate doesn't always locate on remote smbfs share
https://bugs.launchpad.net/bugs/71962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

Sorry, no joy.  Per your suggestion, I installed the latest version of
coreutils, 6.6.91, recompiled, and then  re-ran my test program (code
above).

The first time I ran it, it reported some errors, and that there are
363015 files on the volume.  The second time I ran it, it reported
completely different results.  Different errors, and different totals:

/mnt/duz_cdrive/rave_jpeg_test - rave_jpeg_test - 2 - No such file or directory
/mnt/duz_cdrive/Readiris - Readiris - 2 - No such file or directory
/mnt/duz_cdrive/scans - scans - 2 - No such file or directory
/mnt/duz_cdrive/Symtemp - Symtemp - 2 - No such file or directory
/mnt/duz_cdrive/system.sav - system.sav - 2 - No such file or directory
/mnt/duz_cdrive/thin - thin - 2 - No such file or directory
/mnt/duz_cdrive/Virtual Machines - Virtual Machines - 2 - No such file or 
directory
Total: 457211

However, it's the same old volume that changes by a few tens to a few
hundreds of files per day.  All of the listed directories are available
from the command line, for example:

[EMAIL PROTECTED]:/mnt/duz_cdrive/scans$ ls -al
total 510
drwxr-xr-x 1 root root  4096 2007-01-23 10:53 .
drwxr-xr-x 1 root root  4096 2007-12-21 08:53 ..
-rwxr-xr-x 1 root root 58472 2007-01-23 10:43 testcolor2.tif
-rwxr-xr-x 1 root root 58126 2007-01-23 10:38 testcolor.tif
-rwxr-xr-x 1 root root 59568 2007-01-23 10:43 testgray2.tif
-rwxr-xr-x 1 root root 58152 2007-01-23 10:38 testgray.tif
-rwxr-xr-x 1 root root 51992 2007-01-23 10:53 test_modified.tif
-rwxr-xr-x 1 root root 59836 2007-01-23 10:42 testmono2.tif
-rwxr-xr-x 1 root root 58232 2007-01-23 10:37 testmono.tif
-rwxr-xr-x 1 root root 54490 2007-01-23 10:53 test_original.tif
-rwxr-xr-x 1 root root 52250 2007-01-23 10:53 test.tif

Thank you.

Regards,
Rich

-- 
slocate doesn't always locate on remote smbfs share
https://bugs.launchpad.net/bugs/71962
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

FYI, the latest test was completed on a fully updated Ubuntu Gutsy.

-- 
slocate doesn't always locate on remote smbfs share
https://bugs.launchpad.net/bugs/71962
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

I also tested this on edgy, and it has the same problem.   Directories
that appear 'late' in the list are not traversed, while directories that
appear early in the list are.  In my case /usr/bin/updatedb -v -l0 -U
/mnt/cdrive runs and numerous files are indexed, but /mnt/cdrive/Program
Files and others are not traversed.

If I then use /usr/bin/updatedb -v l0 -U /mnt/cdrive/Program Files,
than many of the directories there are traversed, but some of those that
appear late are not.

Apparently, locate is part of package findutils.  The latest test was
run on 4.2.27-3 (edgy).

Thank you.

Regards,
Rich

-- 
slocate doesn't always locate on remote smbfs share
https://launchpad.net/bugs/71962

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] Re: slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

Sorry, I meant to say, slocate v 3.1-1.  *NOT* findutils.

** Changed in: Ubuntu
Sourcepackagename: None = slocate

-- 
slocate doesn't always locate on remote smbfs share
https://launchpad.net/bugs/71962

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71962] slocate doesn't always locate on remote smbfs share

[Rich Duzenbury]

Public bug reported:

Hi,

I have an smb share mounted via my /etc/fstab.  In my case, it is called
/mnt/duz_cdrive, type smbfs, share //mycomputer/c$.  I mounted it with
an administrator capable password to be sure that authority issues were
not a cause.

I built an slocate database over it, and when searching for known files,
they do not  always appear in the locate results.  Investigating
further, I ran the updatedb job with the -v flag, and I noted that it
did not traverse into some directories, even though I could easiy cd
into them, and sucessfully use the ls command.

I downloaded the source code to slocate and was unsure if the fts_*
routines, or perhaps the matching routine.  I built a simple program to
traverse and count all of the files on the share, and found that even
thought there are more than 300K files on the share, only 60K are
iterated over:

fts_count.c
#include stdio.h
#include string.h
#include errno.h
#include stdlib.h
#include unistd.h
#include sys/types.h
#include sys/stat.h
#include fcntl.h
#include ctype.h
#include time.h
#include fts.h


/* Traverse the database */
/* This is basically the code used by slocate.c to find files and load them */
int main(int argc, char **argv)
{
FTS *dir = NULL;
FTSENT *file = NULL;
int ret = 0;
int count = 0;

if (!(dir = fts_open(argv, FTS_PHYSICAL | FTS_NOSTAT, NULL))) {
printf(fts_open: %s\n, strerror(errno));
}

/* Read all entries */
while ((file = fts_read(dir))) {
count++;
if (file-fts_errno != 0) {
printf(%s - %s - %d - %s\n,   file-fts_path, 
file-fts_name, 
file-fts_errno,
strerror(file-fts_errno));
}
}

if(fts_close(dir) == -1) {
printf( fts_close(): Could not close fts: %s\n, 
strerror(errno));
}   


printf(Total: %d\n, count);
return ret;
}

Many files are accessible, but some are not. The test program produces
some errors when it runs:

/mnt/duz_cdrive/Inprise - Inprise - 2 - No such file or directory
/mnt/duz_cdrive/mysql41 - mysql41 - 2 - No such file or directory
/mnt/duz_cdrive/Perl - Perl - 2 - No such file or directory
/mnt/duz_cdrive/Program Files - Program Files - 2 - No such file or directory
/mnt/duz_cdrive/RECYCLER - RECYCLER - 2 - No such file or directory
/mnt/duz_cdrive/ruby - ruby - 2 - No such file or directory

In reality, I can easily cd /mnt/duz_cdrive/ruby, and ls shows that
there are nine files and nine directories.   File operations appear to
work normally, as in cat ChangeLog.txt.

This is on Dapper.  I'm currently installing Edgy to see if it remains
an issue.

This is most likely repeatable via:

make a mount point:
mkdir -p /mnt/cdrive

Add an smb share to your /etc/fstab thusly:
//mycomputer/c$ /mnt/cdrive smbfs 
defaults,username=my_user_name,password=my_password,workgroup=MYWORKGROUP 0 0

reboot the system and log in.  The share should be accessible via the
gnome gui, as well as via the command line.

Then, slocate -v -U /mnt/cdrive and examine the list of directories that
are reported as the program runs.  Likely, you will notice that some
directories are not traversed.  In my case, the C:\Program Files
directory is one of the big missing directories.

I saw the following on google, but I am not clear on if this is the same issue 
or not:
http://www.mail-archive.com/bug-findutils@gnu.org/msg01212.html
 
Should you need further information, contact me at your convenience.

Thank you.

Regards,
Rich

** Affects: Ubuntu
 Importance: Undecided
 Status: Unconfirmed

-- 
slocate doesn't always locate on remote smbfs share
https://launchpad.net/bugs/71962

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs