Wheezy install script
Posted by Jeff
|
Re: Wheezy install script February 14, 2013 03:04PM |
Registered: 12 years ago Posts: 8 |
Eran Wrote:
-------------------------------------------------------
> Having run into the same problem with deboostrap:
> > # Starting debootstrap installation
> > E: unrecognized or invalid option
> > --no-check-gpg
> > debootstrap failed.
>
> I decided to do some digging to figure out with
> debootstrap versio was being fetched. Even though
> I didn't have it on my filesystem, the script
> helpfully fetched it - except it fetched the old
> version:
> The script decided to get version
> debootstrap_1.0.26+squeeze1_all.deb
> I've forced URL_DEBOOTSTRAP to be:
> http://cdn.debian.net/debian/pool/main/d/debootstr
> ap/debootstrap_1.0.44_all.deb
>
> And the installer went past this stage.
+1
The regex/top command in that line looked suspicious to me as well
-------------------------------------------------------
> Having run into the same problem with deboostrap:
> > # Starting debootstrap installation
> > E: unrecognized or invalid option
> > --no-check-gpg
> > debootstrap failed.
>
> I decided to do some digging to figure out with
> debootstrap versio was being fetched. Even though
> I didn't have it on my filesystem, the script
> helpfully fetched it - except it fetched the old
> version:
> The script decided to get version
> debootstrap_1.0.26+squeeze1_all.deb
> I've forced URL_DEBOOTSTRAP to be:
> http://cdn.debian.net/debian/pool/main/d/debootstr
> ap/debootstrap_1.0.44_all.deb
>
> And the installer went past this stage.
+1
The regex/top command in that line looked suspicious to me as well
|
Re: Wheezy install script February 18, 2013 02:25PM |
Registered: 11 years ago Posts: 22 |
Brainy142 Wrote:
-------------------------------------------------------
> I tried the new script, but I am still stuck at
> configuring intramfs, it tries to configue it 5
> times then fails, I tried the NSA320 rootfs on my
> goflex home but it doesn't seem to work properly
> and never ask's for an IP address meaning I cannot
> administrate it. Any ideas? I have an image of a
> drive that was able to compile correctly.... but
> it decided not to boot :(.
Are you running the install script directly on a flash drive?
IMO, in general, it's not a good idea to do this kind of installation procedure on flash media. There's a lot of disk churn inherent in the debootstrap process (not least due to update-initramfs), and I wouldn't be surprised if minor flaws in the media are brought to the fore by that kind of workload. (I don't have firsthand experience with this myself, but after looking through the forum threads about off-brand flash media not working correctly, it wasn't hard to put two and two together.)
Instead, I would run the install script on a USB hard drive---letting it churn as much as it wants---and then copy the finished rootfs to the flash drive. Especially if you then run with the root filesystem mounted read-only, that approach should be a lot less prone to trouble.
-------------------------------------------------------
> I tried the new script, but I am still stuck at
> configuring intramfs, it tries to configue it 5
> times then fails, I tried the NSA320 rootfs on my
> goflex home but it doesn't seem to work properly
> and never ask's for an IP address meaning I cannot
> administrate it. Any ideas? I have an image of a
> drive that was able to compile correctly.... but
> it decided not to boot :(.
Are you running the install script directly on a flash drive?
IMO, in general, it's not a good idea to do this kind of installation procedure on flash media. There's a lot of disk churn inherent in the debootstrap process (not least due to update-initramfs), and I wouldn't be surprised if minor flaws in the media are brought to the fore by that kind of workload. (I don't have firsthand experience with this myself, but after looking through the forum threads about off-brand flash media not working correctly, it wasn't hard to put two and two together.)
Instead, I would run the install script on a USB hard drive---letting it churn as much as it wants---and then copy the finished rootfs to the flash drive. Especially if you then run with the root filesystem mounted read-only, that approach should be a lot less prone to trouble.
|
Re: Wheezy install script February 18, 2013 02:34PM |
Registered: 11 years ago Posts: 22 |
okigan Wrote:
-------------------------------------------------------
> The regex/top command in that line looked
> suspicious to me as well
I don't think it's the regex---although that could be tightened up a bit---so much as that the script is relying on the server to sort the various debootstrap packages in newest-to-oldest order via the "?C=M;O=D" (last-Modified date, Descending) directive in the URL. This will work with bog-standard Apache, but cdn.debian.net may resolve to a Web server that doesn't have that feature in its directory indexing.
I didn't look too closely at that bit of code earlier, but here's what I'll propose now for a replacement:
Jeff: If this looks good, let me know and I'll put together a pull request. (Three of the scripts have this construct.)
-------------------------------------------------------
> The regex/top command in that line looked
> suspicious to me as well
I don't think it's the regex---although that could be tightened up a bit---so much as that the script is relying on the server to sort the various debootstrap packages in newest-to-oldest order via the "?C=M;O=D" (last-Modified date, Descending) directive in the URL. This will work with bog-standard Apache, but cdn.debian.net may resolve to a Web server that doesn't have that feature in its directory indexing.
I didn't look too closely at that bit of code earlier, but here's what I'll propose now for a replacement:
DEBOOTSTRAP_VERSION=$(wget -q http://packages.debian.org/sid/all/debootstrap/download -O- | egrep -o '\<debootstrap_[^/"]+_all\.deb\>' | head -n1)This hits the Debian package-information site to get the latest version of debootstrap, rather than a mirror's directory-index page. This should be susceptible to failure only if the site is down (happens sometimes), if the site layout changes (not likely, this is Debian), or if the site lists a new version of the package that has not yet reached the mirrors (rare).
Jeff: If this looks good, let me know and I'll put together a pull request. (Three of the scripts have this construct.)
|
Re: Wheezy install script February 19, 2013 06:37PM |
Registered: 11 years ago Posts: 5 |
I still cant get the script working (I swapped the flash drive for a external hdd) and I still fail at the same point with the same error message that is reported here: http://forum.doozan.com/read.php?2,9256,9256,quote=1
I do not have the ability to boot to a debian OS on the goflex home aside from the rescue system (V2) that I had installed previously. I was able to compile the previous script, however, now it fails as the script is broken, and the one time I was able to get it to work I didn't image the usb drive and managed to break the install on it. The NSA320 rootfs boots, however, I am unable to access it as it wont request an IP address from the network.
At this point I just want the thing to work so I can try to set up the system with a couple idea's I have.
ps. I would try to help figure out why the nsa320 rootfs wont run, but sadly I haven't had any luck with netconsole
Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-3-kirkwood Warning: root device does not exist and subprocess installed post-installation script returned error exit status 1 Processing triggers for flash-kernel ... Unsupported platform. dpkg: error processing flash-kernel (--configure):
I do not have the ability to boot to a debian OS on the goflex home aside from the rescue system (V2) that I had installed previously. I was able to compile the previous script, however, now it fails as the script is broken, and the one time I was able to get it to work I didn't image the usb drive and managed to break the install on it. The NSA320 rootfs boots, however, I am unable to access it as it wont request an IP address from the network.
At this point I just want the thing to work so I can try to set up the system with a couple idea's I have.
ps. I would try to help figure out why the nsa320 rootfs wont run, but sadly I haven't had any luck with netconsole
|
Re: Wheezy install script February 19, 2013 06:44PM |
Admin Registered: 13 years ago Posts: 18,570 |
Brainy142 Wrote:
-------------------------------------------------------
> I still cant get the script working (I swapped the
> flash drive for a external hdd) and I still fail
> at the same point with the same error message that
> is reported here:
> http://forum.doozan.com/read.php?2,9256,9256,quote
> =1
>
>
> I do not have the ability to boot to a debian OS
> on the goflex home aside from the rescue system
> (V2) that I had installed previously. I was able
> to compile the previous script, however, now it
> fails as the script is broken, and the one time I
> was able to get it to work I didn't image the usb
> drive and managed to break the install on it. The
> NSA320 rootfs boots, however, I am unable to
> access it as it wont request an IP address from
> the network.
>
> At this point I just want the thing to work so I
> can try to set up the system with a couple idea's
> I have.
> ps. I would try to help figure out why the nsa320
> rootfs wont run, but sadly I haven't had any luck
> with netconsole
I would suggest to install Debian Squeeze and then upgrade it to Wheezy. It should work.
-------------------------------------------------------
> I still cant get the script working (I swapped the
> flash drive for a external hdd) and I still fail
> at the same point with the same error message that
> is reported here:
> http://forum.doozan.com/read.php?2,9256,9256,quote
> =1
>
>
> Processing triggers for initramfs-tools ... > update-initramfs: Generating > /boot/initrd.img-3.2.0-3-kirkwood > Warning: root device does not exist > > and > > subprocess installed post-installation script > returned error exit status 1 > Processing triggers for flash-kernel ... > Unsupported platform. > dpkg: error processing flash-kernel > (--configure): > >>
> I do not have the ability to boot to a debian OS
> on the goflex home aside from the rescue system
> (V2) that I had installed previously. I was able
> to compile the previous script, however, now it
> fails as the script is broken, and the one time I
> was able to get it to work I didn't image the usb
> drive and managed to break the install on it. The
> NSA320 rootfs boots, however, I am unable to
> access it as it wont request an IP address from
> the network.
>
> At this point I just want the thing to work so I
> can try to set up the system with a couple idea's
> I have.
> ps. I would try to help figure out why the nsa320
> rootfs wont run, but sadly I haven't had any luck
> with netconsole
I would suggest to install Debian Squeeze and then upgrade it to Wheezy. It should work.
|
Re: Wheezy install script February 19, 2013 08:56PM |
Registered: 11 years ago Posts: 5 |
Good news: I finally got netconsole to work and the wheezy script works.... for the install
Bad news:
I cant get wheezy to boot
netconsole for squeeze
Update: magic fairy dust has appeared and now the NSA320 rootfs is working
Edited 2 time(s). Last edit at 02/19/2013 09:28PM by Brainy142.
Bad news:
I cant get wheezy to boot
netconsole for squeeze
** File not found /boot/uImage (I have confirmed that this is true) Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) ** File not found /boot/uInitrd (I can also confirm this) Wrong Image Format for bootm command ERROR: can't get kernel image! stopping USB..
Update: magic fairy dust has appeared and now the NSA320 rootfs is working
Edited 2 time(s). Last edit at 02/19/2013 09:28PM by Brainy142.
|
Douglas Henke
Re: Wheezy install script February 28, 2013 01:59PM |
> unrecognized or invalid option --no-check-gpg
I got this too. Mine was a result of trying to run the install script from a NAND-based rescue system (davygravy's 2.8.2, FWIW) which already had a /usr/bin/debootstrap, just not the right one.
Solution (in my case) was, in my usual fashion, brute force and ignorance:
mount -o remount,rw /
rm -rf /usr/sbin/debootstrap /var/share/debootstrap
mount -o remount,ro /
rm -rf /tmp/debootstrap
umount /tmp/debian
... then run the script again. It's still happily unpacking packages as I type, but I'm cautiously optimistic.
I got this too. Mine was a result of trying to run the install script from a NAND-based rescue system (davygravy's 2.8.2, FWIW) which already had a /usr/bin/debootstrap, just not the right one.
Solution (in my case) was, in my usual fashion, brute force and ignorance:
mount -o remount,rw /
rm -rf /usr/sbin/debootstrap /var/share/debootstrap
mount -o remount,ro /
rm -rf /tmp/debootstrap
umount /tmp/debian
... then run the script again. It's still happily unpacking packages as I type, but I'm cautiously optimistic.
