Recent Forum Posts
From categories:
page 1123...next »

Another reminder why backup is important.

Hello,

I changed, by mistake, into "/etc/passwd", the root shell of "/bin/sh" to "/bin/bash"
Now I can not access by SSH as root

I have tried several methods (like creating a symbolic link for "/bin/bash" to "/bin/sh") but the admin user does not have privileges to make the changes I need.

Is there a way to recover access to root without deleting hard disks?
Thank you

I have also been interested in doing this myself but I haven't got a spare 2TB hdd to test with.

I was thinking of looking at the php code for factory reset, see what scripts it runs to reformat the partition.

*edit*

I been looking in "SxM_webui\admin\tools\" and there is fullrestore.php wixMke2fs and wixResize2fs which look interesting.

wixMke2fs and wixResize2fs look like shell scripts but are encrypted which makes it hard to work out how it formats it.

After some years of working well (despite the occasional glitch) about a week ago it seemed to go badly wrong. I was getting no http service though ping was working. Soft switch on back would not respond so I powered it down and waited before switching back on at mains. Then it would not boot. Span up bottom light on then top light and back round loop. I removed drive purchased a sata to USB cable and plugged into pi. Recognised drive but no partitions. Tried lots of different commands but no joy.

Hdparm I reports the following:

/dev/sda:

ATA device, with non-removable media
Model Number: WDC WD10EARS-00MVWB0
Standards:
Likely used: 5
Configuration:
Logical max current
cylinders 0 0
heads 0 0
sectors/track 0 0

Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 0 MBytes
device size with M = 1000*1000: 0 MBytes
cache/buffer size = unknown
Capabilities:
IORDY(may be)(cannot be disabled)
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 0 Current = ?
DMA: not supported
PIO: pio0
Logical Unit WWN Device Identifier: 50014ee204e54aaf
NAA : 5
IEEE OUI : 0014ee
Unique ID : 204e54aaf
Checksum: correct.

Any ideas? Would like to access data if possible.

Many thanks for reading and any suggestions.

Hi,

So… I've got the before-mentioned WD product & I want to upgrade its inner storage from the existing 1 TB Green (WD10EARS) to 2 TB Green drive (WD20EARS).

I already managed to get a dump of the mybook.img file off the existing working 1 TB version. Using the dd command in System Rescue CD 5.0.0. distribution I managed to successfully unpack/clone everything to the WD20EARS drive.

So how do I expand that unallocated space after sda4 in order to make the OS "see" 2 TB of space & not the default 1 TB ?

In the console I tried running the command:

mdam --grow -size=max /dev/md2

And it didn't work.

So I tried issuing command:

mdadm --fail /dev/md2 /dev/sda4
mdadm --remove /dev/md2 /dev/sda4

Also didn't work, so I didn't even bother with the followup commands.

Any advice on how to solve this ? Do you need picture references ?

Thanks,
Dave

Scratch that!

Previously when I did this, it didn't work, but this time is has, using the Martin Hinner hack - as listed in the First Steps guide.

If anyone has any questions, fire away. :)

Adam.

Hi all,

This is probably quite a long shot considering how old the bluering WD device is these days. However, I decided to put in a 2Tb drive - which I've done quite successfully. However, the issue came where, after I'd enabled SSH, I then updated the firmware from the basic version included in the recuse build to 02.00.18. Despite enabling the SSH client as per the instructions on this site in /etc/inetd.conf and /etc/inittab upon installation of the newer firmware, SSH is disabled, as it is post-reboot. So I'm stuck.

I've tried unsuccessfully to run through the various SSH enabling options to no avail. My only options seem to be to run through the whole process of rebuilding the disk and just ensuring I don't upgrade to the latest firmware. Frustrating!

Help?

Thanks,
Adam.

I managed to find out why twonky is unstable, it should have been obvious it wasnt at the time.

Windows 10 server on the network causes twonky to crash even though I've havnt connected to twonky or the NAS. If I shutdown twonky prior to windows, NAS works fine.

and twonky starts up and stability is fine when windows is shutdown.

Anyone know why?

I went through a lot of these steps with frustration, but got it sorted in the end (copying data off now). Yes, the steps above to use a Ubuntu version are needed, the nice thing is that it's a lot more friendly than 5-6 years ago. You'll need to do some web searches to fill in some of the details, but the bottom line is that my NAS My Book World white light version (bought ~2013) had an XFS filesystem with RAID set (no idea why, only a single drive). But the RAID flag prevented the drive from being mounted.
Also, I tried using the rescue tool to rebuild the partitions, but that didn't work.
1. Remove drive and attach to your computer, steps listed in this blog.
2. Create a Ubuntu USB (I used Rufus after download to build the USB).
3. Log in and open a terminal window, do "sudo su" - will ask for your password, but put you in root.
3. Get gparted software (apt install gparted) - if it's already installed it will let you know. Also get mdadm (apt install mdadm) - not sure if this is needed.
4. Run to see partition, remove Raid flag.
5. In Terminal, mount drive:
mkdir /media/nas
chmod 777 /media/nas
mount -t xfs /dev/sdb4 /media/nas
6. Clear permissions on NAS drive:
cd /media/nas
chmod -R 777 *
7. You should now be able to see the drive in the file finder (mine was "997 GB Volume"). Lots of tips on the net for how to transfer files.

tvmobil free version allows streaming upto 10GB - thats not alot. I've already paid 2 licenses for twonky, one 4 years ago and one just recently as I couldnt find the 1st one.

Please, fresh installation instructions for twonky including removing the current broken version on the MBWE.

You should use tvmobili. It's great. I posted about manually installing it successfully here in the past. It comes with great instructions but be sure to use notepad++ to read them.

Hi Dav-M - Do you know where instructions exist to remove and clean install twonky on MBWE? I'm so frustrated, something has not quite worked and twonky eventually fails.

I want to have the latest version but following the instructions here has not worked for me.

I'm seriously considering another product.

Has anyone got this working for the twonky releases version 8.2 / 8.3 or the latest 8.4 release? I've tried with the upgrade notes but it either become unresponsive the first time or intermittently fails.

MBWE2 works fine for twonky versions up to v8.2.1.

That's a pity as v8.3 onwards has HEVC codec updates as well as samsung tv sub-title updates.

I've tried v8.3 and v8.4 and but it consistently overloads the NAS and eventually crashes.

Anyone who can somehow make it work with 8.4, I and so would many MBWE2 users would be extremely grateful!

R

Done the following:

/etc/init.d/S97twonkserver stop
rm -r /var/twonky/twonkyserver/*
rm -r /var/twonky/TwonkyServer/*

Followed post (…complete-guide-to-upgrade-to-twonky-7-8-version-my-book-worl) to install 7.0.8 version.
- points to note twonky-mss2-special-7.0.8.zip refers to 'Maxtor Shared Storage 2' software release

Goto IP address:9000 and enter license and its working.

I previously installed glrellm to provide realtime hardware statistics and the NAS is finally stable.

I'm looking at the various upgrade options as 8.4 is the latest release.

Its set to -1 and its been running for more than 5 years with any problems.

I plan to remove the full twonky installation and try again, I'll post the progress update later today

i set twonky to scan twice a day (660 min) and it's been running great! what's the longest amount of time you've had twonky stopped for whereby you didn't have an issue?

I dont believe it - its failed again!!

I've done the following to determine if its the WD NAS, my network or the NAS software (twonky):
As there were disconnection issues, IP conflicts could be an issue, so modem and switch restart. This is following reports of 'Connection to 192.168.1.2 port 22: Broken pipe' and 'ping statistics of NAS with 20% packet loss'
NAS IP works fine but when twonky starts, IP disconnection intermittently occur..and therfore eventual loss of SSH connection. Also twonky DLNA service initially appears and then fails at the same time SSH loses connection.

I can only conclude its twonky…So why did it work for me ok this morning? and then eventually fail after 2 hours of non-use…?

I just reviewed the twonky rescan settings and the -1 (not all 9's i mentioned prior) is what used to crash my server a lot. I hear that you are using 90m so that should be better. If not, just increase it in the future.

page 1123...next »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License