![]() ![]() ![]() Luckily enough, we won't need anything fancy to perform our task: we're just going to make good use of How can we do that? If you take a look around you'll see that the web is awfully short of a quick and effective tutorial for this: that's why I eventually chose to write my own guide: here it is! It would be great to extend that puny 6.8GB partition and make it become a 106.8GB drive. a 6.8GB drive, used by the Linux OS and all its installed packages. ![]() This screen can be obtained by running cfdisk from the terminal and shows the following: For an updated approach that allows to resize/extend any Linux VM using a more secure technique and without the need of a reboot, we strongly recommend to read this post instead.Įxpanding disk partitions to use all the available (unallocated) disk space is a common issue among Linux Administrators, expecially when working in a VMware-based Cloud environment: deploying a Linux VM from an existing template will often lead to disk partitions smaller than the disk space allocated during the VM configuration phase. I appreciate any help you can offer and the heads up on support replacing the drive helps some other folks out.UPDATE: this post was originally published in 2017 and has noot been updated ever since. I could try plugging the MBWE HD into the new MBL HD, but getting those cases open is no small task. Believe it or not support suggest I remove the HD from the case to try and get my information from it. They have a credit card hold on my, so I just have to mail them the old one. So I have a 30 day warranty, and just have to mail them back the old one during that time. After much troubleshooting, they said I was eligable for a free replacement since I'd never registered the product until that call. If not, any suggestions on what I should do for retreiving my files? I feel like I'm close, but may not be technical enough to figure out the last step.Īs a FYI, I called support (first time I'd called them in 4 years of owning the HD). Does that sound like something that might work. That being said I'm thinking my next option is to copy the MBWE image to another external HD, and seeing if I can access the files then. It could be I'm not overly technical, so I may not know what I'm doing… I've run a few of the suggested softwares like ext2fs, but that hasn't given me access. I can see the harddrive, but I can't access it. I have it plugged in via SATA to USB on my Mac. I've finally given up and removed the hard drive. After the firmware update and the error, I was not able to access any of the files. Also I downgraded the firmware to version 02.11.09-053 but no luck. I have already tried to remove "max protocol = SMB2" line from nf, restarting the unit, to downgrade samba protocol to v1. Jun 6 06:59:48 hd smbd: dumping core in /var/log/samba/cores/smbd Jun 6 06:59:48 hd smbd: BACKTRACE: 14 stack frames: Jun 6 06:59:48 hd smbd: PANIC (pid 18866): failed to drain pending bytes Here´s the wd mybook live log output when the camera attempts to send video: If I use the ftp server of the wd mybook live, it works flawlessly. ![]() When the vivotek tries to record to samba server, i file with 0kb (zero) is recorded to the choosen folder. Previously i had a WD Mybook World which would work with all three cameras without issues. Just to let you know, I have three cameras, two can record without issues, the vivotek can´t. Both the camera and the mybook have the latest firmware. Dear friends, I have a Vivotek IP7330 camera and i´m having issues while trying to record video to my wd my book live. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |