“the j stands for Join”
about me | research blog | wordpress plugins | jQuery plugins

25 July, 2011

How I revived my disappearing Seagate GoFlex Home DLNA/UPnP server

My family bought a Seagate GoFlex Home 2TB network-attached drive for streaming videos directly to our Samsung TV via DLNA/UPnP. Everything worked fine for a while, until suddenly one day it just refused to show up on the TV anymore. After eliminating all the home networking factors (cables, IPs, DHCP etc.), I noticed that when restarting the device it actually showed up briefly on the TV, but with no files on it – only to disappear after a few seconds.
Note that the device still behaved normally as a network device, i.e. when browsing using Windows Networking/SAMBA we could still access all our files normally. It was only the DLNA service that did not seem to be functioning.

Combing through the Seagate forums (and the web in general) I found that others have had similar issues but no real solutions seem to have emerged. So a little more investigation had to be done. The GoFlex Home web interface did not report anything untoward, and fiddling with all the settings in the preferences did not seem to have any effect.

So, like all good hackers I got my hands dirty and gained SSH access to the device.

Getting SSH access to the device

As described here and here, to gain access to your GoFlex Home via SSH you will need:

  1. An SSH client (obviously)
  2. The IP address of your GoFlex Home
  3. The administrator username & password
  4. Your device’s product key, which you can find by clicking About GoFlex Home in the bottom left of the web interface
  5. Confidence using the Linux command line

So, you open an SSH connection to your device with this specially-formed username USERNAME_hipserv2_seagateplug_XXXX-XXXX-XXXX-XXXX, where USERNAME is your username and XXXX-XXXX-XXXX-XXXX is your product key. On a Linux/Mac terminal this could look something like this (note the username, product key and IP will be different):

ssh john_hipserv2_seagateplug_FKSU-FJDU-DOWU-OSHD@192.168.1.100

Once you’re in, go straight into root — as you will need to do so anyway before long — with:

sudo -s

Of course poking around as root is dangerous and could irreversibly mess up your device, but if you’re still reading then you probably already knew that.

Restarting the DLNA service

At this point I tried poking around, trying to find some logs or anything which could give me an idea what the problem was. The name of the service which actually provides the DLNA server is minidlna, for which a totally invaluable reference can be found here. I tried to access the MiniDLNA log with

tail /tmp/minidlna/minidlna.log

but was told that the log was unavailable. Curiously, running ls -l in the directory reported that the file had no size, permissions, or modification date; so that wasn’t much help. I then tried to find the status of the MiniDLNA service with

/etc/init.d/minidlna.init status

which told me that the PID in /mnt/tmpfs/var/run/minidlna.pid did not match that of any running process, implying that the daemon had crashed. Made sense so far, but when I tried to restart the service with

/etc/init.d/minidlna.init restart

the service would attempt to restart, but instantly crash again as described above. Same thing with manually stopping and starting the service. Some trial and error later, I discovered that what needs to be done is is that MiniDLNA’s temporary folder needs to be forcibly unmounted, like so:

umount /tmp/minidlna

Restarting the service again after doing this finally did the trick; Checking the service’s status again as above now reports that MiniDLNA is running, and everything shows up normally on my TV etc.

Rebuilding the database

If the steps above still don’t fix your problem, you likely need to get MiniDLNA to rebuild its media database, with the command

/usr/sbin/minidlna -f /etc/miniupnpd/minidlna.conf -R -d

This time, I was given an error message about being unable to open sqlite database file, /tmp/minidlna/files.db. Attempts to force-delete the file manually also failed, and I finally had to resort to manually unmounting the minidlna directory with

umount /tmp/minidlna

This happily worked, and I was then finally allowed to rebuild the database with the command given above. This will scan your media folders and rebuild the database for you in MiniDLNA’s debug mode, which means it will spit out lots and lots
of output message to the console. After maybe 5 minutes or so, it finally told me the media library scanning was complete, and lo and behold I could once again access my GoFlex Home via my DLNA-enabled TV.

Now, I am still unclear as to what happens when I restart my device. The first time I tried this (after rebuilding the media database) my device went into the exact same problem as before! This time I logged in via SSH again, and run the MiniDLNA daemon in debug mode but without rebuilding the library:

/usr/sbin/minidlna -f /etc/miniupnpd/minidlna.conf -d

This successfully started the service again, allowed me to cleanly exit my SSH connection and access the DLNA server via my TV again. However it did take many minutes until my files all showed up, so I am assuming that MiniDLNA was in fact rebuilding the media database itself.

Conclusion

Despite finally managing to get things working as described above, it turns out that every time my GoFlex Home is restarted the MiniDLNA daemon crashes in the same way, and I am forced to fire up an SSH connection to sort things out. I have as yet found no way of permanently fixing the issue, but since our device is basically online 24/7 it’s not too much of an issue.

Of course I realise the steps here are not for the computer faint hearted, but after exhausting all the “user-friendly” ways of restoring the device, this is only sure-fire way I have found.

97 Comments »

  1. i am having an issue with all this sh@t as well.
    seagate goflex home 2 tb
    slow refresh

    Neil – did this all work for you?

    Comment by brandon — 11 December, 2012 @ 9:47 pm

  2. Hi guys and special thanks to John…………however…

    I have gf 3tb, samsung tv and a sharp tv, various laptop/tablet and desktop windows my prob is not being able to view all folders via the TV’s

    I have followed John’s guide and have tried dbase rebuild but am unsure if it completes. I get a close connection after 10mins or so, but then can access some folders fine

    I can then see only 5 folders which is 1 more than before, there are about 20 folders with 690gb being used of a mostly photos and movies

    Any ideas anyone please. I am considering a factory reset option

    Thanks
    Hari

    Comment by Hari Birdi — 13 December, 2012 @ 11:10 pm

  3. ps Neil pls advise if it worked for you I did also delete the files.db and allow rebuild

    Comment by Hari Birdi — 13 December, 2012 @ 11:14 pm

  4. any new news gents???

    Comment by brandon — 16 December, 2012 @ 12:28 am

  5. Hi. Great blog. Have the same problem ie won’t refresh media changed and stopped mid database. What would be the most simple process to restart the indexing process etc using a window platform. Any help is most appreciated. Spent days looking for answers to no avail. . Thanks

    Comment by Glen — 22 December, 2012 @ 8:55 am

  6. Thanks the procedure worked when I couldn’t find newly copied files on my drive via UPnp.

    I had to type in my userpassword to become root. Got an error afterwards that some logging doesn’t work, but I was root.

    All that seems left in the moment is.

    [2012/12/26 14:45:25] upnphttp.c:918: warn: /MediaItems not found, responding ERROR 404

    Comment by nils — 26 December, 2012 @ 5:19 pm

  7. Having the same issues as most here.
    I’m new to Linux but have been able to follow fairly well
    When I run /etc/init.d/minidlna.init status
    It tells me: A MiniDlna server seems to be running (PID: 14894), but no PID file exists. Probably no write permission for /var/run/minidlna.pid

    Any ideas on how I can fix this
    Any help is greatly appreciated

    Comment by Ken — 13 January, 2013 @ 8:32 pm

  8. Thanks John and posters for this.

    I had the ‘only showing a handful of files’ problem, for which the solution turned out to be
    – rename the directory containing the offending file to z……. (so that it gets scanned last – I’m not bothered about sharing the files in that directory anyway)
    – stop the minidlna process
    – rebuild the database (which is still churning away nicely)

    Comment by Brian — 20 January, 2013 @ 1:00 am

  9. Hey All,

    Few notes:
    – I am running OSX 10.6.8
    – Issue is, GoFlex shows up on xbox but not media shows up other than default GoFlex videos

    Issue im having (Copied from Terminal):

    -bash-3.2$ sudo -s
    Password:
    audit_log_user_command(): Connection refused
    bash-3.2#

    Does anyone know what is causing this? i am new to Macs but work heavily with PCs.

    Thanks,
    D

    Comment by D — 24 January, 2013 @ 6:13 am

  10. I am having a problem when I `sudo -s`. It is asking for a password. I don’t know it other than the GOFLEX password which doesn’t work.

    Comment by peter greeley — 24 January, 2013 @ 10:32 pm

  11. The password which you set it for the first time should work for the sudo -s password or the same password given by when you ssh to the device

    Comment by Siva — 26 January, 2013 @ 4:04 pm

  12. I don’t think audit_log_user_command(): Connection refused is a problem. Just do a whoami and you will see that you’re logged in as root.

    bash-3.2# whoami
    root

    Comment by Sidd — 11 February, 2013 @ 7:24 am

  13. Hi been having problems with my seagate home and after some time on google came across this. This is my log, does anybody have any idea what to do to fix it?

    bash-3.2# tail /tmp/minidlna/minidlna.log
    [2013/02/13 18:16:23] minidlna.c:909: warn: Starting MiniDLNA version 1.0.22 [SQLite 3.6.14.2].
    [2013/02/13 18:16:23] minidlna.c:932: warn: Creating new database...
    [2013/02/13 18:16:23] scanner.c:732: warn: Scanning /home/0empty
    [2013/02/13 18:16:23] scanner.c:803: warn: Scanning /home/0empty finished (0 files)!
    [2013/02/13 18:16:23] scanner.c:732: warn: Scanning /home/shellz090/GoFlex Home Personal
    [2013/02/13 18:16:23] minidlna.c:1010: warn: HTTP listening on port 8200
    [2013/02/13 18:16:24] scanner.c:803: warn: Scanning /home/shellz090/GoFlex Home Personal finished (25 files)!
    [2013/02/13 18:16:24] scanner.c:732: warn: Scanning /home/0common
    [2013/02/13 18:29:05] upnphttp.c:958: warn: HTTP Connection closed unexpectedly
    [2013/02/13 18:29:06] upnphttp.c:958: warn: HTTP Connection closed unexpectedly

    Comment by liam — 13 February, 2013 @ 8:37 pm

  14. I found that I was having a “session disconnected” error while using Putty; the problem was that my username “admin” needed to be lowercase, even though the page where I created it said it wasn’t case sensitive, and the instructions I’ve read for accessing the server show it being uppercase. Bottom Line: Make the case match what you entered it as when configuring the unit.

    Comment by Tom — 16 April, 2013 @ 5:28 am

  15. After constantly having to reboot / rescan my library enough is enough and after some further googling I’ve taken the plunge and install Meidatomb to my device in place of the stock MiniDLNA software.

    Not too complicated to install and it just sits on the back of whats already there so no need to re format the drive etc.

    So far so good and seems stable enough, even after a reboot it comes back up and just a case or re scanning from Mediatomb web interface to get stuff showing again.

    http://mediatomb.cc/pages/userinterface

    Cheers

    Jason

    Comment by Jason — 10 May, 2013 @ 8:19 am

  16. I have had intermittent problems with disappearing dlna after the number of files/directories on my Goflex Home 2TB got into the hundreds in the Public partition. I had been accessing the drive with a win7 pc and with a MK808 android stick and for many months everything was fine. It may have been some quirky file or directory names causing the problem.

    After a few days of trying various settings, routers and apps I found this blog. I tried resetting and loading new firmware on the goflex home, but dlna was still not showing up. Then I opened Seagate Share > GoFlex Home Public > submenu (click the little right arrow) > “Unshare with Media Devices”. After selecting “Share with Media Devices” it seems to reset the database and everything has been fine for a week or so. This might be the solution for you too. .

    Comment by Ray — 5 August, 2013 @ 7:49 am

  17. i follow the above step , could find the most of the files in the public folder , but unfortunately the back drive and personal folder disappeared now . i see that capacity of the harddrive did not change but the files in public and backup has completely disappeared .

    Guys Need some help . just recently moved my important files to the Go flex drive .

    Steps followed :
    /etc/init.d/minidlna.init status
    /etc/init.d/minidlna.init stop
    /usr/sbin/minidlna -f /etc/miniupnpd/minidlna.conf -R -d

    after this steps i was able to rebuild the folder , but i could only discover some 20 file i created in Public , all other folder including the other shares (Backup & Personal) disappeared . other 2 shares show no files are displaying.

    couple of times i tried to rebuild but after building some files it get disconnected with a message that gofles IPaddress:portnumber is not reachable .

    need suggestion .

    Comment by Magesh — 7 August, 2013 @ 5:19 pm

  18. Great guide, did not quite fix my issue (which was the media devices not reading more than a couple of files). Forcing the update alone didn’t fix the problem, and I didn’t have an issue with the service stopping.

    What I had to do was edit the minidlna.conf file so that it pointed to the correct folders (correct used loosely, but hey they worked). WITHOUT taking a single thing away from this guide here is step-by-step what I done. I have no previous knowledge of bash, linux or dlna, all the info presented here is based on this blog (plus a small bit of complimentary googling), and is only intended to supplement it b showing my specific case. Anyway enough B***S**T from me, thanks again great post very big help

    1. Open PuTTy SSH Terminal
    2. Enter username: USERNAME_hipserv2_seagateplug_XXXX-XXXX-XXXX-XXXX (Where USERNAME = web login username, and XXXX-XXXX-XXXX-XXXX = the product ID)
    3. Enter password: the same as web login
    4. Type sudo -s and press return
      This will enter root (you can brick your device if you make the wrong changes here, be warned!)
    5. Type dir /home
      This will give you a list of folders in your home directory one of which should be your username
    6. Type dir /home/subfolder (where subfolder is the name of one of the subfolders e.g. /home/bob)
      This will give you a list of folders in your account (I use the term account very loosely)
    7. Type /bin/init.d/minidlna.init -stop
      This will stop the DLNA service
    8. Type vi /etc/miniupnpd/minidlna.conf
      This will open the minidlna.conf file in the VI editor
      Here is my original file for comparison
    9. Press i
      This will enable editing of the file
    10. Add the line(s) media_dir=/home/USERNAME/ACCOUNTFOLDER (See updated config below for example)
      repeat for all folders containing files
    11. Comment out the existing media directories (e.g #media_dir=/home/0empty) unless they are being used i.e. folders with no media files
    12. Confirm “inotify” is set to yes
    13. Press “ESC”
      This will revert VI to command mode
    14. Type :w! and press return
      This will overwrite the existing file and save the changes
    15. Type :q!
      This will exit the VI editor
    16. Type /usr/sbin/minidlna -f /etc/miniupnpd/minidlna.conf -R -d and press return
      This will force the DLNA database to update, takes a while
    17. When complete, type /bin/init.d/minidlna.init -start and press return
      This will restart the DLNA service
    18. Type /bin/init.d/minidlna.init -status and press return
      This will confirm to you that the service is running again
    19. As an option you can also lower the notify period and enable tivo, up to you.
    20. Test on media device
      Hopefully all well at this point (if not I’m shit outta ideas, sorry!)
      Here is my modified .conf file for comparison

    Comment by smijen — 25 September, 2013 @ 8:12 am

  19. I don’t know how many people would have the same problem as me, but if someone is still having trouble with it, I fixed mine FINALLY.

    Basically what happened is it would only go to my Justin Bieber music folder, then stop. I took out the folder, and it worked properly.
    After looking at the contents of the folder, I realized something: It was the only folder in the whole drive with a .NFO file in it.
    I don’t know if maybe uPNP messes up with trying to read these files, but after I did that, everything else gradually poured in completely correctly.

    Hopefully this helps someone other than myself, I’ve dealt with this for about a year now.

    Comment by Austin — 30 September, 2013 @ 6:26 am

  20. Im reading all comments of this blog, but, i dont work in linux or another language of programtion. Pls I need help , if you are make a script pls send to me.
    Sorry for my rudimentary english. I have 3 TB GoFlex.

    Tks

    Comment by Bruno Fusaro — 18 October, 2013 @ 3:52 am

  21. Thanks a ton. I have had the same problem for a year but now its all fixed. 🙂

    Comment by Dino — 7 November, 2013 @ 3:21 am

  22. Anyone getting: “urn:schemas-upnp-org:device:WANConnectionDevice:1, MX: 5, MAN: “ssdp:discover” error message while scanning the device, check the last file before this error. It either has some special characters, or it is broken AVI. Just remove this file and you will be fine.

    Comment by Hobbit — 10 November, 2013 @ 11:36 am

  23. Very helpful..

    A few things to add:

    after sudo -s, just stop the media server

    /etc/init.d/minidlna.init stop

    then force a rescan

    /usr/sbin/minidlna -f /etc/miniupnpd/minidlna.conf -R -d

    either watch it work, or go find a long book to read, then restart the server

    /etc/init.d/minidlna.init start

    OR

    /etc/init.d/minidlna.init restart

    (I forget which). If this does not fix things, there may be file system corruption to deal with. Do a google search for pchkntfs. It is basically chkdsk for the goflex box. You can unmount /dev/sda1 and scan it for issues (I unmounted mine using the web interface, but you should be able to unmount it if you are root.) then reboot and fix the dlna sesrvice.

    Comment by Luc — 30 November, 2013 @ 4:36 pm

  24. Hi
    my goflex home drive died.
    Can I insert a new hard drive and get it working?
    It doesnt recognise it when I put a new drive it (not a goflex drive just one I have spare).
    I’m guessing I need to format and mount the drive somehow.
    Can anyone provide details on how to do this?
    (I’m not a linux user)

    thanks in advance

    Comment by stef — 26 January, 2014 @ 3:22 pm

  25. Hi everyone,

    Slightly different problem for me, but after two days of wrestling with the unix command line, I thought the following insights might be helpful to anyone else having issue with their seagat drive.

    I go my seagate home 3 TB NAS drive in 2008, and it worked fine, although it wasn’t in constant daily use. I use a PC and my wife uses a MAC, and we had both backed up files to the drive.

    We recently encountered a problem where the permissions on the device appeared to have gotten scrambeled, so it was possible to log into the seagate drive in a browser, or using the seagate share application, but all our files were missing, even though our passwords were correct, and we hadn’t deleted any data.

    Having worked with unix in the past, I used the ssh tip above to get into the command line and look around for clues. The permissions seemed to have got messed up somehow, wiht one users folder belonging to anohter. Also, when I attempted to run a firmware update on the device it failed.

    I tried resetting the device to factory defaults, and no joy there either, only now I had to recreate everyone’s password.

    Then, purely by accident, I was back at the command line looking for clues, so I checked the version of liux being used by the seagate unit using the command #

    uname – a

    I was clutching at straws to see if there were any more articles that might be useful.
    I noticed an entry which references to something called ‘axentraserver’
    So I googled that word, and immediately foung this article :

    http://support.goflexhome.hipserv.com/en/reflash/index.html

    I did this, recreate all user accounts, and everything was back to working order.
    It seems the firmware sent out with the drives may be less than perfect, so hopefully the problem is now sorted.

    Good luck to anyone struggling, I won’t buy any seagate items in future on principle, as the thought of loosing data scares the heck out of me

    Comment by karl — 22 February, 2014 @ 5:17 pm

  26. I kept getting a problem where after a power loss to my 2tb home pro.
    The server would still appear but without any files!
    Every thing else seamed fine!!
    I only share a couple movie folders and all I do is UNSHARE with media devices then reshare the folders!!
    My goflex seems to just rebuild the shared library nd all is back on.
    Seems to simple but hope this helps somebody.

    Comment by Pete — 27 March, 2014 @ 1:41 pm

  27. Thank You very much!
    It was driving me crazy, but now it’s perfect!
    Fantastic blog!!!!!!
    Thank You again!

    Comment by Alexandre — 31 March, 2014 @ 6:34 am

  28. HI,
    My go flex home drive has just started having issues, I use it for video streaming. I have 6 main folders on the root drive with multiple files under each, I can see all files from my PC. When using my PS3 or smart TV, I can only see the first main folder and then the first 20 under that, all other content is hidden. If i change the name of my folders so that folder 3 is n ow shown in postion 1. I can now see the one but no others. I hope this makes sense & any help of how to get all of my content back would be great.

    Thanks in advance?

    Comment by Jason — 16 April, 2014 @ 9:47 am

  29. Thought I would add a fix I came across. I have a 3TB drive nearly full… used solely for media streaming throughout my home to several tvs/phones/tablets/pcs.

    Every 3-4 days my drive would become unresponsive and require a reboot. When it was unresponsive, all streaming died, drive mappings were unavailable, and I could not SSH into the device, but it would respond to a ping. Leading up to a crash, my data transfer speeds would start to slow down drastically. After several weeks of monitoring, I found the process igd-daemon was using a tremendous amount of memory — 40-50% and was consuming almost all of the swap space. Normally I can copy to the drive at 250-275 mbps, but this would sharply drop when memory was reaching capacity (till hit hit 0 mbps). If left, igd-daemon eventually consumed all memory/swap space, and the device crashed. Rather than prevent the daemon from launching, I simply set it to restart daily.

    I added a quick script (igd_restart) to /etc/cron.daily/ with the following:

    #!/bin/sh
    /etc/init.d/upnp-igd restart

    Step by step process (# indicates shell command):
    1. change to directory: #cd /etc/cron.daily
    2. create file: #sudo touch igd_restart
    3. edit file: #sudo vi igd_restart
    4. in vi editor, press i for insert
    5. add content above (2 lines)
    6. press esc to cancel insert mode
    7. press :w to write to file
    8. press :q to quit vi
    9. make file executable: #sudo chmod a+x igd_restart

    The cron daily jobs run automatically for you, and will keep memory usage in check. You could also place this in cron.hourly or cron.weekly instea of cron.daily if you prefer. There doesn’t appear to be any impact in restarting this service, everything still works just fine for me.

    FYI – The igd-daemon is used to support uPnP port forwarding in routers.

    Hope this helps someone.

    Comment by Jiggs — 1 June, 2014 @ 8:42 am

  30. Hello.
    I’m having a similarly frustrating issue as well with my Goflex Home. When trying to access the drive through windows vista /7 or version 8.1 it won’t accept my username and password anymore by typing the IP address in windows explorer ex. \\192.168.1.130 . After messing around with it for weeks I hit the reset button with a paperclip, reset the drive up, used the same username and password as before and it fixed it as I could browse through explorer and even map the drive again, but the next day it started doing the same thing again!

    When I go to map network drives and click browse something is now showing up called AXENTRASERVER? wondering if this has something to do with it or not, I don’t have any other devices like the GoFlex on my network so this must be it?

    Anyone know how I can resolve this issue as I really need to be able to map the network drive to be able to manage it the way I want to, right now I have to login with FTP using the same IP, username and password which is much more of a pain.

    Thank you!

    Comment by Brett — 8 June, 2014 @ 6:01 am

  31. […] media. I had a side adventure figuring out how to rebuild the database. A useful link I found was this one, where John has a similar NAS with the same service (minidlna) and had some similar issues. […]

    Pingback by DLNA Adventures | engunneer.com — 2 December, 2014 @ 3:57 am

  32. I’m able to connect to the device, I enter my password and I receive this prompt; -bash-3.2$

    I then type in sudo -s and receive the following notification, though even after entering my password (the same as previously entered) it rejects my attempt;

    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

    I receive; audit_log_user_command(): Connection refused

    I then try the tail /tmp/minidlna/minidlna.log step as listed in your guide and receive this;

    tail: error reading `/tmp/minidlna/minidlna.log’: Input/output error

    I then try /etc/init.d/minidlna.init status;

    Which displays that Minidlna is running; MiniDlna is running.

    So I try to unmount the service as listed using umount /tmp/minidlna;

    umount: /tmp/minidlna: device is busy
    umount: /tmp/minidlna: device is busy

    I’ve tried rebuilding the library following the latter steps on your guide but again this did not seem to work;

    Trying to debug the service didn’t work;

    bash-3.2# /usr/sbin/minidlna -f /etc/miniupnpd/minidlna.conf -d
    [2015/01/13 17:21:16] minidlna.c:821: error: MiniDLNA is already running. EXITING.

    Do you have any ideas at all as to why this is happening?

    Seagate are refusing to support me, stating it must be the media devices with the issue as the device is read/writable from my Mac.

    Comment by Yosuf — 15 January, 2015 @ 6:28 pm

  33. If anyone still has that, Ray’s solution completely fixed my issue without having to ssh or anything like that.
    Thanks Ray!!!

    Comment by Alex — 1 February, 2015 @ 7:35 am

  34. I had a 2TB GoFlex which was not pushing anything via DLNA, but then I had another with a small 60Gb drive which was happy to share a couple of videos without a problem. This discussion nudged me in the right direction. Haven’t got a clue about Linux but I got rid of the default shares and shared only the media folders I needed, which worked a treat.

    Thank you everyone.
    Simon

    Comment by SImon Fraser — 19 February, 2015 @ 11:30 pm

  35. Thanks for these posts it’s the only useful thing I have found for the problem which I have been experiencing for 3 years. After going through this many times with the server running fine, but when I rebuilt the library it would fail at the same point which was obviously why I could only ever see files up to this on all other devices. When I shifted the file the problem would move, and If I shifted it to the end it would move to the end so I could see everything but whatever was after this file (note I found you can do this in explorer and the device will eventually rebuild the library itself). So I went to play the file and it appears to be corrupted, after deletion the full library has rebuilt and all was good again. So similar to post 20 it appears if the server does not like a file for some reason try isolating this file somewhere and see if it eventually rebuilds itself (perhaps try a reset). Keep doing this until all of the corrupted files are identified and you should be good without even going into SSH.

    Comment by inka — 22 February, 2015 @ 12:24 am

  36. Further to my previous comment if you reset the device on the GoFlex Home – Preferences web page (under Shutdown) then it appears to rebuild the library automatically when restarting. If you view the device on a TV you can see the files being added to the folder list as it occurs and eventually where it stops. If it stops before the end of your directory tree then chances are the file is corrupt and needs moving. I ended up moving all of the suspicious to a directory I created at the end of my folder list so I can still see them in windows, but not on the DLNA server list. Then either rename if that’s the problem (post 20) or delete and download another copy if possible. As mentioned this can be done without entering SSH.

    Comment by inka — 22 February, 2015 @ 12:57 am

  37. Mr. John, i’m writing you from Portugal, Leiria City. I hope you may help me to recover my disk. I have a expansion seagate drive USB3.0 2TB. I have it connected to a router ASUS rt-ac66u, beeing share in my homenetwork, with a directory with several folders (backupmovies, backup software, etc). the drive wasn’t formatted when i bought it because it already was in ntfs i think. I just simply started to save files there and connected to the router and it always worked well. A few days ago the disk looks empty with a directory with this structure : .minidlna(folder) + files: .___var + .___var.txt.6 + .__admin_var + .__admin_var.txt.6 + .__folder_list + .__folder_list.txt.9 . What do you think it happened? How do i recore it? Thank you for reading this. Sorry for my english.

    Comment by Pedro Santos — 22 March, 2015 @ 12:11 pm

  38. Lads, this is all excellent stuff.

    Zoltan comment #20 was on the button with what caused my issue, but having read a few things now I’m going to tweak this damn thing to make it hum!

    SeaGate really need to have a better UI for this thing in terms of identifying issues and running DLNA rebuilds. Even my ancient D-Link DNS-323 has this capacity!

    Comment by Pfitzy — 5 April, 2015 @ 7:59 am

  39. Hi there! Gabriel from Slovakia is greeting you, and I want to send you a BIG thanks, you are a genius! It works, can’t belive, but it works! Tried flashing the firmware, factory reset… sharing’n’unsharing – useless. But with restarting the dlna service, it works again. THX!

    Comment by Gabriel — 7 June, 2015 @ 9:01 pm

  40. Really good information on this page. I wished that Seagate could have the same support but it seems to be impossible to get in touch with them!

    I’ve lost contact with my GoFlex Home hard drive (NAS) and I have followed the instructions contained in the user manual by taking a paper clip and press the reset button for 10 seconds. I used the exact same user name as it stood so now I have contact with the hard drive, but the drive has got a new IP numbers and device names has changed. My backup drive letter previously (X) has gained a new drive letter (Y). I see my old folders and there is 911 GB on the disk but the disk says there is zero files. Any suggestions on what I should do?

    Comment by Conny — 30 September, 2015 @ 7:20 am

  41. HI guys

    been looking at this for a while now.. worked for a bit and then bombed out.
    then I had the idea… the database is way tooooo big for the device..

    so I have amended the configuration to point the files.db and log onto the hard drive…..

    Bingo.. its working fine…
    so go ahead and mkdir /home/0common/minidlna

    add the following to the config

    #——————————————————#
    # set this if you would like to specify the directory where you want MiniDLNA to store its database and album art cache
    #——————————————————#
    db_dir=/home/0common/minidlna/db

    #——————————————————#
    # set this if you would like to specify the directory where you want MiniDLNA to store its log file
    #——————————————————#
    log_dir=/home/0common/minidlna/log

    then a reboot … try that…

    Comment by glyn — 25 October, 2015 @ 9:00 pm

  42. This site is invaluable. Thank you!!!

    For TiVo owners, if the minidlna is working fine and then one day it suddenly stops working, one possible cause is that the IP address of the minidlna server changed (e.g. router restart and DHCP assigns it a new address). Restart the TiVo for it to re-discover the new IP of the minidlna server.

    Comment by Todd Carmichael — 25 December, 2015 @ 12:26 am

  43. Awesome blog!!!
    I’m feeling rather pissed off at the moment. My 2TB Goflex_home failed with similar symptoms described in this blog. In my case I’m not using the DLNA but still could not see files beyond the top couple of folders. I paid a data recovery firm lots to recover my files, scrapped the disc, and put a new drive in my Goflex_Home. Two months later it happened again.

    Using various bits of this blog I have been able to resurrect my files. Looks like it is a case of corrupted database.

    Comment by Richard — 17 February, 2016 @ 1:14 am

  44. I just wanted to say thanks!! I’ll start off by saying I have zero experience in using SSH. My only issue was the SSH client. I ended up using putty and because of how it’s set up, once again first time using it, the login command failed because of me adding the ip addy when it was added (again?) by putty since i put it in to connect before putting in the login command line.

    Anyway it all worked out and it is for now showing up again on my DLNA devices!!

    Comment by Craig — 16 May, 2016 @ 3:54 am

  45. Hi guys,

    Just stumbled across this as I have encountered problems with my Go Flex.
    Had issues before but a deep reboot had always seemed to fix them.
    Issue I have now is strange. I can view all files and folders on my DNLA TV. If I logon via web browser to golfex_home I can view all my files and it lets me into preferences.
    Problem if that if I try and access through windows explorer like I normally do its asking for user and password, when I put these in it just states error (i know these are correct as I use them on web browser).
    I am resigned to the fact this device is about dead but I would like to get some backups from it before I bin it.
    I have tried to create a new user in web browser preferences but it won’t allow me stating not enough space on drive (even though it shows 1.5TB free!)

    What would peoples next step be so I can try and access via Windows explorer? Should I go firmware update first and take it from there?

    Comment by Simon — 8 July, 2016 @ 10:12 pm

  46. […] Most personal NAS are just a hard drive connected to a computer board that has a small operating system embedded on a chip.  It’s this additional functionality that makes it into an appliance rather than just an external drive.  You can use SSH to connect to a GoFlex device (or my new one, a Western Digital MyCloud Personal).  It’s a command line interface, so you need to feel comfortable in Linux without an interface.  I’d done this a couple of times when the minidlna media server hung up. […]

    Pingback by Data Migration When My Network Drive Started to Fail – David Whelan — 16 September, 2016 @ 4:44 pm

  47. I’ve tried using the formatted userid as suggested in the original post, but just get “Server unexpectedly closed network connection”. It could be an issue with the productID, since I took that off the bottom of the unit (the web page referenced doesn’t show any productid). Could it be there are different versions that react differently? Mine states it is software version 2.6:2.0.0.382:1.2.340.

    Comment by hwmiller — 21 January, 2017 @ 2:23 am

Leave a comment