quicksilver

Members
  • Content count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

About quicksilver

  • Rank
    Junior Member
  1. crap... migration will not run... back to trying to get into the logs or backing everything up and installing a fresh system.
  2. I completely agree. It's got to be the logs and they likely filled up while the rebuild was occurring. I wish that I had checked /root and /logs before attempting a reboot. At least I WAS logged in. Live and learn. I'm using Nanoboot with DSM 5. I think that it's the latest one before everything changed to XPEnoboot. I'm now extracting files that will be difficult to replace from the Array using an Ubuntu CD and mdadm. Currently it says 13 hours to go... if I have not figured out how to get logged back in to clear /logs by then I'll try a reinstall. That should clear out the logs. I suspect that the login problem is due to the system trying to log my login and failing so it's all a bit of a catch 22. If I could get to a single user instance of DSM it would be easy but I've tried adjusting the kernel line in grub but whatever I changed it to I only ever got a login prompt. Thanks again for the responses.
  3. It's an interesting post but does not say what do do if I cannot get myself logged in. It does say: I think that I'll try a reinstall
  4. Hi Diverge, Thanks for the response. Neither telnet nor ssh, nor the console will let me in using root, admin or any other username/password combination. All were working but now everything says access denied. I'm checking out the Synology post now.
  5. I found another guide here that was somewhat helpful: http://phenomenology/forum/viewtopic.ph ... 262#p32262 I've now tried SystemRescueCD. It also allows me to get to /volume1 but not root. SystemRescueCD puts volume1 in /dev/dm-0 so: mkdir /v1_recovery mount /dev/dm-0 /v1_recovery or.. mount /dev/mapper/vg1000-lv /v1_recovery Provides access to the Synology volume in /v1_recovery Pretty cool actually an makes it really easy to pull the data out. I've also tried: As suggested in the other post but when I try to mount /dev/md0 I get: mount: /dev/md0: can't read superblock I would really love to repair root. trying to find out why it can not read the superblock now. Any/all suggestions welcome. I've also been considering an upgrade to XPEnoboot anyway. Is a reinstall safe with DSM in semi-broken state?
  6. SystemRescueCD put this in /dev/dm-0 mkdir /v1_recovery mount /dev/dm-0 /v1_recovery or.. mount /dev/mapper/vg1000-lv /v1_recovery Provides access to the Synology volume in /v1_recovery Pretty cool actually an makes it really easy to pull the data out but I would really love to repair root. trying to find out why it can not read the superblock now. Any/all suggestions welcome.
  7. Hmmm.. I'm getting an error during mount. mount: /dev/md0: can't read superblock I've been considering an upgrade to XPEnoboot anyway. Is a reinstall safe with DSM in semi-broken state? Thanks Chris
  8. Hello, Interesting tip. Hopefully it will help me out too. While doing a rebuild /root got to 100% full. See here: viewtopic.php?f=2&t=5292 I've managed to get to volume1 but can not get to root. I've tried your suggestion but I do not seem to have /dev/md0. I'm using Ubuntu 14.04 Live CD and will try SystemRescueCD next. Hopefully it will allow me to mount /root. Chris
  9. well... I've managed to get into the volumes by booting to a Ubuntu Live CD, opening a terminal and issuing the following commands: sudo -i apt-get install mdadm lvm2 mdadm –Asf && vgchange -ay or mdadm --assemble --scan Note: specify 'no configuration' for postfix, which seems to be a dependency for mdadm. I can now see my main volume so at the very least I can recover, but this does not get me into the root partition, which is what is full... Perhaps this will prove useful to anyone who needs to access their Synology data from another system but it get me any closer to recovering... Perhaps someone here will know how to get into root.
  10. Hello, Something has happened to by NanoBoot diskstation while replacing a bad disk. I'm getting a message saying: Partition layout is not Diskstation style and sed: couldn't flush /tmpRoot/etc/....: No space left on device ... I get a login prompt and the webgui seems to be there but it will not accept my login. Does anyone here know how to boot DSM/NanoBoot into single user mode so that I can check /root. Thanks
  11. @sancome... Dude.... wow. Great news! I had almost given up hope. Thanks to you and the team for all the hard work and dedication!
  12. Tried the updgade yesterday... everything went perfectly. Bluetooth even worked first time. Long live Nanoboot!
  13. I would love to know this too. It would be nice to have bluetooth audio working with nanoboot. I've not tested yet but see nothing about bluetooth USB support in this thread.
  14. I've got a Synology 1511+ with all the current updates, an N40L with update 2 (but not 4482), an N54L (without update 2 or 4482) and some time to help test and/or provide info from an actual Synology if that will help.
  15. Dadudeondacouch, Where did you add this script and where did you find it? I would like to hide the boot USB / SD card (in my case) too. I've done a quick search in the forums for boot unmount USB but did not see anything. Perhaps this is documented in one of the PC setup guides? Thanks Quick