Debian jessie image 1.0 released for Bubba|2 / B3

Discuss development on Bubba
tdebruin
Posts: 2
Joined: 05 May 2016, 08:53

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by tdebruin » 05 May 2016, 16:01

Thx for swift reply.

I'm afraid that recompiling Gentoo patches into deb packages is quite a bit above my level, sorry. The Bubba overlay had it all nicely wrapped together indeed, but as said I will leave Jessie-izing that to smarter people that myself. I guess I'll have to just install whatever it is I want to have on that box. Samba should not be too difficult for a start, there are lots of how-to's out there obviously.

Any advise from experience on what a good combination is for minimal services, like Apache + rtorrent + samba + ftp, or rather nginx + owncloud + some other torrent package? I'd like to use that box as a shared data container for a collective housing project (15 people or so), so I need to install services that have not-too-difficult GUI user interface.

Thx!

lognok
Posts: 23
Joined: 30 Nov 2011, 11:23

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by lognok » 10 May 2016, 18:01

Hi again
Here are my latest attempts at getting Jessie running on my b3.

What works and gives b3 an IP (so I can ssh into it):
Gentoo live 1.8.0
Arch live 1.2.0
Full install of b3-install-2.2.zip
Full install of b3-install-2.4.1.1.zip

What doesn't give b3 an IP:
b3-install-1.0.zip in rescue mode
b3-install-2.2.zip in rescue mode
b3-install-2.2.1.zip in rescue mode
b3-install-2.3.zip in rescue mode
b3-install-2.3.1.zip in rescue mode
b3-install-2.4.1.1.zip in rescue mode

When installing the b3-jessie-install-1.0.zip, it installs fine (according to the install.log), but wont give b3 an IP!?
I used Arch-live-usb to access the /etc/network/interfaces of the jessie install, and changed it from this:

allow-hotplug eth0
iface eth0 inet dhcp

allow-hotplug eth1
iface eth1 inet dhcp

.......... into the exact same interfaces file as the 2.4.1.1 install:

auto lo
iface lo inet loopback

iface eth0 inet dhcp

iface eth1 inet dhcp

........... but it didn't work. Jessie still won't give b3 an IP (poor b3 :-P)


I haven't fiddled with static IP (now or ever) and the full installs and the live-usb's work with no help from me, so I'm pretty sure that there's a dhcp server at the other end of the ethernet wallplug (the server is in a locked rack in the basement of our apartment complex).

I'm starting to think that it's a hardware issue. Maybe it's related to my broken SATA port?, I remember reading about a batch of bad mainboards that had broken SATA ports. Maybe something else was broken too?

lognok

Gordon
Posts: 1360
Joined: 10 Aug 2011, 03:18

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by Gordon » 11 May 2016, 07:03

If there is something wrong with your SATA port, there is a chance that the `mount all` command fails. This will cause Debian systems to halt the boot process. You may try to add 'nofail' flag in /etc/fstab to partitions that are not really required to start the system. I'm afraid the only other way is to get the serial console running so you can see what happens at boot time (and respond to interactive questions).

sakaki
Posts: 172
Joined: 15 Aug 2014, 11:20

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by sakaki » 11 May 2016, 07:50

lognok wrote:Hi again
Here are my latest attempts at getting Jessie running on my b3.

What works and gives b3 an IP (so I can ssh into it):
Gentoo live 1.8.0
Arch live 1.2.0
...
I'm starting to think that it's a hardware issue. Maybe it's related to my broken SATA port?
Hi lognok,

As you've got the Arch live usb working, there are two things you could try:
  • install the Jessie system to your internal hdd as before, then boot the Arch live usb and see if you can mount the Jessie hdd system partition manually (using the mount command; if you get errors doing this, almost certainly the Debian boot is failing, as Gordon has just suggested). You'd want to try something like the following:

    Code: Select all

    [root@archb3 ~]# mkdir /tmp/sda1
    [root@archb3 ~]# mount -v /dev/sda1 /tmp/sda1
    
  • Alternatively, if there is nothing on your hdd you want to keep, you could try (temporarily) installing Arch onto your hdd using the provided script on the Arch live usb (instructions here; it only takes about 5 mins) and then seeing if you can reboot off hdd, and login.
These steps may help to narrow down any issue caused by your hdd or SATA port.
Best, sakaki

pai
Posts: 10
Joined: 19 Sep 2015, 14:12

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by pai » 13 May 2016, 10:48

Tweety wrote: I have now a working B3 with Debian Jessie running Webmin and Transmission/DLNA/Samba/FTP servers like I wanted it too
Hey, how can I get ftp access to the b3? Do i firstly need to install proftpd and create a user?

lognok
Posts: 23
Joined: 30 Nov 2011, 11:23

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by lognok » 14 May 2016, 04:15

Hi Gordon and sakaki

Thank you for your inputs.

I'm very sorry for making an error in my last post. I wrote SATA when I should have written E-SATA. Sorry!

The problem is this:
The Jessie installs fine on the HDD. However it won't setup the WAN and LAN correctly, so I don't have an IP-address to ssh into...
I can use Arch to mount the partition and access the files on it. I tried to change the file interfaces, but still no luck.

Additional information:
When I use the rescue-modes of the b3 install/rescue zip-packages, they will also not setup the WAN and LAN with an IP-address.

When I use the install-modes of the b3 install/rescue zip-packages, they install fine AND setup the WAN and LAN with an IP-address.


Afterthought:
My understanging is that the jessie-b3-install is based on the original b3-install/rescue packages, but whatever the original b3-install/rescue packages did to setup the WAN and LAN, did not make it fully into the jessie-b3-install package.


Bottom line:
Jessie install, but no IP :-(

sakaki
Posts: 172
Joined: 15 Aug 2014, 11:20

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by sakaki » 14 May 2016, 07:54

Hi lognok,

in that case, if you use the Arch live USB to mount /dev/sda1 (containing the failing Jessie system partition), you should be then be able to query the contents of the (Jessie) systemd journal, using "journalctl -D <path to mounted journal dir>"; and from this determine if a boot service is failing etc. thereby causing your networking issue.

For example, assuming the Jessie image uses /var/log/journal as its log path, you could use something like:

Code: Select all

[root@archb3 ~]# mkdir /tmp/sda1
[root@archb3 ~]# mount -v /dev/sda1 /tmp/sda1
[root@archb3 ~]# journalctl -D /tmp/sda1/var/log/journal
Of course, you can use the normal unit name filters etc. with journalctl.

Best, sakaki

victorn
Posts: 2
Joined: 16 May 2016, 11:41

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by victorn » 16 May 2016, 12:05

I'm confused, I can't make the USB key to boot.

It works perfectly well if I use the old rescue image, I can boot on it and all.
But if I use this jessie image I simply get a red light quickly after the green one.

And what is strange is that there is no install.log file anywhere on the key!

By the way, notice that the guide available on the wiki (the one titled Rescue_System) is erroneous concerning the formatting of the key: it is /dev/sdc1 that mus be passed as an argument to mkfs.vfat and not /dev/sdc).

Any idea to debug that? Thanks :)

MouettE
Site admin
Posts: 267
Joined: 06 Oct 2011, 19:45

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by MouettE » 16 May 2016, 14:55

victorn wrote:But if I use this jessie image I simply get a red light quickly after the green one.

And what is strange is that there is no install.log file anywhere on the key!
There are a few steps that can fail during the early jessie image bootup and result in a red led :
  • Initramfs was unable to mount to usb key
  • Initramfs was unable to find the rootfs.cpio.xz in the install folder on the key
  • Initramfs was unable to extract the rootfs.cpio.zx from the key
These are very early so there is zero logging (except the console of course). Except for harware-related (motherboard, usb key) issues, causes are usually simple enough : bad key formatting, bad files layout, ...

When the installer starts, it turns the LED to cyan. Logging goes first into /root/install-early.log in the ram filesystem of the system. Then the installer tries to read the ini file. If it's missing, it will exit leaving a red led and dhcp on both network interfaces. You should be able to connect using telnet/ssh on the b3 and read the /root/install-early.log . Note that the LED will also blink the relevant part of the IP attributed to the b3 if applicable.

Once the ini file is read, the network is configured, the logging finally goes on the usb key (install/install.log) and the install part is run.

I hope this will help...

MouettE
Site admin
Posts: 267
Joined: 06 Oct 2011, 19:45

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by MouettE » 16 May 2016, 15:25

While I'm on this topic, it may not be clear enough in the presentation (I will amend it afterwards) but the network configuration derived from the install.in file is only used in the installer and will not be copied on the installed system.

The resulting installed system will always use dhcp on both interfaces because it's hard coded into the image. If you don't have DHCP on your network the simplest way would be to change network parameters and disable reboot in install.ini; run the installer and wait for the led to turn green (install done and rescue system running); connect to the b3 using telnet or ssh, mount the freshly install system partition (/dev/sdb1 in most cases) and edit its /etc/network/interfaces file before rebooting manually.

victorn
Posts: 2
Joined: 16 May 2016, 11:41

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by victorn » 17 May 2016, 13:19

I finally worked! I had to change the USB key, for a reason I ignore the faulty one worked with the old resuce/installer image, but not with the new one :)

Thanks, now I'm going to play :)

Tweety
Posts: 7
Joined: 02 Jul 2013, 07:28

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by Tweety » 25 May 2016, 14:21

tdebruin wrote:Thx for swift reply.

I'm afraid that recompiling Gentoo patches into deb packages is quite a bit above my level, sorry. The Bubba overlay had it all nicely wrapped together indeed, but as said I will leave Jessie-izing that to smarter people that myself. I guess I'll have to just install whatever it is I want to have on that box. Samba should not be too difficult for a start, there are lots of how-to's out there obviously.

Any advise from experience on what a good combination is for minimal services, like Apache + rtorrent + samba + ftp, or rather nginx + owncloud + some other torrent package? I'd like to use that box as a shared data container for a collective housing project (15 people or so), so I need to install services that have not-too-difficult GUI user interface.

Thx!
While you won't get the polished look and complete package feel like the original GUI, Webmin gets you quite close to that, with a whole lot of flexibility and a fair bit of help installing whatever services you need... Give it a whirl, it's not too complicated to install...

Tweety
Posts: 7
Joined: 02 Jul 2013, 07:28

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by Tweety » 25 May 2016, 14:23

pai wrote:
Tweety wrote: I have now a working B3 with Debian Jessie running Webmin and Transmission/DLNA/Samba/FTP servers like I wanted it too
Hey, how can I get ftp access to the b3? Do i firstly need to install proftpd and create a user?
Yep, or whatever ftp service you prefer...

lognok
Posts: 23
Joined: 30 Nov 2011, 11:23

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by lognok » 28 May 2016, 16:17

Hi sakaki

Thanks for introducing me to journalctl. I didn't get to use the unit name filters as I didn't know what to look for (and what not to look for...).

Instead I just took my time and scanned through the entire log, looking for something related to ip-stuff.

I believe I found something interesting here (I have the whole log if anyone is interested in a look):
...
May 24 20:08:20 b3 systemd[1]: Startup finished in 2.339s (kernel) + 7.450s (userspace) = 9.790s.
May 24 20:08:20 b3 kernel: mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
May 24 20:08:20 b3 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
May 24 20:08:25 b3 dhclient[208]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
May 24 20:08:25 b3 ifup[202]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
May 24 20:08:26 b3 dhclient[213]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 24 20:08:26 b3 ifup[206]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
May 24 20:08:27 b3 dhclient[213]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 24 20:08:27 b3 dhclient[213]: DHCPOFFER from 89.23.240.3
May 24 20:08:27 b3 ifup[206]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 24 20:08:27 b3 ifup[206]: DHCPOFFER from 89.23.240.3
May 24 20:08:27 b3 dhclient[213]: DHCPACK from 89.23.240.3
May 24 20:08:27 b3 ifup[206]: DHCPACK from 89.23.240.3
May 24 20:08:27 b3 dhclient[213]: bound to 89.23.240.76 -- renewal in 1196 seconds.
May 24 20:08:27 b3 ifup[206]: bound to 89.23.240.76 -- renewal in 1196 seconds.
May 24 20:08:27 b3 systemd[1]: Reloading OpenBSD Secure Shell server.
May 24 20:08:27 b3 sshd[217]: Received SIGHUP; restarting.
May 24 20:08:27 b3 systemd[1]: Reloaded OpenBSD Secure Shell server.
May 24 20:08:28 b3 sshd[217]: Server listening on 0.0.0.0 port 22.
May 24 20:08:28 b3 sshd[217]: Server listening on :: port 22.
May 24 20:08:32 b3 dhclient[208]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
May 24 20:08:32 b3 ifup[202]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
May 24 20:08:47 b3 dhclient[208]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
May 24 20:08:47 b3 ifup[202]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 17
May 24 20:09:03 b3 buttond[218]: Start shutdown timer
May 24 20:09:03 b3 kernel: evbug: Event. Dev: input0, Type: 1, Code: 116, Value: 1
May 24 20:09:03 b3 kernel: evbug: Event. Dev: input0, Type: 0, Code: 0, Value: 0
May 24 20:09:04 b3 dhclient[208]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
May 24 20:09:04 b3 ifup[202]: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
May 24 20:09:05 b3 buttond[218]: Shuting down system

It looks like the b3 gets the ip from the dhcp-server on the WAN-port, but then it also looks for ip on the LAN-port (I did not have my laptop connected during this startup).
I'll connect my laptop and reboot the b3. Then I'll have a look at the log again, to see what has changed...

MouettE has specified multiple times that there are no dhcp-server on this Jessie-b3, but does that mean that I have to setup a dhp-server on my laptop, in order to give the b3 an ip-address, that I can ssh into?


lognok

sakaki
Posts: 172
Joined: 15 Aug 2014, 11:20

Re: Debian jessie image 1.0 released for Bubba|2 / B3

Post by sakaki » 29 May 2016, 17:03

lognok wrote:MouettE has specified multiple times that there are no dhcp-server on this Jessie-b3, but does that mean that I have to setup a dhp-server on my laptop, in order to give the b3 an ip-address, that I can ssh into?
Hi lognok, yes, based on what MouettE has said and your journald output, you are running a DHCP client on both eth0 (wan port) and eth1 (lan port).

To get a login on eth1, you could run a DHCP server on your laptop to allow connection, but it's probably easiest just to set up a static IP address on both eth1 and your laptop. To do this, boot into your arch live USB and mount the Debian system partition again, as you did before when interrogating the journal:

Code: Select all

[root@archb3 ~]# mkdir /tmp/sda1
[root@archb3 ~]# mount -v /dev/sda1 /tmp/sda1
Then, edit your /etc/network/interfaces file on the system partition:

Code: Select all

[root@archb3 ~]# nano -w /tmp/sda1/etc/network/interfaces
Change the eth1 stanza in this file, for example to the following:

Code: Select all

allow-hotplug eth1
iface eth1 inet static
    address 192.168.10.1
    netmask 255.255.255.0
    broadcast 192.168.10.255
leave the rest of the file as is. Reboot your b3 back into Debian, and plug in your laptop via an Ethernet cable into eth1. Set your laptop's ethernet interface (how to do this will depend on what OS you are running), to e.g.

Code: Select all

address 192.168.10.2
netmask 255.255.255.0
broadcast 192.168.10.255
if you are forced to specify a gateway, use 192.168.10.1.
Now, on your pc, try running:

Code: Select all

ssh excito@192.168.10.1
hth, sakaki

Post Reply