• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 3 [4] 5 6 ... 10
 31 
 on: January 26, 2014, 07:31:07 PM 
Started by bad_gui - Last post by birdman
Then I used dd to copy the contents of the partitions to the new drive.
So you copied the file system (which includes its size) into what is now a larger partition.  But the file-system is still the same size.

You need to use resize2fs to expand the file-system on /dev/sda9 now (assuming it is an ext2/ext3/et4 file-system).

Take a look at it's man page, and:

   http://webapp5.rrz.uni-hamburg.de/SuSe-Dokumentation/manual/sles-manuals_en/manual/biuymaa.html

NOTE that you have already enlarged the partition - you just want to grow the file-system to use all of the space.

Also note that all of these things warn about backing up before you do anything.

 32 
 on: January 26, 2014, 08:44:01 AM 
Started by bad_gui - Last post by bad_gui
I have Guruplug server booting from an external SATA drive.

A while ago I upgraded the drive from 1TB to 2TB by transferring both drives to a desktop computer.  First
I created a new partition table on the 2TB drive with everything the same except /dev/sda9 which I set to
use the ending cylinder.  Then I used dd to copy the contents of the partitions to the new drive.

Wheezy boots from the new drive and everything seems OK except when I use df -h I see that /dev/sda9
is much smaller than it is supposed to be:

Code:
# df -H
Filesystem                                              Size  Used Avail Use% Mounted on
rootfs                                                  272M  153M  105M  60% /
udev                                                     11M     0   11M   0% /dev
tmpfs                                                    53M  476k   53M   1% /run
/dev/disk/by-uuid/525184d1-eb77     272M  153M  105M  60% /
tmpfs                                                   5.3M     0  5.3M   0% /run/lock
tmpfs                                                   415M     0  415M   0% /run/shm
/dev/sda1                                               239M   39M  188M  17% /boot
/dev/sda9                                               975G   34G  892G   4% /home
/dev/sda8                                               386M   11M  356M   3% /tmp
/dev/sda5                                               5.0G  1.2G  3.6G  24% /usr
/dev/sda6                                               3.0G  652M  2.2G  24% /var


But /dev/sda9 should have an extra 1TB according to this

Code:
# sfdisk -l -uM
Disk /dev/sda: 243201 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   End    MiB    #blocks   Id  System
/dev/sda1   *     1    243    243     248832   83  Linux
/dev/sda2       244    510    267     273408   83  Linux
/dev/sda3       511  1907728  1907218  1952991232    5  Extended
/dev/sda4         0      -      0          0    0  Empty
/dev/sda5       512   5283   4772    4886528   83  Linux
/dev/sda6      5285   8141   2857    2925568   83  Linux
/dev/sda7      8143   9617   1475    1510400   82  Linux swap / Solaris
/dev/sda8      9619   9998    380     389120   83  Linux
/dev/sda9     10000  1907728  1897729  1943274496   83  Linux


Am I understanding this correctly?  The /dev/sda9 partition is the correct size but the
filesystem can't see the extra 1 TB?

The other problem I had was that the swap partition kept the UUID of the old drive rather
than the new drive.  I had all kinds of weird memory problems until I saw the error in
/etc/fstab.

 33 
 on: January 18, 2014, 03:14:32 AM 
Started by odoll - Last post by apemberton
Yes, I already boot from an ext2 partition which is named as /boot in /etc/fstab. However wouldn't it be nice to have a single ext4 partition as I have in my Cubox's as the u-boot has these commands built in. I'm not sure now if I grabbed a binary or compiled the u-boot source for the cubox's. I have tried compiling a u-boot 2013-10 for sheevaplug but the patches and sources didn't work for me. I added the ext4 commands in the config but that was pointless.

 34 
 on: January 17, 2014, 06:25:57 PM 
Started by odoll - Last post by birdman
However, since all(?) of the files you need will be under /boot, you could just make an ext2 file-system  for that and use the ext2load.
Given that it will be fairly static you wont see any difference c.f. ext4.

 35 
 on: January 17, 2014, 01:30:11 PM 
Started by odoll - Last post by odoll
No, I don't think so:
Code:
U-Boot 2013.10 (Oct 21 2013 - 21:06:56)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0
Marvell>> version

U-Boot 2013.10 (Oct 21 2013 - 21:06:56)
Marvell-Sheevaplug - eSATA - SD/MMC
gcc (Debian 4.8.1-9) 4.8.1
GNU ld (GNU Binutils for Debian) 2.23.52.20130727

Marvell>> help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
chpart  - change active partition
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
diskboot- boot from IDE device
echo    - echo args to console
editenv - edit environment variable
env     - environment handling commands
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fsinfo  - print information about filesystems
fsload  - load binary file from a filesystem image
go      - start application at address 'addr'
help    - print command description/usage
ide     - IDE sub-system
iminfo  - print header information for application image
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
ls      - list files in a directory (default /)
md      - memory display
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub-system
mtdparts- define flash/nand partitions
mw      - memory write (fill)
nand    - NAND sub-system
nboot   - boot from NAND device
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv  - set environment variables
sleep   - delay execution for some time
source  - run script from memory
tftpboot- boot image via network using TFTP protocol
ubi     - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
usb     - USB sub-system
usbboot - boot from USB device
version - print monitor, compiler and linker version

 36 
 on: January 16, 2014, 10:34:47 AM 
Started by odoll - Last post by apemberton
Thanks for the info. If you have the info, can this version boot from an EXT4 partition (commands 'ext4load' and 'ext4ls') as this could simplify the SDHC/disk partitioning?

 37 
 on: January 16, 2014, 06:56:31 AM 
Started by odoll - Last post by odoll
I think I haven't seen it been mentioned somewhere else in this forum, yet so let me make the following hint:

I recently noticed that Michael updated his u-boot binaries repository at http://people.debian.org/~tbm/u-boot/ with a newer version which is called 2013.10-2 from 02-Nov-2013.

I upgraded both my SheevaPlugs (prod and spare) a few days ago and I noticed no issues since then. Even with having the system on the 4 GB MicroSD, which, when plugged in instead of another 4 GB 'big' SD, usually now and then loses the USB attached 2 TB HDD (http://www.plugcomputer.org/plugforum/index.php?topic=6113.0).

 38 
 on: December 24, 2013, 03:29:28 AM 
Started by mgillespie - Last post by mgillespie
Link is the same as usual (so save you scrolling back to page 1).


http://www.mediafire.com/sheeva-with-debian


 39 
 on: December 24, 2013, 03:21:25 AM 
Started by mgillespie - Last post by mgillespie
Updated the script and prebuilt images today with the latest Debian Wheezy (7.3).   Also posted a complete ready to go ESIA application image with Linux 3.0.60/Wheezy7.3

I would recommend running this with DenX U-Boot 2013.10-rc1-00034-g2b26201
(not created/compiled by me, but I have put it in the same mediafire directory, incase it disappears from the web in the future)

Tested it all out on my original Globalscale Sheevaplug, which aside from a powersupply replacement has turned out to be a very trusty and reliable bit of kit.

Once loaded, don't forget to change the password, create new ssl keys, flash the latest sheeva kernel using the update script:

http://www.xilka.com/sheeva/kernel/UPDATE-KERNEL.sh

and pick up the latest Debian package updates with an apt-get update.

Enjoy.

 40 
 on: December 23, 2013, 05:45:59 PM 
Started by UnaClocker - Last post by UnaClocker
Heya guys.. It's been a good 4 years with my SheevaPlug. I got my SheevaPlug for Christmas 2009. It's been running 24/7 ever since, as my fileserver (NAS), webserver, and firewall. I used the same 8gb SD card the whole time, though I managed to fill it all the way up a year or two back and have been kind of cramped ever since.
I just wanted to thank everyone here for the great help. Especially cbxbiker61 for continuing to release pre-compiled kernels for the unit, I upgraded several times along the way and it was always a relief to have a kernel that Just Worked. Smiley
In the end, I'm retiring it because I wanted to play with something new. My new server is a budget PC running FreeBSD.
If anyone would like my Sheeva, let me know.

Pages: 1 2 3 [4] 5 6 ... 10