Re: [Reproducible-builds] bpi0 armhf node disk failure
Hi Vagrant, On Mon, May 09, 2016 at 02:32:24PM -0700, Vagrant Cascadian wrote: > Reinstalled with a new SSD (which has considerably more space for > wear-levelling). > Ready for the jenkins setup scripts to be run on it! cool! installation in progress, should be back building packages rather soon! :) thanks! -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] bpi0 armhf node disk failure
On 2016-05-04, Holger Levsen wrote: > On Tue, May 03, 2016 at 11:35:07PM -0700, Vagrant Cascadian wrote: >> I think bpi0's SSD may be in a very bad state. It's one of the oldest >> nodes, so it's no huge surprise to see disk failures there... Yup, disk seemed to be in a pretty bad state. It did boot once again and then promptly failed hard... >> I do have an extra SSD on hand to replace it with, but it will mean a >> clean re-install and then jenkins setup code run, so probably best to >> suspend scheduling jobs related to bpi0 for the near future. Not sure >> exactly when I can get to it. > > ok. Just do it when you have the time and ping me once it's done. Feel > free to keep or not keep the ssh host keys… Reinstalled with a new SSD (which has considerably more space for wear-levelling). Ready for the jenkins setup scripts to be run on it! ssh key fingerprints for the new bpi0: 256 12:47:f1:47:2c:fd:a6:af:84:bf:6b:f2:ab:5f:2a:ab /etc/ssh/ssh_host_ecdsa_key.pub (ECDSA) 2048 0f:5a:72:49:a6:8e:29:8f:2a:40:d6:59:3c:c6:48:18 /etc/ssh/ssh_host_rsa_key.pub (RSA) live well, vagrant signature.asc Description: PGP signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] bpi0 armhf node disk failure
Hi, On Tue, May 03, 2016 at 11:35:07PM -0700, Vagrant Cascadian wrote: > I think bpi0's SSD may be in a very bad state. It's one of the oldest > nodes, so it's no huge surprise to see disk failures there... > > I do have an extra SSD on hand to replace it with, but it will mean a > clean re-install and then jenkins setup code run, so probably best to > suspend scheduling jobs related to bpi0 for the near future. Not sure > exactly when I can get to it. ok. Just do it when you have the time and ping me once it's done. Feel free to keep or not keep the ssh host keys… & thanks! > Does make me think a bit about the idea Steven Chamberlain had mentioned > at one point of using networked disks... but then finding a good network > disk server might be too much effort. unless you spent considerable money a network file server will not be faster and not be more reliable, also if that server goes down, all nodes will go down… IMO we should stay with local discs here. -- cheers, Holger signature.asc Description: Digital signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] bpi0 armhf node disk failure
I think bpi0's SSD may be in a very bad state. It's one of the oldest nodes, so it's no huge surprise to see disk failures there... I do have an extra SSD on hand to replace it with, but it will mean a clean re-install and then jenkins setup code run, so probably best to suspend scheduling jobs related to bpi0 for the near future. Not sure exactly when I can get to it. Does make me think a bit about the idea Steven Chamberlain had mentioned at one point of using networked disks... but then finding a good network disk server might be too much effort. live well, vagrant signature.asc Description: PGP signature ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
