I’ve been running raspbmc for nearly a year now, originally on an old original one, then on the B+ and now I’ve got hold of the pi 2, with a view to upgrading the three different media players/media servers that I’ve had. I upgraded the raspbmc with update/upgrade/rpi-update on B+, dd’ed it across and stuck it on a new card, then booted the pi 2.
Initially I was impressed with speed of the boot of the new rapsberry pi, but after a while I spotted something strange. Half my files were gone from my server. This is an external USB3 disk, with a bit of ext3 (for swapfile) and a lot of NTFS disc.
Worried that I’d lost all my media, I unplugged and checked on a pc. Fine, all files are there. So I plugged back in. SMB showed most of the files were missing, and some directories still there, but either contained nothing, or a file which wouldn’t fetch when I clicked to watch it.
Ssh into the pi itself, and correct the ls says they are missing. Pull the card, stick into Pi B+ again, and all the files are back…
I’m a programmer with over 15 years of linux experience, with the type of system admin involved with running home linux desktop during that time…
Any idea of how to proceed to diagnose this? I’d seriously replace all my pi’s with pi 2’s, but this is a basic fail. NTFS reading was solved a long time ago, wasn’t it? Anyone seen anything like this?
Err, I don’t know how you managed that, because Raspbmc cannot boot on a Pi 2 as the kernel is incompatible.
So can you please confirm what you are actually running - are you running OSMC RC2, or are you running some custom modification of Raspbmc with a different kernel ?
We can’t really proceed with any sort of troubleshooting until we’re sure what you’re actually running.
Yes, rpi-update was run. I ran it because I was averse to the clean install and remembering what I’ve installed again. I find it a pain to wipe and reinstall every so often, and previous to pi, I ran a hacked pogoplug server which you could easily brick during install…
I guess I’ll dd copy, wipe, install OSMC and set up again. Seems easier than diagnosis…
The problem with “diagnosis” of what you have now, is that you have a half Raspbmc, half Raspbian (kernel) Frankenstein that is unsupported and untested on Pi 2. You’re not actually running OSMC at all (Not to mention that Raspbmc is no longer being developed, so won’t be receiving any more updates or fixes)
The best way to migrate from Raspbmc to OSMC while keeping your Kodi config IMO is to do a fresh install of OSMC RC2 on another SD card, run updates to make sure you’re fully up to date (there have been quite a few updates since RC2) then put your old Raspbmc SD card into a USB card reader and plug that into your Pi.
This will automatically mount your old install under /media. You can then stop Kodi:
sudo systemctl stop mediacenter
Delete the default .kodi folder and copy your old .kodi folder directly into place without mucking about taring and untarring. (which saves a lot of time) Another advantage is you’re not destroying your original Raspbmc install by re-using the SD card so you can have multiple attempts at migration or decide to just go back to Raspbmc.
This will migrate your entire Kodi configuration including library, all skins, addons, keymaps custom settings and so on. This is the method I always use to migrate my Kodi config from one system to another.
If you’ve installed system software outside of Kodi in Raspbmc you’ll have to redo that manually of course - but since Raspbmc is based on Debian wheezy using upstart and network manager, and OSMC is based on Debian Jessie using systemd and connman there are a lot of differences anyway so no automatic migration is feasible.
If you’re still having any NTFS problems after setting up RC2 let us know and we’ll look into it.
Colour me unimpressed. As a long term coder on linux, I’ve found recent years has had the rise of emperors new clothes in distributions and osmc smells a little of this. Sorry
(I’ve long since abandoned Ubuntu, the bloated unstable mess that it has become with unwanted new desktops).
Anyway, so I ssh in, with full intention of getting it up and running. I’ll keep a text file of what I do. So, right.
sudo -i
apt-get install xemacs21
No? xemacs? emacs? No? Not even the basics.
Ok, I can go on in nano, but I’m not expecting a hell of a lot of packages there if the very basics are there.
Is this like completely brand new? Are we dropping raspbmc a tad prematurely.
Or is there a startup guide to setting up the basic respositories?
Sorry, just frustration.
I found out that the ntfs disc didn’t mount, and what had happened is that deluge had torrented a bunch of half finished files onto the sd card mount directory where the disc should be…
This is perhaps the most stupid post I’ve read in a long, long time.
As a long term “Linux” coder, I am extremely surprised we have been given no logs from you to diagnose the issue. Have you updated the APT repository first? OSMC is based on Debian. We have 30,000 packages available.
I strongly suggest you either provide sufficient logs that demonstrate an inadequacy in OSMC and how it is a regression over Raspbmc or otherwise vet your queries before posting.
Never assume a Debian’s package name is always the same across other distros. Use apt-cache to identify the appropriate package name first.
As always, patches welcome. Use those Linux skills to further OSMC in to the project you’d like it to be
OSMC doesn’t ship with a pre-populated APT cache, so until you run apt-get update the first time you won’t be able to install any packages.
Please remember that OSMC is a mediacenter operating system, not a general purpose Linux distribution. 99% of users will update via the Updates GUI in OSMC settings which takes care of running apt-get update (and dist-upgrade) for the user.
Power users who want to run updates or install packages from the command line should already know that you need to run update first to ensure the APT cache is up to date.
We don’t ship an APT cache both to minimise bloat in the install image, and because by the time a user installs an image it could potentially be a few months old and thus the cache is out of date and needs to be re-downloaded anyway - so why ship an out of date cache. It takes all of about one or two minutes to download the first time.
Ok, so the answer would be run apt-get update as the first command before any other.
However, to dismiss someone is stupid because you think debian is the only distribution, and people should immediately be experts, well thanks for the lovely attitude.
I’ve never worked on Debian professionally. Slackware. Mandriva. Suse. Centos. RHEL Ubuntu. Redhat itself.
And this being from the project lead.
I guess I will look elsewhere for my raspberry pi 2 distro.
I did not call you stupid, I suggested that remarks like this:
are stupid
I guess we all get frustrated. I don’t expect people to be experts at all, but they should be less quick in their conclusions: OSMC has all the Debian packages so it’s quite expansive.
It is quite common for users not to run apt-get update first, so I’m actually going to add a couple of sanity checks to the apt-get command (check for a cache, check its recent, check that the user has run it with sudo). So your post has helped improve OSMC in a sense. Thanks.
(Not to mention that Raspbmc is no longer being developed, so won’t be receiving any more updates or fixes)
