New installation does not work

[BadTicket]

Thanks for helping! Now I try it with root:excito and even root.excito and admin and all with upper cases too, and so on. Nothing, I always get the message "Permission denied, please try again." after some inputs comes "Permission denied (publickey,password). "

[BadTicket]

So, my son helps me and we found that we have to connect the HD by using "ssh 10.0.1.33 -l root". Then I can connect with the password "excito". So, this is one part, but what now. I don't understand what Johannes mean with that:

kill the install process (from memory: processes installer.sh and mkfs.ext3 if that already started) and then run the installer manually. You will then see log output in the terminal, and perhpas figure out what hte problem is.

Can anybody write what I really have to input in the console? Because I never work in a console or something like that and don't understand anything of linux

[Gordon]

Sorry about that. Yes, that was what I meant with that shorthand writing: user `root` with password `excito`.

So okay. Once you got in you can do `ps aux` to list the current active processes and look for something that resembles what Johannes wrote. Then use `kill -9 <process ID>` to stop that process.

[BadTicket]

OK, thanks for that. It's very frustrating, because the next problem is here. Here what I do:

# ps aux

and whats coming:

PID USER COMMAND
1 root init
2 root [kthreadd]
3 root [ksoftirqd/0]
4 root [events/0]
5 root [khelper]
8 root [async/mgr]
9 root [pm]
104 root [sync_supers]
106 root [bdi-default]
108 root [kblockd/0]
114 root [ata_aux]
115 root [ata_sff/0]
123 root [khubd]
130 root [kslowd000]
131 root [kslowd001]
153 root [kswapd0]
154 root [aio/0]
155 root [crypto/0]
258 root [scsi_eh_0]
261 root [scsi_eh_1]
272 root [orion_spi]
277 root [mtdblock0]
282 root [mtdblock1]
287 root [mtdblock2]
326 root [kstriped]
363 root [scsi_eh_2]
364 root [usb-storage]
387 root /sbin/udevd -d
423 root [flush-1:0]
428 root udhcpc -R -n -p /var/run/udhcpc.eth0.pid -i eth0
442 root /usr/sbin/dropbear
444 root /bin/sh /bin/bubbainstall.sh
447 root /sbin/getty -L ttyS0 115200 vt100
448 root /sbin/syslogd -n -m 0
449 root /sbin/klogd -n
498 root [flush-8:0]
499 root /usr/sbin/dropbear
505 root [kjournald]
508 root tar zxf /mnt/usb/install/payload/bubbaroot-111111-1456.tar.gz
509 root tar zxf /mnt/usb/install/payload/bubbaroot-111111-1456.tar.gz
510 root -sh
514 root ps aux

then I do:

# kill -9 444

and then

# /bin/sh /bin/bubbainstall.sh

and now, the avalanche started:

File descriptor 5 (pipe:[947]) leaked on lvdisplay invocation. Parent PID 515: /bin/sh
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
Waiting for usb device to show up
Mount usb
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy

and so on, and so on....

How do I have to start the right installer?

[BadTicket]

OK, I've got a strange idea, when he is looking for the USB, why not remove and insert the USB stick. Here what happens:

Code: Select all

Mount usb
Reading external config
Fixing umask
Setting date/time
Connecting to www.excito.com (194.236.32.217:80)
Connecting to www.excito.com (194.236.32.217:80)
-                    100% |*********************************************************************|     0  --:--:-- ETA/bin/date: unrecognized option `-->'
BusyBox v1.16.1 (2010-07-08 15:56:33 CEST) multi-call binary.

Usage: date [OPTIONS] [+FMT] [TIME]

Display time (using +FMT), or set time

Options:
	[-s,--set] TIME	Set time to TIME
	-u,--utc	Work in UTC (don't convert to local time)
	-R,--rfc-2822	Output RFC-2822 compliant date string
	-I[SPEC]	Output ISO-8601 compliant date string
			SPEC='date' (default) for date only,
			'hours', 'minutes', or 'seconds' for date and
			time to the indicated precision
	-r,--reference FILE	Display last modification time of FILE
	-d,--date TIME	Display TIME, not 'now'
	-D FMT		Use FMT for -d TIME conversion

Recognized TIME formats:
	hh:mm[:ss]
	[YYYY.]MM.DD-hh:mm[:ss]
	YYYY-MM-DD hh:mm[:ss]
	[[[[[YY]YY]MM]DD]hh]mm[.ss]

-                    100% |*********************************************************************| 50911  --:--:-- ETA
xargs: unmatched single quote
Removing existing lvm
File descriptor 5 (pipe:[46510]) leaked on lvremove invocation. Parent PID 1740: /bin/sh
  Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
  One or more specified logical volume(s) not found.
File descriptor 5 (pipe:[46510]) leaked on vgremove invocation. Parent PID 1740: /bin/sh
  Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
  Cannot change VG bubba while PVs are missing!
File descriptor 5 (pipe:[46510]) leaked on pvremove invocation. Parent PID 1740: /bin/sh
  Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
  Can't pvremove physical volume "/dev/sda2" of volume group "bubba" without -ff
LVM removed
Partition disk
Error: Partition(s) on /dev/sda are being used.
Error: Unable to satisfy all constraints on the partition.
Error: You requested a partition from 10.7GB to 1999GB.
The closest location we can manage is 10.7GB to 10.7GB.
Error: You requested a partition from 1999GB to 2000GB.
The closest location we can manage is 2000GB to 2000GB.
Create volume
File descriptor 5 (pipe:[46510]) leaked on pvcreate invocation. Parent PID 1740: /bin/sh
  Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
  Can't initialize physical volume "/dev/sda2" of volume group "bubba" without -ff
File descriptor 5 (pipe:[46510]) leaked on vgcreate invocation. Parent PID 1740: /bin/sh
  Command failed with status code 5.
File descriptor 5 (pipe:[46510]) leaked on lvcreate invocation. Parent PID 1740: /bin/sh
  Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
  Cannot change VG bubba while PVs are missing!
Format system disk
/dev/sda1 is mounted; will not make a filesystem here!
tune2fs 1.41.11 (14-Mar-2010)
Setting maximal mount count to -1
Setting interval between checks to 0 seconds
Formatting lvm data partition
Could not stat /dev/mapper/bubba-storage --- No such file or directory

The device apparently does not exist; did you specify it correctly?
tune2fs 1.41.11 (14-Mar-2010)
tune2fs: No such file or directory while trying to open /dev/mapper/bubba-storage
Couldn't find valid filesystem superblock.
Create swapspace
Setting up swapspace version 1, size = 1073737728 bytes
Install root filesystem
mount: mounting /dev/sda1 on /mnt/disk failed: Device or resource busy
mkdir: can't create directory '/mnt/disk/home': File exists
mount: mounting /dev/mapper/bubba-storage on /mnt/disk/home failed: No such file or directory
Creating missing devicenodes
Reboot into new system
# Connection to 10.0.1.33 closed by remote host.
Connection to 10.0.1.33 closed.

Now I have a purple LED again

[johannes]

Good work, and interesting result! I am not the best of interpreting this, but my _guess_ from reading this is that the installer for some reason does not manage to remove your old LVM (which is kind of special since you had it LVM:ed over two disks before) and therefor fails to do a fresh install.

I would try to remove the LVM manually and then try to restart bubbainstall.sh again. Unfortunately I can't help you on how to do that, but try:

lvremove
vgremove
pvremove

in one way or another (this is what the installer tries, but fails). Sorry that I cannot be more specific.

[BadTicket]

OK, I try the tree things, here what I get (with --help, too):

# lvremove
File descriptor 5 (pipe:[770]) leaked on lvremove invocation. Parent PID 500: -sh
Please enter one or more logical volume paths
Run `lvremove --help' for more information.
# lvremove --help
File descriptor 5 (pipe:[770]) leaked on lvremove invocation. Parent PID 500: -sh
lvremove: Remove logical volume(s) from the system

lvremove
[-A|--autobackup y|n]
[-d|--debug]
[-f|--force]
[-h|--help]
[-t|--test]
[-v|--verbose]
[--version]
LogicalVolume[Path] [LogicalVolume[Path]...]

# vgremove
File descriptor 5 (pipe:[770]) leaked on vgremove invocation. Parent PID 500: -sh
Please enter one or more volume group paths
Run `vgremove --help' for more information.
# vgremove --help
File descriptor 5 (pipe:[770]) leaked on vgremove invocation. Parent PID 500: -sh
vgremove: Remove volume group(s)

vgremove
[-d|--debug]
[-f|--force]
[-h|--help]
[-t|--test]
[-v|--verbose]
[--version]
VolumeGroupName [VolumeGroupName...]

# pvremove
File descriptor 5 (pipe:[770]) leaked on pvremove invocation. Parent PID 500: -sh
Please enter a physical volume path
Run `pvremove --help' for more information.
# pvremove --help
File descriptor 5 (pipe:[770]) leaked on pvremove invocation. Parent PID 500: -sh
pvremove: Remove LVM label(s) from physical volume(s)

pvremove
[-d|--debug]
[-f[f]|--force [--force]]
[-h|-?|--help]
[-t|--test]
[-v|--verbose]
[-y|--yes]
[--version]
PhysicalVolume [PhysicalVolume...]

Seems like hieroglyphics to me

[Gordon]

Try run `pvs`. It should return something like

Code: Select all

  PV /dev/sda2   VG bubba   lvm2 [1.81 TiB / 0    free]
  Total: 1 [1.81 TiB] / in use: 1 [1.81 TiB] / in no VG: 0 [0   ]

Next run `lvdisplay /dev/bubba` (use the VG you got from `pvs`). It should return a load of info and if all is well one line should read

Code: Select all

  LV UUID                533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1

(which is the UUID you posted yesterday). Is that correct?

Next run `lvs -a -o +devices`. Normal return will look like this

Code: Select all

  LV      VG    Attr   LSize Origin Snap%  Move Log Copy%  Convert Devices     
  storage bubba -wi-ao 1.81t                                       /dev/sda2(0)

Do you see more than one device listed? If so, then remove the missing copy by running `lvconvert -m 0 bubba/storage <failing device>` (which will probably be /dev/sdb1).

Verify be rerunning that last command and rerun the installer.

[BadTicket]

When I run pvs, I get this:

File descriptor 5 (pipe:[10478]) leaked on pvs invocation. Parent PID 510: -sh
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
PV VG Fmt Attr PSize PFree
/dev/sda2 bubba lvm2 a- 1.81T 1.81T
unknown device bubba lvm2 a- 3.64T 3.64T

Good or bad? And what do you mean with VG?
Anyway, I use then "lvdisplay /dev/bubba" and get this:

File descriptor 5 (pipe:[10478]) leaked on lvdisplay invocation. Parent PID 510: -sh
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.

And when I try "lvs -a -o +devices" I get the same like above...

Stil a chance to find a solution? Sounds like a "chess game over telephone"

[Gordon]

Bad...

It is clear that you have a broken LVM because you have a disk missing. Documentation states that this command should fix it and reduce the VG (which stands for Volume Group) to the one disk that is inside your B3:

Code: Select all

vgreduce --removemissing --verbose 

Retry the previous given commands if that completes successfully.

[BadTicket]

OK, I used "vgreduce --removemissing --verbose" but get this:

File descriptor 5 (pipe:[856]) leaked on vgreduce invocation. Parent PID 500: -sh
Please give volume group name
Run `vgreduce --help' for more information.

But what I don't understand is: Why is it not possible to format the complete disk and install all from the beginning? I mean, every HD is produced with nothing on it and can be prepared for an OS.

[Gordon]

Sorry, my bad. Command was incomplete. It needs to be:

Code: Select all

vgreduce --removemissing --verbose bubba

With `bubba` being the volume group name.

But yes, you are right. The problem here appears to be that the disk is in fact not repartitioned like you would expect. Which is why the volume group information is kept and what causes the issue at hand.

You can go different ways from here:

• If you can fix the volume group to use the one disk inside the B3, chances are that you can boot it normally after that and you will not need a reinstall at all.
• If you do get the volume group repaired but still want to reinstall, you can edit the ini file for the installer to install system only and keep your data.
• Use gdisk to delete every partition on the disk, in which case the installer should recreate them.

[BadTicket]

Hi Gordon

Cool that you help me so much If you're sometimes close to the Lake Constance in switzerland, don't miss me to taste some of my own beer

So, I try "vgreduce --removemissing --verbose bubba" and get

File descriptor 5 (pipe:[10349]) leaked on vgreduce invocation. Parent PID 511: -sh
Finding volume group "bubba"
Wiping cache of LVM-capable devices
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
There are 1 physical volumes missing.
Trying to open VG bubba for recovery...
Couldn't find device with uuid '533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1'.
There are 1 physical volumes missing.
Creating directory "/etc/lvm/archive"
Archiving volume group "bubba" metadata (seqno 6).
Removing PV with UUID 533XOX-QtxZ-PhBY-sdVV-l6AJ-4BME-CAmQC1 from VG bubba
Creating directory "/etc/lvm/backup"
Creating volume group backup "/etc/lvm/backup/bubba" (seqno 7).
Wrote out consistent volume group bubba

It seems that there is something missing... But the HD sounds always as in use. Would it help if I take the HD out of the B3 and format it on a Mac or a Windows PC? Because I have a HD adapter to use HDs directly over USB. And if so, what would be the best method? "gdisk"? It could be the deepest method, because there are no missing datas on It, I made a copy of them before I take the external USB disk away (there was no method to do this first in a software).

[Gordon]

Heheh,

I used to have some friends over in Neuchatel Switzerland, but I think the closest I ever got to Lake Constance was at a wedding in Landeck Austria. Don't expect to return to any of those places anywhere soon though.

But actually that log looks promising. What do you get from `pvs` now? If it still complains, I think gdisk will be your way out. Could be hazardous in its own though, as many people have called in for support here after buying a diskless B3 from iBood and somehow failed to get install running and I at least did not ever get a clear view of what caused their issues.

[BadTicket]

When I use "pvs" (after kill -9 444) the I get:

File descriptor 5 (pipe:[883]) leaked on pvs invocation. Parent PID 506: -sh
PV VG Fmt Attr PSize PFree
/dev/sda2 bubba lvm2 a- 1.81T 0

Sound good - even if I don't understand that - and so I try to use "/bin/sh /bin/bubbainstall.sh" again. And then comes:

File descriptor 5 (pipe:[883]) leaked on lvdisplay invocation. Parent PID 514: /bin/sh
--- Logical volume ---
LV Name /dev/bubba/storage
VG Name bubba
LV UUID HGc6aY-62KH-T4In-kxc9-sm1t-Rr6p-BktiXI
LV Write Access read/write
LV Status available
# open 1
LV Size 1.81 TB
Current LE 474115
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

Waiting for usb device to show up
Mount usb
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy
mount: mounting /dev/sdb1 on /mnt/usb failed: Device or resource busy

and after removing and inserting the USB stick:

mount: mounting /dev/sdb1 on /mnt/usb failed: No such file or directory
mount: mounting /dev/sdb1 on /mnt/usb failed: No such file or directory
mount: mounting /dev/sdb1 on /mnt/usb failed: No such file or directory

So I check the datas on the stick and found files that should be the right ones...

Shal I try "disk" now? Do I have to do that on a windows pc?