Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 11 FirstFirst 12345 ... LastLast
Results 21 to 30 of 105
  1. #21
    Junior Member
    Join Date
    Nov 2006
    Location
    Oxford, UK
    Posts
    11

    Attempt to improve instructions -

    Starting from a clean disk :-

    Unpack your files onto the TS box from the install package.

    These will be:-
    install.sh
    ubuntu-hoary-chroot-mpc82xx-2006-07-23-release-2.1.tar.gz
    01-mplayer-codecs-ppc-module-update.tar
    01-mplayer-dev-CVS-060408-18-07-3.3.5-ppc-module-update.tar
    01-SlimServer_v6.3.1-mpc82xx-2006-11-13-module-update.tar
    01-sox-ppc-module-update.tar
    01-timezone-2006-11-19-noarch-module-update.tar
    01-unicode-2006-05-29-ppc-module-update.tar
    01-usb-automount-2006-11-19-ppc-module-update.tar
    02-plugins-pack-6.3.x-2006-07-23-module-update.tar

    BEFORE YOU DO ANYTHING ELSE, create a folder called "updates" on your TS box and move into it all the files with names beginning 01 and 02. That leaves only ubuntu-hoary... and install.sh at the root of your TS box

    Then start your telnet session
    Type cd /share/HDA_DATA/Public (case-sensitive!)
    Then type ./install.sh
    Then type reboot <enter>

    Pause, several bleeps, and your TS box should have rebooted.

    That is, basically, what worked for me. For some reason, moving the 01... and 02.. files into updates AFTERrunning install.sh and the rebooting again doesn't seem to work - don't know enough to understand why.

    b33k34, from your first message, looks as though you did something wrong installing the link to ubuntu, so the script cannot find some of the basic Linux utilities. Can't see what went wrong on your second try.

    If you find you now have two disks that the TS box won't reformat and you don't want to hoick them out into a PC to reformat, then you need to start a telnet session to it and type the following:-

    mkdir /tmp/flash
    mount /dev/mtdblock4 /tmp/flash
    rm /tmp/flash/autorun.sh
    umount /tmp/flash
    reboot

    This undoes the link to ubuntu and gives control back to the standard QNAP version of Linux and reformatting the disk using the web admin tools should work properly again.

    Do email me in case of despair - this took me several hours of trial and error to figure out!

  2. #22
    Junior Member
    Join Date
    Oct 2006
    Posts
    13
    Thanks, I was beginning to worry when no one was replying. I will have to try this when I get home. I want to get a squeezebox, but would like to have this up and running before hand. Plus it would be a nice benefit to be able to reformat my NAS again.

  3. #23
    Junior Member
    Join Date
    Oct 2006
    Posts
    13
    The list of things to do did not work... I think I have tried it before cause the autorun file was not there to delete. Would taking the disks out and reformatting them work?

  4. #24

    Lightbulb Must reboot after installing each component

    Don't forget to reboot after each install to get the services running.

    BB

  5. #25
    Junior Member
    Join Date
    Nov 2006
    Location
    Oxford, UK
    Posts
    11

    I may have to do it again

    At some point I am going to switch the TS box from a single disk to mirrored disks, so will have to go through it all again.

    As BBear points out, you do need to reboot each time after running the procedures to remove autorun.sh.

  6. #26
    Senior Member
    Join Date
    Apr 2005
    Location
    Finland
    Posts
    119
    Quote Originally Posted by pcresswell View Post
    Starting from a clean disk :-
    My TS-101 has become painfully slow and I'd like to reinstall. However, I don't want to reformat my disk. Would it work if I simply deleted the ubuntu folder, rebooted and went through the normal installation procedure? If not, is there any way to cleanly uninstall SlimServer from the TS-101?

  7. #27
    Junior Member
    Join Date
    Oct 2006
    Posts
    13
    I have rebooted many times.. and still no autorun.sh

  8. #28
    Quote Originally Posted by Aylwin View Post
    My TS-101 has become painfully slow and I'd like to reinstall. However, I don't want to reformat my disk. Would it work if I simply deleted the ubuntu folder, rebooted and went through the normal installation procedure? If not, is there any way to cleanly uninstall SlimServer from the TS-101?
    I'm afraid I cannot help with your query here, the Progressive self-install instructions (http://www.progressiveav.com/ts101_u...tall/ts101201/) suggest that you CAN remove slimserver but then you need to reformat the disk.

    Just curious tho (which is the main point of this post), what makes you think that it's Slimserver itself which is making your QNAP run slowly and that a re-install will make it run quicker again?

  9. #29
    Senior Member
    Join Date
    Apr 2005
    Location
    Finland
    Posts
    119
    Quote Originally Posted by Ian_F View Post
    Just curious tho (which is the main point of this post), what makes you think that it's Slimserver itself which is making your QNAP run slowly and that a re-install will make it run quicker again?
    Well, everything else on the QNAP seems to run fine. Since this is an installation thread I don't want to go too much off topic but I've posted more about my slow TS-101 here: http://forums.slimdevices.com/showth...=203688#203688

    Anyway, I'm not sure what options I have to try and get things running normally again. I thought reinstalling would be one thing I could try but I don't really want to reformat the disk if that's possible.

  10. #30
    Junior Member
    Join Date
    Nov 2006
    Location
    Oxford, UK
    Posts
    11

    Firmware?

    Maybe it's worth trying to reinstall the firmware.

    I think what we have here is a very small Linux setup on flash memory, but it is a very "cut-down" Linux without most of the utilities (because most people will never use them).

    The Progressive install routine puts most of itself onto the hard disk but writes some files to the flash memory, but I haven't yet figured out where and how.

    "Upgrading" the firmware again may be the answer - luckily I haven't needed to try, but if you are otherwise stuck it might be worth a go.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •