NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Recommended Approach for upgrading drive
I have to replace a drive with some early smartctl errors, looking for advice on how to best proceed. I am going to be upgrading the size and also moving volumes round between a couple of drives tha...
So I hope you are the one that can help me figure this out. When I issued DESTROY command on those two data volumes, a running IDrive deamon freaked out and started filling up my / partition really fast for some reason (that I will look more into later). IDrive command line tools is installed by default in /opt. This froze up some functionality with / full.
But the worst part is that I think one of the volume destroy's did not complete its task completely due to the / filesystem filling up halfway through or something, because now when I try to create a new volume with that name, it complains and issues error. I don't know if there is something in the OS configuration somewhere that needs to be completely reset manually to overcome this, or if the actual new drive I'm trying to use was only halfway blessed and needs to be completely wiped in some way to start over or what, but I am hoping you are the one that would know the details of how I can fix this, hopefully not requiring me to factory reset......
But the worst part is that I think one of the volume destroy's did not complete its task completely
What happens if you boot up the system with the original drive in place?
Yea the original drive has already been reformatted and re-volumed and actually restored and is working. I had tried to reboot several times. I had also tried to re-volume this problematic new drive as some other new name which worked fine, but then trying to go back to the first name, complained about couldn't find a device...
But overnight I was restoring the other old drive (that one that used to be called volume2 but is now called volume1...and overnight that drive completely restored everything with rsync and working perfectly with the name volume1. And strangely, this morning I am able to re-volume this new drive as volume2....so somehow the problem seems to have gone away magically.
I don't like it when problems go away magically....that doesn't mean the problem is gone per say... hehe. But at least as of now I appear to have the smart error drive removed, the previous volume2 drive renamed to volume1 and restored, the new drive named as volume2 and in the process of being restored....so with any luck...I'll be good now...
Just as a sidenote, should I have any other concerns about the fact that my / filesystem filled up, presumably by idrive deamon when I destroyed two data drives. Can anything else have gotten corrupted that would give pause to consider doing a factory reset to have completely clean OS? df says my / is 25% full, does that seem like about normal?
I am working with IDrive support now to see if there is a way to install it in someplace other than /opt to avoid this every happening again, their installer doesn't give us the option to specify a path. I could also symlink /opt/IDriveForLinux over to /data/. which would at least work temporarily until I update idrive again probably it would require manual intervention every time. In the past, long time ago, I remember I once had to sym link /var/log over to /data/. because something was logging crazily in there, I don't remember what now.
df says my / is 25% full, does that seem like about normal?
It is normal, but with x86 NAS you should check with btrfs df. Free space is a bit slippery concept with btrfs (and similar file systems), and the df results can be misleading.
Just as a sidenote, should I have any other concerns about the fact that my / filesystem filled up, presumably by idrive deamon when I destroyed two data drives.
It can cause issues, particularly if you try to change the config when the OS is full.
which is what I think happened that was preventing me from re-voluming the new drive as "volume2". I think when I did the "DESTROY" somehow between that time and a few minutes later when I attempted to create a new volume with the same name...the / partition filled up. I can only guess it was the Destroy itself caused IDrive deamon to freak out and fill up its /opt/idrive subdir with stuff...whether or not the destroy completed successfully or not I do not know. It seemed like not since I was having problems, but its magically working, so I dunno.
Do you think this warrant's the time hassles of doing a factory reset to make sure I have clean OS?
btrfs filesystem df shows pretty much the same used data as normal df, actually it shows slightly LESS used space then df... But anyway if 25% seems like reasonably normal usage of / then I won't look for other stuff that may have filled it up, I think pretty much it was IDrive...
sjs@webman:[/plex/media]: df -h / Filesystem Size Used Avail Use% Mounted on /dev/md0 4.0G 911M 2.8G 25% / sjs@webman:[/plex/media]: sudo btrfs filesystem df / Data, single: total=3.58GiB, used=855.91MiB System, DUP: total=8.00MiB, used=16.00KiB Metadata, DUP: total=204.56MiB, used=19.06MiB GlobalReserve, single: total=16.00MiB, used=0.00B sjs@webman:[/plex/media]:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
