manfriday

When you expanded the volume, did it complete it about 5 secs?

**Limited Test**** Your mileage may vary** I did this as a test a couple of weeks back, I was testing the Samsung HD204UI issue. Installed 4.3 on 1 single drive system, two packages and one userid. Everything was still there after the upgrade to Nanoboot 5.0-4258.

Here we go again. Once again I added a drive and cannot expand the file system. Lo & Behold I have the original LINUX boot USB from the 1st time this happened. My question is: Do I need to go through step 2 - the install of mdadm or do I skip to step 3 and continue? Never mind problem solved

Answering my own question. Expansion of volume shows rate of completion. Consistency Check just shows checking

Feel free to add your experiences regarding removing/adding HDD. I have done this before but do not remember it responding like this. System in Zotac Intel Atom based board running DSM4.3-3810 (still) 4x2TB and 2x3TB, 2 of the 2TB drives are Samsung HD204UI so I decided to swap them out as I am close to capacity plus want to finally upgrade to 5+. Pulled one of the Samsung HDD and replace with 3TB WD green. System gave an expected response to this, DSM goes into rebuild mode and is now Checking Parity Consistency. I see plenty of CPU activity, no HDD activity in widget on screen but I open resource monitor and I/O a plenty is going on. My question is I remember the last time I did this the Checking Parity Consistency showed a percentage completed as it was underway. I am not seeing that count and I started the install about 4 hours prior to this post

managed to upgrade to 4528 but not without minor issues. New IMG file to USB Edit 3 files to change SN, VID & PID shutdown DSM replace USBs and power up open Syno Assistant and find Migrate-able and select follow the bread crumbs on GUI ----upon reboot screen show a line of garbled characters and no boot tried 3 times to Ctl Alt Del, same result power off and on, enter BIOS set USB as boot. DSM starts and Starting Services sits there for 5 mins Install completes. HW= Atom based Zotec board, never had issues with booting before

Don't know if it helps but I also edited debug.lst too

Answering my own question: Installed DSM4-3 3810 on test rig with only 1 HDD Samsung HD204UI. Installed a couple of packages, Antivirus and Download Station Added a user Let install complete. Insert new USB drive and reboot Select install/upgrade from menu. Select PAT file d/loaded previously Installation completed without issue Logon to DSM with Admin attempt to open Storage Manager - get error saying no privilege and kicks me straight out to Logon Screen Log back in with Admin select control panel and straight to update to patch 1 install patch and reboot Logon with Admin Open Storage Manager - no issue Check packages Check userid All is right with DSM

Has anyone upgraded with Samsung drives of the model type- HD204UI? If so, what happens?

thanks for the link! this work around from said link Instructions on how to change this setting (no warranties): - Log in to your NAS with SSH using the root account (not admin, you need root rights) - type "vi /etc/synoinfo.conf" to open the file in VI editor - Using your cursor keys, scroll down to the line that says allow_HD204UI="yes". In my version of the file, it's at line 214, at 64% under # Fixed items (lol) - Press "i" or hit the insert key to enter edit mode of VI editor - Write "#" in front of the line, to comment it: # allow_HD204UI="yes" - Press ESC to enter command mode - Type :wq and hit return to write the file and quit VI editor - Type reboot and hit return to reboot your NAS. After your NAS has rebooted, you should be able to access the web interface again.

Any word on what the issues might be, I have 2 DSM boxes with Samsung in both. Test rig is Seagate?

Any word on what the issues might be, I have 2 DSM boxes with Samsung in both. Test rig is Seagate?

I through a test rig together 1 x160GB drive with 4458 on it, plugged in new USB boot drive and selected upgrade. Magic happened and new system up. My question to those who will know. Can I re use the USB stick to upgrade a DSM 4 3810 system?

Many Thanks!

Just for my clarification: When you say .lst files, you mean .debug, .install & .nano. Did you change the SN, VID & PID to the same values in all files Cheers MF

Just for my clarification: When you say .lst files, you mean .debug, .install & .nano. Did you change the SN, VID & PID to the same values in all files

Many thanks for this. I used XPEnology_VenderFilePatcher_v1001.exe previously but that was during the early daze of getting up and running, have not had to use it subsequently with patches etc. Cheers MF

" edited the .lst files (sn, vid and pid so I have a custom SN and my usb thumb drive doesn't show up in DSM) like the previous installation." Could someone please explain this?

If you want to start slowly with VM maybe Workstation or VMWare Player. I run VM Workstation under Win 7. I have multiple VM machines (not all powered on at once) and DSM. DSM has 640MB allocated and 2 CPU cores. main system is Shuttle XPC with i5-2500 CPU- 16GB and 5x128GB SSD. Each SSD serves a particular function. 3 are used for VM systems. I have an eSATA card and Sans Digital 4xSATA case, 3 drives are for DSM. Map the drives as physical. The DSM is purely to test updates and other assorted tests

little bit scary, the update took less than 4 secs. and worked (VM based system) Also patched Baremetal system - all ok

Seems we should start a thread on the latest & greatest....the chaps down in security are very excited with this one

Check the cpu load on the N44L as you are trying to to view video. I doubt The N45Lhas the horsepower to do video conversion on the fly.

Did exactly that and all is hunky dory Cheers

torrents no longer torrenting

-downloaded update 5 -stop at Update now -run script to execute commands -continue with update 8mins in system available but msg says volumes are outside of operating temps -reboot (stuck at Starting Services in DSM assistant for a long time) System up and volumes not visible -shutdown -come back tomorrow ....tomorrow -restart , all volumes visible, permissions screwed -fix permissions -Done!