JP76
-
Posts
24 -
Joined
-
Last visited
Posts posted by JP76
-
-
So I was finally able to run these commands but no volume was created. Do I need to create a new volume to access my files or would I delete the files if I create a new volume?
-
Hi.
Can you please tell me how you run the e2fsck command? When following the instructions and try to run e2fsck -nvf -C 0 /dev/vg1000/lv I get an error message that dir /dev/sda1 doesn't exist
-
So I was able to downgrade from DSM 6.0.2-8451 to DSM 5.2-5644 Update 5 but volumes refuse to mount (Abnormality detected on [NAS Name]. All volumes have been unmounted). Moved thread to here:
-
@ingen300 - please you are trolling! We know that DSM 6 is not compatible with the current Xpenoboot!
It was automatic updated!
The only thing that worked was:
1. Boot into Install Upgrade mode
2. Run SynoAssyst in order to find IP
3. Open browser to Install Wizard
4. Choose Clean install (delete settings, preserve files)
5. Install DSM_5.2-5644
6. Reboot and login with Admin and blank password
7. Make manual upgrade (one by one), from Update-1, Update-2, Update-3, Update-5 (there is no Update-4).
The files for upgrade are here.
8. Reconfigure the nas... (two hours).
I took all these steps but when I login I get the error "Abnormality detected on (NAS Name). All volumes have been unmounted." Help
-
The problem is that you didn't follow the correct update path. Because you have tried to upgrade from within the DSM update process your system is in an unknown state. I'm not going to test it to see what happens and I doubt anyone would spend time investigating an edge case that's caused by user error.
You have few options:
1: Try and force an update with your machine in it's current state 6.x to 6.x using Jun's loader. Edit the grub to select the default boot option or press the arrow keys to interrupt the boot process. Personally I wouldn't spend too much time on this option as it's an unknown.
2: Roll back to the most recent Xpenology version and recover to a known good position and then follow the tutorial for installing 6.x using the migration process.
3: If your data is safely backed up and verified use a linux boot disk and trash the partitions on the drives. Once your drives are cleared of Synology partition data follow the tutorial and rebuild from scratch. If I were in your situation that's what I would opt for. In fact I wasn't in your situation and after testing my migrated build I decided to do a fresh install (bit of ocd I wanted a clean build rather than gaining any other benefit).
Make sure you use the AMD installation option from the grub, if you miss that step you will be pissing in the wind.
You're going to have to bite the bullet and pull the trigger on one of those choices imho. I'm crap with linux though so maybe someone has better ideas involving some linux magic?
Thanks, any clue if I can rollback to 5.2.4 and how to do it?
-
Hang on. So you originally booted from the DSM 6 key, it was found on the network and you updated it to DSM6 via the web interface. Now after the install, you can no longer find it on the network? Is it still booting with the AMD option?+
And yes, you should be able to mount the disks under linux and recover. TI have seen a post somewhere and sometime on how to use mdadm to do so, but I can't remember where....... sorry
Not exactly. I originally booted from a DSM 5 key. I've updated to DSM 6 from the control panel using my browser. There was a migration step that allowed you to delete some data (according to it) but retain my files. After that 2 things happen:
1. If I use a DSM 5 key I'm able to boot and log on to the control panel but it says no volumes exist. I assigned a static IP address though which still allows me to access the control panel.
2. If I use the DSM 6 key the NIC it doesn't get any IP.
And I believe that's where your problem lies. You used Xpenoboot 5.2 to update to DSM 6.0.2. That's a no no in my opinion. Xpenoboot was never meant to be used with DSM 6. Both loaders use different ways to hack different DSM versions.
Reboot your router. Make sure MAC, s/n, and pid/vid are set correctly. Then try reinstalling.
MAC, s/n, pid/vis settings are correct. What do you mean with reinstalling?
By the way, when booting the NL54 latest showed status is that it's booting the kernel.
I just want to access my files so I would also consider downgrading DSM 6.0.2 to XPenoboot 5.2 if possible
-
Did you try http://10.10.10.3:5000 ?
If you use http://10.10.10.3 it should redirect to the set-up page if you're doing an install or the web page if DSM is set-up and web hosting is configured.
https://10.10.10.3:5001 if you had set-up the ssl and migrated that port should still be working.
Edit: Those port numbers are only relevant if you clean install or migrate and didn't change the default port values in the old installation.
Yes same issue
-
billat29 thanks! I forgot the N54Ls came with AMDs and not Intel
So device is now showing up on synology assistant with the static IP address, status is set as ready but when I try to connect to it I get an error on the browser (http://10.10.10.3:5000/?timestamp=1480540354) detailing that 10.10.10.3 ^(the static IP I've set) refused to connect. -
Hang on. So you originally booted from the DSM 6 key, it was found on the network and you updated it to DSM6 via the web interface. Now after the install, you can no longer find it on the network? Is it still booting with the AMD option?+
And yes, you should be able to mount the disks under linux and recover. TI have seen a post somewhere and sometime on how to use mdadm to do so, but I can't remember where....... sorry
Not exactly. I originally booted from a DSM 5 key. I've updated to DSM 6 from the control panel using my browser. There was a migration step that allowed you to delete some data (according to it) but retain my files. After that 2 things happen:
1. If I use a DSM 5 key I'm able to boot and log on to the control panel but it says no volumes exist. I assigned a static IP address though which still allows me to access the control panel.
2. If I use the DSM 6 key the NIC it doesn't get any IP.
-
Have you checked your router to see if it gets an IP from the DHCP service?
Thanks for your reply. No, it's not detected on the network. When I use the USB with DSM 5 I can access the NAS but not with the DSM 6 USB key (it doesn't get an IP so likely a driver issue). ~Is there anyway I can access the files, copy them elsewhere and reconstruct the RAID?
-
I changed the loader as detailed and used DS3615xs 6.0.2 Jun's Mod V1.01 Changed the config file, all that stuff and booted it on my N54L. No errors (last message is that the interface is running) but I'm unable to find the NAS using the Synology Assistant
-
´*bump* for help
-
So I've updated my N54L to DSM 6.0.2-8451, completed the install and now I have no volumes and when I try to create a new one it says it will erase all my files... Any way I can restore the files I had?
PS - I did the upgrade through the DSM interface and the option I've picked said it would erase data but not the files...
Thanks,
J.
-
Nevermind, I was able to delete the IPs from the list using my laptop, seems this option is not available from the Ipad client.
-
It worked! Thank you so much
Connected from my Ipad and I was able to access the console. any idea on how to re-enable the access from those other banned IP addresses? I see them on my Ipad on the block list but can't find any option to remove them from there, except if I disable the feature.
-
Didn't worked either using my other user...
One thing I just detected: when I try to access my XPEnology shares from windows, system asks me for a user and password. I use "admin" + the password I recalled and I can access the shares. However, I can't login to DiskStation using these credentials...
Anyway I can do a fresh install and keep the data on my disks? Lucky enough, I have all the data on another Netgear NAS...
-
Hi everyone.
Seems I forgot my admin password and I've been unsuccessful remembering it. I've added the parameter “resetuser=admin“ on boot, as detailed in the tutorial video, but after prompt appears, I try to insert a blank password for user admin and I still get the message that it's invalid. Help!
Current specs:
HP N54L
DSM 5.2-5592 update 4
Thanks,
JP
-
That's because NTFS isn't supported. Use FAT32 or EXT3/4 instead.
Hi.
If that's the case how come my 2TB HDD is detected (as it's also formatted using NTFS)? Is there a capacity related constraint when it comes to choose which file system to format the external HDD with)
Thanks,
JP
-
Hi.
I've connected my WD Elements 3Tb disk to my N54L to copy some files to the NAS. System detects the disk but the file system type shows as unsupported, although it's formated in NTFS... My WD Passport 2TB works fine... Help?
Thanks,
JP
-
Nevermind, the BIOS settings weren't correct...
-
Nevermind, seems I was to dumb to use the screws to properly fit the disks in the plastic frames. Still, seems I'm unable to see the 5th HDD. I did upgrade the firmware and connected it internally. Any ideas?
-
So I took the disks out and tried to fit them again in the server. Now I see a disk 2. Has someone else have any trouble of this sort?
-
Hi.
So this is my first attempt into XPEnology. Got myself a NL54 and 5x2Tb disks from Western Digital (removed them from my netgear NAS). I've installed 4 of them into the 4 slots and connected the 5th one to the internal SATA port. Installed DSM 5.2-5592 and update it up to update 4. Issue is that when I take a look into the available disks in Storage Manager I just see one (Disk 4). Not sure what's going on, but no indication that the other ones are also installed. Help?
Thanks,
J.
Boot from external E-Sata port
in Archives
Posted
Hi.
I was wondering if there's anyway I can install DSM in an external HDD and boot from it? Whenever I connect an external HDD to my N54L's external ESATA port to boot it just doesn't show up (although it works flawlessly if I use an USB port)...