techweenie
-
Posts
8 -
Joined
-
Last visited
techweenie's Achievements
Newbie (1/7)
1
Reputation
-
Doesn't the ATA port numbering in software begin at 1, while it begins at 0 on the board? Though it is possible that the controller provides 4 ports, and a separate controller is used for eSATA. I doubt that those messages are related to the reason why it won't boot further. Can you provide full logs from start? The ata denomination is really not the issue here. As I have already said, there is nothing else in the consol output, else I would have provided it. Those are the only two lines that appear once the kernel start decompressing. Nothing else shows. I've left it for 10 min see if anything else would show, but nothing there. Recalling a bug I encountered a while back with a certain motherboard, try resetting the BIOS to defaults and don't change anything except ensuring ahci is active. If that still doesn't work, remove the cd drive entirely or disable in BIOS if that option is available.
-
6.1 Update 2 is out. Installed without issue for me using 3615 loader.
-
This thread needs be broken into one for each loader version. Each one has its own issues and following along is just confusing as hell. Who's the moderator around here?
-
I have this LSI controller. The new loader is able to load but after DSM install, it is not responsive to any power commands via DSM web GUI, eg. Shutdown or restart. Anyone else experiencing power issues? I am also using the 9211-8i and it works flawlessly with both of the latest loaders. The disk order makes no sense, but I can live with that. Shutdown / reboot works fine as well.
-
I have an HP ProLiant ML350 G6 that I just started using for XPEnology. I did a fresh install of 6.1 followed by update 1 using the 3617xs loader. It has never had 6.02 installed nor have I ever used the 3615xs loader. I was just on it trying to install Synology Office when the process failed and I got a message to check network connection. It was still responding to pings, but I couldn't access the web interface anymore. Now all I get is the page not found message. Since this is a new build I don't have any data on there yet, plus one of my disks has 2120 reallocated sectors that weren't reported by the previous raid controller.
-
The VM didn't function enough to get SSH access. I wound up deleting the original virtual disk from the configuration and adding a new blank disk, and also removed the passthrough SATA controller. That allowed me to install a fresh copy of 6.0.2. I then reconnected the passthrough controller. It still booted up fully but claimed the system partition on all the passthrough disks was corrupt and offered to repair them. That was successful, and none of my data was lost. I did lose all of my apps and configurations, but that is not going to kill me.
-
Out of desperation to try and solve a problem on a real Diskstation (different discussion for a different day), I updated my ESXi version to the 6.1 beta. As you probably guessed, it doesn't work now. It shows up in the Synology Assistant as recoverable, but that doesn't do anything. The web interface says errors were detected on the drives so they were shut down, and the SATA ports were disabled as well. Any chance I can recover from this? I don't have critical data on there, but if I can avoid losing it I'd like to.
-
For those of you who used the original ESXi OVF and updated to Update 9, I have a pretty easy method to fix it. 1. Download the 1.01 loader and unzip everything. 2. Enable SSH to your ESXi host if you haven't already. 3. Use WinSCP (or equivalent) to copy the synoboot.img and synoboot.vmdk files to the VM folder on ESXi. 4. Using vSphere Web Client, edit the VM configuration to remove the existing SATA disk, then add a new disk using the existing synoboot.vmdk. (if anyone knows an alternate method for those without vCenter, please share) 5. Set the controller type to SATA just like the original was. 6. If necessary, modify the boot order to match the new disk That's all I had to do to get mine working again. I did have to reset the static IP, but that's it.
