[ECOS] Thermaltake MUSE, corrupted symlink to libc

[ECOS] Thermaltake MUSE, corrupted symlink to libc

[Mello Wiz]

Hi All,
maybe this should be a topic for a different alias but there's nowhere I can get help so I hoped that the experts here... pretty please!

I was fooling (!) with my Thermaltake MUSE NAS (board with ARM CPU, Flash, RAM + 4 SATA disks running a RAID software+HTTP/telnet server) when I changed the symbolic link to libc from one version to another (2.3.2 -> 2.3.6).

Sadly everything stopped and I was not able to revert the change.

Now the situation is:
1. I can get access to the board via serial cable
2. I can get the Redboot> prompt
3. the Linux system can be started via:
  RedBoot> fis load ramdisk.gz
  RedBoot> fis load zImage
  RedBoot> exec
4. at some point, during the bootup phase (I can provide logs), the systems hangs with the message:
...
...
+ cd /sysroot
+ umount /proc
+ '[' '!' -d initrd ']'
+ pivot_root . initrd
+ mount -t proc none /proc
mount: relocation error: /lib/libc.so.6: symbol _rtld_gmount: relocation error: /lib/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE not defined in file lKernel panic - not syncing: Attempted to kill init!
d -linux.so.2 with link time reference
+ StartRescueMode
+ exec /sbin/init
/sbin/init: relocation error: /lib/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference

Is there any way, by means of Redboot, to stop the above sequence and/or mount the file system and change the symbolic link I've modified?

TIA,
-mw


More details:


RedBoot> version
RedBoot(tm) bootstrap and debug environment [ROM]
Intel IOP RedBoot release
         version 2.2.V6-IOP-RedBoot
         built 13:51:51, Jan 12 2006

Platform: EP80219 (XScale) 
Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

RAM: 0x00000000-0x10000000, 0x00021790-0x0ffd1000 available
FLASH: 0xf0000000 - 0xf0800000, 64 blocks of 0x00020000 bytes each.


RedBoot> fis list
Name              FLASH addr  Mem addr    Length      Entry point
RedBoot           0xF0000000  0xF0000000  0x00040000  0x00000000
RedBoot config    0xF07C0000  0xF07C0000  0x00001000  0x00000000
FIS directory     0xF07E0000  0xF07E0000  0x00020000  0x00000000
zImage            0xF0040000  0x01008000  0x00200000  0x01008000
ramdisk.gz        0xF0240000  0x01800000  0x00400000  0x01800000
vendor            0xF07A0000  0xF07A0000  0x00020000  0x01800000
_________________________________________________________________
More than messages–check out the rest of the Windows Live™.
http://www.microsoft.com/windows/windowslive/

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] FW: [ECOS] Thermaltake MUSE, corrupted symlink to libc

[Mello Wiz]

Issue solved by starting the NAS without the disks plugged in.
Linux bootup process had to stop at some point while using the ramdisk version of the operating system.
From there it was pretty easy to:
1. plug the disks in
2. mount them
3. revert the change to the symlink
4. unmount the disks
5. restart the system

Sorry for the nuisance and thanks anyway for the patience,
-mw


> From: mellowiz@hotmail.com
> To: ecos-discuss@ecos.sourceware.org
> Date: Mon, 9 Mar 2009 19:38:00 +0000
> Subject: [ECOS] Thermaltake MUSE, corrupted symlink to libc
>
>
> Hi All,
> maybe this should be a topic for a different alias but there's nowhere I can get help so I hoped that the experts here... pretty please!
>
> I was fooling (!) with my Thermaltake MUSE NAS (board with ARM CPU, Flash, RAM + 4 SATA disks running a RAID software+HTTP/telnet server) when I changed the symbolic link to libc from one version to another (2.3.2 -> 2.3.6).
>
> Sadly everything stopped and I was not able to revert the change.
>
> Now the situation is:
> 1. I can get access to the board via serial cable
> 2. I can get the Redboot> prompt
> 3. the Linux system can be started via:
> RedBoot> fis load ramdisk.gz
> RedBoot> fis load zImage
> RedBoot> exec
> 4. at some point, during the bootup phase (I can provide logs), the systems hangs with the message:
> ...
> ...
> + cd /sysroot
> + umount /proc
> + '[' '!' -d initrd ']'
> + pivot_root . initrd
> + mount -t proc none /proc
> mount: relocation error: /lib/libc.so.6: symbol _rtld_gmount: relocation error: /lib/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE not defined in file lKernel panic - not syncing: Attempted to kill init!
> d -linux.so.2 with link time reference
> + StartRescueMode
> + exec /sbin/init
> /sbin/init: relocation error: /lib/libc.so.6: symbol _rtld_global_ro, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference
>
> Is there any way, by means of Redboot, to stop the above sequence and/or mount the file system and change the symbolic link I've modified?
>
> TIA,
> -mw
>
>
> More details:
>
>
> RedBoot> version
> RedBoot(tm) bootstrap and debug environment [ROM]
> Intel IOP RedBoot release
> version 2.2.V6-IOP-RedBoot
> built 13:51:51, Jan 12 2006
>
> Platform: EP80219 (XScale)
> Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
>
> RAM: 0x00000000-0x10000000, 0x00021790-0x0ffd1000 available
> FLASH: 0xf0000000 - 0xf0800000, 64 blocks of 0x00020000 bytes each.
>
>
> RedBoot> fis list
> Name FLASH addr Mem addr Length Entry point
> RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
> RedBoot config 0xF07C0000 0xF07C0000 0x00001000 0x00000000
> FIS directory 0xF07E0000 0xF07E0000 0x00020000 0x00000000
> zImage 0xF0040000 0x01008000 0x00200000 0x01008000
> ramdisk.gz 0xF0240000 0x01800000 0x00400000 0x01800000
> vendor 0xF07A0000 0xF07A0000 0x00020000 0x01800000

_________________________________________________________________
Show them the way! Add maps and directions to your party invites. 
http://www.microsoft.com/windows/windowslive/products/events.aspx

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss