What's new
SNBForums

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

After reset HDD label change to (1)

SebZab

Regular Contributor
After reset via GUI my usb hdd label change from Seagate to Seagate(1).
When I reset via buton on RT-N66U the label remains OK.

I noticed that last Merlin's soft which hasn't got this issue is 374_34. All new ones give me this additional (1) in label.

When it happens, in Segate I have got only download directory as set in pyLoad and in Seagate(1) there is real content of my drive.

Is there any solutions which allow me to use new soft higher than 374_34?
 
MiniDLNA

After reset via GUI my usb hdd label change from Seagate to Seagate(1).
When I reset via buton on RT-N66U the label remains OK.

I noticed that last Merlin's soft which hasn't got this issue is 374_34. All new ones give me this additional (1) in label.

When it happens, in Segate I have got only download directory as set in pyLoad and in Seagate(1) there is real content of my drive.

Is there any solutions which allow me to use new soft higher than 374_34?

I think it's related to MINIDLNA server.

I have a partition on HDD which contains miniDLNA database.
Only that partition is duplicated sometimes (MUSIC & MUSIC(1) )
 
I think it's related to MINIDLNA server.

I have a partition on HDD which contains miniDLNA database.
Only that partition is duplicated sometimes (MUSIC & MUSIC(1) )
to confirm this I used WinSCP to go into the mnt directory and spotted the original folder name containing a few files related to minidlna, you can rename it and reboot the router, then it sets it back to the correct name and allows deletion of the bogus folder.
 
Me the same.

miniDLNA has DAtabase and music in Media partition.

After reboot I find 'Media(1)' Which contains music and actual database and is locked, and Media which contains only a database but not in use because I can remove the whole mount point without problems.

Then I restart and Media(1) correctly beacomes Media.
 
This problem is caused due to too slow mounting of hdd in new Merlin builds.
Before hdd is mounted, other programs like minidlna or pyLoad make their own folders and after mounting there is conflict of names.
Soft 374_34 has not got this issue.
Temporary solution is to make reset via button in router not via web admin page. It helps.
 
Last edited:
This problem is caused due to too slow mounting of hdd in new Merlin builds.
Before hdd is mounted, other programs like minidlna or pyLoad make their own folders and after mounting there is conflict of names.
Soft 374_34 has not got this issue.
Temporary solution is to make reset via button in router not via web admin page. It helps.

if this is the case and Merlin can confirm it, my limited tinkering leads me to think starting minidlna via postmount would fix this ?
 
New Merlin's soft 374.40 beta1 has got still this bug.
I can't reboot router via GUI because (1) add to my hdd name.
 
Last edited:
New Merlin's soft 374.40 beta1 has got still this bug.
I can't reboot router via GUI because (1) add to my hdd name.

I got the same problem plus the slow speed on HDD (I opened a new thred explaining my problem). I've been looking in the forum and it seems like there is no solution to this. I think reverting to stock firmware will do it. Or maybe if RMerlin would give us a little help...
 
Last edited:
I have found solution. I removed hdd label "Seagate" with command:

tune2fs -L "" /dev/sda1
reboot

When hdd is only sda1 without label the problem with adding (1) doesn't exist
 
Great finding Seb! Although the command didn't work for me (or I didn't run it properly), I took the hdd out and manually did the label change on my computer. Now the hdd appears as sda1 and I think the problem is gone. Took a while, but you found it :)
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top