NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
jackerhack
Jan 20, 2014Aspirant
Recovering from apt-get dist-upgrade
Hey all, my first time here. I've been a happy ReadyNAS user for close to a year. I have a Duo v2 at home and an NV+ v2 at work, all loaded with 3 TB drives. Last week I was trying to setup my s...
jackerhack
Jan 21, 2014Aspirant
I took the disks to work today and put them in a desktop computer. Both show up as GPT drives with two partitions each, with both partitions of type linux_raid_member. Which is curious because I had asked the Duo v2 to set them up as JBOD, so either it uses RAID even for JBOD, or it messed up the disks afterwards. (I had no idea there was such a thing as "JBOD" before getting the Duo v2.) FWIW, I can't read these disks from my desktop. The partitions are not recognised as ext2/3/4 or btrfs. The Duo v2's log include these discouraging lines:
I had a power failure shortly after the dist-upgrade, necessitating a shutdown. The PST timestamps are from the OS reinstall. I appreciate the advice on not messing with embedded devices, but I've been using Debian for 15 years, including on embedded devices going back to the Linksys NSLU2 (my first home NAS), and this is the first time an apt-get dist-upgrade resulted in a filesystem becoming inaccessible. Suffice to say it caught me unprepared, and the power failure and UPS shutdown left me with little time to do anything about it.
I do have a backup of my data, but it's offsite, so getting ~1 TB of data back in sync is going to be a bit of a pain. I'll do it if the Duo v2 has already wiped my data (as it appears).
I will call Netgear Support in the morning, but I will be surprised if they actually help. I've rarely had a good experience calling technical support at any company.
What I mean is what you quoted: OS installations can go bad (dist-upgrade messed up, etc), but at least the filesystem remains functional when accessed from a working OS.
Tue Jan 14 19:33:42 PST 2014 Volume scan failed to run properly.
Tue Jan 14 19:15:27 PST 2014 System is up.
Tue Jan 14 19:15:16 PST 2014 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume.
media
transmission
backup
Wed Jan 15 08:43:40 PST 2014 Volume scan failed to run properly.
Wed Jan 15 00:42:58 PST 2014 265: ERROR: mysql failed when creating mysql user. (error=1)
Wed Jan 15 00:41:57 PST 2014 Volume scan failed to run properly.
Wed Jan 15 04:44:00 IST 2014 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 2]
Wed Jan 15 04:44:00 IST 2014 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1]
Tue Jan 14 13:50:30 IST 2014 UPS is shutting down system.
Tue Jan 14 13:50:28 IST 2014 UPS battery is low; system will shutdown soon.
Tue Jan 14 13:39:37 IST 2014 UPS is on battery power.
Mon Jan 13 10:33:21 IST 2014 System is up.
I had a power failure shortly after the dist-upgrade, necessitating a shutdown. The PST timestamps are from the OS reinstall. I appreciate the advice on not messing with embedded devices, but I've been using Debian for 15 years, including on embedded devices going back to the Linksys NSLU2 (my first home NAS), and this is the first time an apt-get dist-upgrade resulted in a filesystem becoming inaccessible. Suffice to say it caught me unprepared, and the power failure and UPS shutdown left me with little time to do anything about it.
I do have a backup of my data, but it's offsite, so getting ~1 TB of data back in sync is going to be a bit of a pain. I'll do it if the Duo v2 has already wiped my data (as it appears).
I will call Netgear Support in the morning, but I will be surprised if they actually help. I've rarely had a good experience calling technical support at any company.
fastfwd wrote:
jackerhack wrote: Also, software installations go bad. It's in the nature of software.
I have no idea what that means.
What I mean is what you quoted: OS installations can go bad (dist-upgrade messed up, etc), but at least the filesystem remains functional when accessed from a working OS.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!