manfriday
-
Posts
208 -
Joined
-
Last visited
-
Days Won
3
Posts posted by manfriday
-
-
Same issue here on VM based DSM. it is running fine now but I am holding off on upgrading bare metal DSM. Did you D/L update from sinology or bromolow from elsewhere?
...time rolls on....
updated DSM bare metal system.
D/L from sinology,
run script,
apply patch.
Wait a painfully long time (almost another 10mins beyond the 10min countdown circle of hope) for system to come ready, was almost going to do hard off but could hear disk activity so let it go.
Eventually could connect, all volumes and data alive and well.
-
Regarding your restart after update process. Did you shutdown in an orderly manner or just pull the cable while DSM was up?
Regarding the ping update.synology.com. You can't ping just it or any IP from ANY device inside your network?
Did you open DSM to outside access aka. quick connect/easy internet etc prior to update?
-
Unusual update 4 outcome.
Logged into DSM and noticed update available. Without too much thought I started my sandbox DSM_VM and followed what I thought was correct process.
D/L update (directly from Syno) and wait...
Run script to setup flashupdt
proceed with update.
Initial Success, then notification msg says all volumes unloaded.
I see no volumes.Applied liberal use of profanity
Reboot.
All volumes back but packages missing, data missing and volumes go into build mode.
I dare say it was the Syno D/L that cooked me. Had i used bromolow file this would not have happened.
Anyone else with this?
DSM 5.0 4493 on VM Workstaion 10. 3 RAW mapped HDD.
-
BTW I also have a VM Workstation 10 (DSM 5.0 4493) instance with 2 raw mapped drives inside a SANs Digital 4 rack box. No exactly the same as what you are proposing but the port multiplier works as pass through via Win7 Host and Workstation guests. The port multiplier card came with the SANs Digital box, SIL3xxx or thereabouts.
-
IO Crest 2 Port SATA III PCI-Express x1 Card (SY-PEX40039)
ASM1061 Chipset (Asmedia 1061 SATA Host Controller)
Supports Hot Plug and Hot Swap
Supports Communication Speeds of 6.0Gbps, 3.0Gbps, and 1.5Gbps
Supports 2 Ports Serial ATA, Native Command Queue (NCQ), Port Multiplier
Works with SSDs
*** I do not use this with SSD or the port multiplier ***
used only to add 2 extra SATA ports as mobo has only 4 on board SATA @DSM5 4493-3
I also use an SiL based card, 4ports in a second DSM 4.3
-
I have multi-port cards working but not port mulitplier, had tried it some time ago @4.3 but same results as we others these pages. You see one drive only. Must be more than a handful of users with SANS DIGITAL 4 slotters all wanting this to work.
-
Check Help in DSM GUI - look for change RAID type
-
...and welcome to Linux school, class is in, take your time, no one fails this class
-
If you chose you use RAID1 or SHR (default) protection during setup and have only 2 HDD you will see the capacity equal to one drive. The second drive and capacity of that drive is used as protection against the primary drive failing. As you add more capacity (HDD) your capacity will increase e.g with SHR protection 2x3TB HHD yields ~3TB usable capacity, 3x3TB yields ~6TB, 4x3TB yields ~9TB etc. If you opt for no protection during setup or disk addition you will have full capacity but no protection against HDD failure.
Good luck storming the castle
MF
-
Hands up those who work in IT? Keep your hand up if you have pinged your Network guru guys and inquired about opening ports on your one and only retail ready router. Keep your hands up if after they made you a VISIO, drew a picture on a white board or explained in some detail what happens when you do that? Keep your hands up if you ignored every piece of advice and said, "this will not happen to me"
Sorry but it's been a tough day at the coal face
MF
-
Hello I am getting error when I tried sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 via ssh error " -sh: can't create /autoupd@te.info1: Permission denied
" Please help. thanks
Loggining in as Root?
-
The SSH and task methods are not working for me.
My current version is DSM 5.0-4493 Update 2
I have downloaded DSM 5.0-4493 Update 3, to my local PC
I launch the manual update through the DSM Web GUI... "Transferring data...".
I stop at the "Do you want to continue" dialog box
SSH, log in as root, type in:
sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1 mv /autoupd@te.info1 /autoupd@te.info
Hit enter in SSH, and this is displayed:
...directory issue ?
In any case, going forward with the update fails with a temp directory does not exist message... Help...
...Have you tried building a task via DSM GUI and using the command string inside the task?
I had a couple of failed attempts sometime back and discovered the error to be mine because of a sequencing issue. The task removed the SSH requirement
-
Network bandwidth and connectivity?
I had issues sending 1080p through a DLink DIR-655 wireless router. MKV would play but stop within the first few minutes of play. 720P played ok.
CPU load was always within acceptable loads. Ditched router for something with more horsepower problem solved. I have Samsung Smart TV, WD TV live x 2. One wired, one wireless GigE wired network. Atom based DSM 4493-3
-
Your only options are to replace the HDDs with lager units (one at a time) or drop the RAID 1/SHR protection to use the capacity of the protecting disk. I would opt for option 1.
-
Hmmm... bit of a problem but try this.....
...wonder what this indicates for any kind of future development efforts?
-
Not sure where to post this question/comment due to land fill design of this forum but here it is:
Followed the very clear instructions at http://www.xpenology.nl/vmware-workstation/ <-excellent work, thank you
Created my VM and now would like to add storage/HDD.
What is the "best practice" or at least what have other users preferred for allocating more capacity?
Raw Disk mapping or other options? I have limited space in my VM Host rig.
Cheers
MF
**Never mind** went with Ready, Shoot Aim....RAW disks mapped and in use
-
Built a script some time ago to cut out the SSH step. There are step by step instructions somewhere around here. Basically built it through the GUI by creating a task and C&P the commands that we have all seen. Anyway, from Update & Restore select Download and wait for D/L to complete. Run script/task. Hit Update and wait, the system will reboot.
-
Disclaimer:
I'm not responsible if you screw up by following these steps.
Always do a complete backup before attempting anything like this.
Why does my volume not expand?
Even after several tried I'm not sure what the reason is that DSM does not expand. The only thing I can confirm is that there is NO 16TB limit, even though I thought so in the beginning. The log files either show that you are out of reserved GDT blocks or that the volume has expanded successfully even though it didn't. DSM is basically just using LVM and mdadm so it's not a problem to expand it by hand in a safe way. Most guides on the web tell you to do this through SSH, but since most people struggle just to unmount the volume, here's a much easier way.
How to expand your volume
These guidelines are tested with SHR2 and a single volume only, no disk group! SHR should be fine too, but normal raid-setups do not use lvm as far as I know. Even thought the concept would be the same, the commands would differ (instead of expanding though lvm you would probably just use mdadm).
Anyway....
1. The first step is to download Ubuntu Desktop 64-bits and boot it up. This way we do not have to try to stop all the Synology services running. How this is done depends on your hardware and if you are running DSM on a physical or virtual machine. Basically just download the ISO and either burn it to a CD or make a bootable USB-drive from it. Then insert and boot it on the machine running DSM.
http://www.ubuntu.com/download/desktop
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows
2. Once booted up (try without installing), we need to install mdadm as it's not included by default. Just accept the default values, they don't matter in this case:
sudo apt-get install mdadm
3. Now we need to assemble the raid. Once done it should tell you that the raid is assembled.
sudo mdadm --assemble --scan
4. We now need to get lvm to load the volume. Run the following commands in the right sequence. What it does is: load necessary module, scan for lvm volumes, activate volume and find local volume:
sudo modprobe dm-mod
sudo vgscan
sudo vgchange -ay vg1000
sudo lvs
5. Now we can run the file system check. This may take some time:
sudo fsck.ext4 -fvp /dev/vg1000/lv
6. Now we expand the volume. This may take a while! You may open a new terminal window and use "top" in order to see what's going on:
sudo resize2fs -fpF /dev/vg1000/lv
7. Just reboot the system, remove the CD and boot into DSM. It should be all green, no crashed volume!
Did this guide help you out? Please consider a small donation.
Despite being a complete Linux noob (had to do some figuring out along the way) this procedure worked perfectly. Many thanks for your help. It's not good to be thirsty
Cheers
MF
-
Should this guide be moved into the "How To" section?
-
All quiet on the eastern front....nothing to report here
-
Many thanks for the input.
To be clear to those of us (me) who are not reading between the lines.
1. The first step is to download Ubuntu Desktop 64-bits and boot it up. This way we do not have to try to stop all the Synology services running.
I assume I am looking for an Ubuntu ISO image to burn to CD. From there I boot from the CD on the Syno box that contains the non expanding disk capacity?
Any particular ver of Ubuntu (I would assume 14x)
Cheers
MF
http://www.pendrivelinux.com/put-ubuntu ... g-windows/
Starting BU process now but expect a couple of days of work as there is 8TB to move
-
16TB Volume(not disk group) limit. Disk Groups limit = size of wallet.
Issue on Trantor 4-3-3810 system is a bad file system stopping expansion. While the various "how to's" point in the right direction I can not correct FS problem and therefore can not expand the volume.
A little more light reading
after a hard crash of server.
-Plugged in monitor.
-Reboot
-login to DSM
-Storage Manager > Expand volume and watch monitor traffic
-Expand fails and last line on console "no reserved gdt blocks can't resize"
https://bugs.launchpad.net/ubuntu/+sour ... bug/656115
This outside my pay grade so it's a clean install for from here
-
-
this last 2 weeks I replaced 2x2TB with 2x3TB and had similar issue regarding expansion of capacity. Volumes were all hot swapped. As soon as I rebooted the option to expand appeared.
I start the expansion and it stops straight away. Running 4.3-3810. with SHR1
Followed instructions from further up the page but no joy.
Tried umount /volume1 but get a device busy or in use, cannot see what has a hold of the volume, all shares are shutdown, no PC's accessing shares. Next this is to power off any media devices or smart TV's attached to SHARES via media server
question as this does have something to do with the nanoboot
in Archives
Posted
It's nice to know it's possible but I am looking for insight on why. Correct me when I'm wrong but the USB stick ticks the boxes of, next to nothing in heat generation & power draw, no moving parts to wear out, no noise, don't have to give a slot in the case. Giving up capacity on a HDD for a handful of MB for a few minutes of boot time. Feel free to add or subtract from the list.
cheers
MF