(Solved) NAS310: old usb died, can I use internal HDD only?

Hi,

the usb stick of my NAS310 doesn't boot anymore.

/sbin/init[   25.656033][    T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[   25.665135][    T1] CPU: 0 PID: 1 Comm: init Not tainted 5.5.1-kirkwood-tld-1 #1.0
[   25.672732][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   25.679756][    T1] [<8010f668>] (unwind_backtrace) from [<8010b9f4>] (show_stack+0x10/0x14)
[   25.688238][    T1] [<8010b9f4>] (show_stack) from [<80119e8c>] (panic+0xfc/0x328)
[   25.695851][    T1] [<80119e8c>] (panic) from [<8011bc4c>] (do_exit+0x1b4/0xa24)
[   25.703287][    T1] [<8011bc4c>] (do_exit) from [<8011d280>] (do_group_exit+0x54/0xe0)
[   25.711248][    T1] [<8011d280>] (do_group_exit) from [<8011d31c>] (sys_exit_group+0x10/0x14)
[   25.719820][    T1] [<8011d31c>] (sys_exit_group) from [<80101000>] (ret_fast_syscall+0x0/0x50)
[   25.728559][    T1] Exception stack(0x8ec3dfa8 to 0x8ec3dff0)
[   25.734336][    T1] dfa0:                   76f2ac18 76f330a0 0000007f 7ebe4530 0000007f 00000000
[   25.743249][    T1] dfc0: 76f2ac18 76f330a0 76f33078 000000f8 76f2ab0c 6fffffff 76f3c970 76f32918
[   25.752157][    T1] dfe0: 7ebe4e94 7ebe476c 76f235f0 76f25314
[   25.757941][    T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]---
: /lib/arm-linux-gnueabi/libpthread.so.0: unsupported version 0 of Verdef record
/sbin/init: error while loading shared libraries: /lib/arm-linux-gnueabi/libpthread.so.0: unsupported version 0 of Verneed record

fck.ext4 shows 31 bad blocks (read). So I am assuming that's the issue.

The question is now: Do I need to buy another USB stick (and have it fail again in a year or two) or can I install debian on the internal HDD? I can't remember anymore why it wasn't on the HDD in the first place.

Very happy for any help, thanks!



Edited 2 time(s). Last edit at 09/21/2022 03:20AM by kiesel.

kiesel,

> The question is now: Do I need to buy another USB
> stick (and have it fail again in a year or two

You could run USB rootfs fine, with some wear-prevention setup as described here:

http://forum.doozan.com/read.php?2,13702,13704#msg-13704

> can I install debian on the internal HDD? I can't
> remember anymore why it wasn't on the HDD in the
> first place.

Which u-boot is on your box? stock u-boot or my u-bootrelease?

You can install directly to the HDD, but you need to run a USB rootfs first to make it easier.

While running the system with USB rootds, format the HDD and untar the tarball the same way you installed USB rootfs. With stock u-boot, there is more set up to be done. But with my released u-boot 2017.07 for this box, it should boot straight into the HDD rootfs (after removing the USB rootfs and reboot).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thank's, I'll replace the internal HDD with an SDD and install there.

I remembered that the reason for using a USB key in the first place was that otherwise the HDD can't spin down, and a SSD of course doesn't have that problem.

I got the new SSD and I am trying to set it up.

Your uboot is installed on the box (I had an older version of your debian releases running for a year) so that means I need to prepare the SSD only since your uboot will recognize them?

The issue is that as far as I can see I need to install 'linux-image-5.19.2-kirkwood-tld-1_1.0_armel.deb' on the box, but I don't have a working system on the box atm.

Which means I can't run

cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.19.2-kirkwood-tld-1 -d vmlinuz-5.19.2-kirkwood-tld-1 uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.19.2-kirkwood-tld-1 -d initrd.img-5.19.2-kirkwood-tld-1 uInitrd

Can I prepare the files on another linux machine?

kiesel,


> Which means I can't run
>
>

> cd /boot
> mkimage -A arm -O linux -T kernel -C none -a
> 0x00008000 -e 0x00008000 -n
> Linux-5.19.2-kirkwood-tld-1 -d
> vmlinuz-5.19.2-kirkwood-tld-1 uImage
> mkimage -A arm -O linux -T ramdisk -C gzip -a
> 0x00000000 -e 0x00000000 -n
> initramfs-5.19.2-kirkwood-tld-1 -d
> initrd.img-5.19.2-kirkwood-tld-1 uInitrd
> 
>

>
> Can I prepare the files on another linux machine?

There is no need to go to that trouble, just use the latest rootfs Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2. Get it running on the SSD. And then upgrade kernel to 5.19.2-kirkwood-tld-1 .

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

That worked on the first try, thank you so much! <3