- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
@Grizzi wrote:
I have tried to do OS reinstall from boot menu, didn't change anything. I wanted to do Factory Default, but not able to as Raidar can't find the device.
Try zeroing one of the disks, and power up the NAS with only that disk installed. That should do a factory install onto that disk.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
Just zeroed out the drive and rebooted, but it didn't resolve the issue (it did do a "Firmware update" during boot).
I am still able to ping the device, but get communication error when i try to access via browser, and Raidar doesn't discover the device.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
I'm not sure why it would matter, but did you try both Ethernet ports on the NAS?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
I actually did, and i have also tried basically all available browser - no change 😐
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
Interestingly enough if i add the main drive from the NAS back to my PC after it has "installed the OS", it is still just 1 partition. Should i not expect a new partition setup with a small 4gig OS Partition? Maybe the OS have not been properly installed for some reason.
The NAS also still boots into Safe mode, so something is definately wrong.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
If the drive was zeroed before insertion, then installed alone and initialized, you should have an OS partition, swap partition, and main partition.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
Also exactly what i would expect, but i didnt have that last time i checked. I will do a check again in a little while, as i am zeroing out all ouf my other drives and got no open SATA slots for the moment 🙂 (i didn't check the drive again after i zeroed it, only before i did the zeroing).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
Just checked the zeroed drive in my PC and it does not have a OS, Swap and Main partition, just 1 large partition. So i guess the OS have not been correctly installed and this could be the reason it is not allowing me to access.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
- should do it no?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
@Grizzi wrote:
Cmd, format /Fs:ntfs /p:1
- should do it no?
No, that formats it.
Perhaps try zeroing it (either with Lifeguard, or Seatools). The Lifeguard "quick zeros" test is sufficient. Then it will have no partitions. Then insert it in to the NAS, and see if the NAS creates any.
Another way to get there is to use the windows disk manager to delete the existing "volume" on the disk.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
Great, that got me a step further. After, correctly...., zeroing the HD, the NAS now did a correct Factory reset and intalled OS 6,10. Raidar is now able to detech the NAS, but i am not quite home yet it would seem.
I still get communication error when trying to access, and it would seem that Raidar is not able to recognize the Model and Serial number.
EEPROM corrupted after USB boot recovery?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Failed update from 4.2.31 to 6.10.0, Boot Menu unavailable, 4.2 USB recovery not working in Win1
Should add the below screenshot to indicate that the Model and Serial is no longer recognizeable. Trying to contact Mods for some help 🙂
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- « Previous
-
- 1
- 2
- Next »