Upgrade GoFlex Net to Debian 8.0 (jessie) stable

I just saw that Debian 8.0 stable was released.

I've a GoFlex Net with

user@goflex:~$ uname -a
Linux goflex 3.17.0-kirkwood-tld-1 #4 PREEMPT Wed Oct 22 00:55:17 PDT 2014 armv5tel GNU/Linux

I'm not sure about the u-boot version I have and rather not reboot the device.

Is it safe to make a `apt-get upgrade` ? Or should I install a 3.18/4.0 kernel first?

Debian Jessie comes with 3.16 kernel, so 3.17 should be fine, AFAIK

I'm currently upgrading my PogoV1 and will report back if everything worked.



Edited 1 time(s). Last edit at 04/26/2015 06:29AM by theliquid.

twonline,

> user@goflex:~$ uname -a
> Linux goflex 3.17.0-kirkwood-tld-1 #4 PREEMPT Wed
> Oct 22 00:55:17 PDT 2014 armv5tel GNU/Linux
>
> Is it safe to make a `apt-get upgrade` ? Or should
> I install a 3.18/4.0 kernel first?

It's OK to upgrade it. But you if you keep your apt source wheezy and do apt-get upgrade, then nothing big will happen. Only when you change apt sources to jessie and do apt-get dist-upgrade, that's when you do really need to backup your rootfs first.

And furthermore, since we are using customed build kernel, it is always better to upgrade to the latest here, and then do upgrade or dist-upgrade .

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 04/26/2015 06:41AM by bodhi.

Upgrade to Jessie worked flawlessly; I am on Kernel 4.0 with my PogoV1.



Edited 1 time(s). Last edit at 04/26/2015 07:42AM by theliquid.

Thank you both for your feedback. Will do the upgrade when time permits.

My goflex home is on the latest 4.0 kernel. I would like to upgrade it from wheezy to jessie.

I suppose I can follow bodhi's steps.

However, with the custom kernel, "apt-get -s upgrade" always reports a upgrade for "linux-image-3.2.0-4-kirkwood". I suppose "apt-get upgrade" in those steps would attempt to upgrade it. Will it screw up my system?



Edited 1 time(s). Last edit at 06/01/2015 10:24PM by sylvester.

sylvester,

Quote

I suppose I can follow bodhi's steps.

Yes.

> However, with the custom kernel, "apt-get -s
> upgrade" always reports a upgrade for
> "linux-image-3.2.0-4-kirkwood". I suppose
> "apt-get upgrade" in those steps would attempt to
> upgrade it. Will it screw up my system?

It will screw up the system.

Which kernel version are you running? is it from mainline or my realeased kernel? If you are running my custom kernel, and have removed flash-kernel, it will stay the same. The only things will be updated are debian packages, and the initramfs image, not the kernel image.

And the correct command to go full bown jessie is

apt-get dist-upgrade

Please post output of

uname -a

And if you could post your dmesg output here too, for completenes..

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/01/2015 11:22PM by bodhi.

Yes, I am using your release kernel. Never have flash-kernel in the system.

# uname -a
Linux goflex 4.0.0-kirkwood-tld-1 #1 PREEMPT Mon Apr 13 17:35:28 PDT 2015 armv5tel GNU/Linux

I usually do "apt-get -s upgrade" to get a list of updated packages and do "apt-get install" after that, avoiding the kernel package. So does it mean that I can actually run "apt-get upgrade" any time without any issues? Will it just update its own set of "kernel files" but not affecting the actual kernel my system runs on? Should I expect any "harmless" errors?

# dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.0.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.1 (Debian 4.9.1-19) ) #1 PREEMPT Mon Apr 13 17:35:28 PDT 2015
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Seagate GoFlex Home
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c0808398, node_mem_map c7ef9000
[    0.000000]   DMA zone: 256 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 32768 pages, LIFO batch:7
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 115748K/131072K available (5621K kernel code, 340K rwdata, 1988K rodata, 268K init, 302K bss, 15324K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc077669c   (7610 kB)
[    0.000000]       .init : 0xc0777000 - 0xc07ba000   ( 268 kB)
[    0.000000]       .data : 0xc07ba000 - 0xc080f22c   ( 341 kB)
[    0.000000]        .bss : 0xc080f22c - 0xc085ab3c   ( 303 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000016] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    0.000427] Console: colour dummy device 80x30
[    0.000457] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    0.090117] pid_max: default: 32768 minimum: 301
[    0.090239] Security Framework initialized
[    0.090337] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090358] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091127] Initializing cgroup subsys blkio
[    0.091157] Initializing cgroup subsys devices
[    0.091180] Initializing cgroup subsys freezer
[    0.091211] Initializing cgroup subsys net_cls
[    0.091313] CPU: Testing write buffer coherency: ok
[    0.091767] Setting up static identity map for 0x556470 - 0x5564c8
[    0.092050] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.094267] devtmpfs: initialized
[    0.096197] prandom: seed boundary self test passed
[    0.099955] prandom: 100 self tests passed
[    0.099978] pinctrl core: initialized pinctrl subsystem
[    0.105188] NET: Registered protocol family 16
[    0.105655] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.130118] cpuidle: using governor ladder
[    0.160116] cpuidle: using governor menu
[    0.160554] Feroceon L2: Enabling L2
[    0.160600] Feroceon L2: Cache support initialised.
[    0.160979] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.165486] No ATAGs?
[    0.201613] vgaarb: loaded
[    0.201995] usbcore: registered new interface driver usbfs
[    0.202077] usbcore: registered new interface driver hub
[    0.202144] usbcore: registered new device driver usb
[    0.203244] Switched to clocksource orion_clocksource
[    0.239379] NET: Registered protocol family 2
[    0.240135] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.240161] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.240182] TCP: Hash tables configured (established 1024 bind 1024)
[    0.240252] TCP: reno registered
[    0.240266] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.240288] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.240500] NET: Registered protocol family 1
[    0.240897] RPC: Registered named UNIX socket transport module.
[    0.240910] RPC: Registered udp transport module.
[    0.240917] RPC: Registered tcp transport module.
[    0.240924] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.240950] PCI: CLS 0 bytes, default 32
[    0.241213] Unpacking initramfs...
[    0.755450] Freeing initrd memory: 5552K (c75af000 - c7b1b000)
[    0.755594] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.756956] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.756989] Initialise system trusted keyring
[    0.757114] audit: initializing netlink subsys (disabled)
[    0.757171] audit: type=2000 audit(0.750:1): initialized
[    0.757949] zpool: loaded
[    0.757967] zbud: loaded
[    0.758304] VFS: Disk quotas dquot_6.5.2
[    0.758363] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.758980] NFS: Registering the id_resolver key type
[    0.759031] Key type id_resolver registered
[    0.759041] Key type id_legacy registered
[    0.759071] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.759088] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.759314] jffs2: version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9\xffffffa9 2001-2006 Red Hat, Inc.
[    0.759807] Key type big_key registered
[    0.762656] alg: No test for stdrng (krng)
[    0.762696] Key type asymmetric registered
[    0.762712] Asymmetric key parser 'x509' registered
[    0.762798] bounce: pool size: 64 pages
[    0.762889] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.762909] io scheduler noop registered
[    0.762923] io scheduler deadline registered
[    0.762971] io scheduler cfq registered (default)
[    0.764366] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.765048] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[    0.765475] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[    0.766009] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.803326] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    0.843310] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    0.843500] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.883309] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.923307] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.923737] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.925115] console [ttyS0] disabled
[    0.925178] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    1.520810] console [ttyS0] enabled
[    1.525653] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xda
[    1.532039] nand: Toshiba NAND 256MiB 3,3V 8-bit
[    1.536714] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.544344] Scanning device for bad blocks
[    1.767270] 4 cmdlinepart partitions found on MTD device orion_nand
[    1.773584] Creating 4 MTD partitions on "orion_nand":
[    1.778750] 0x000000000000-0x000000100000 : "u-boot"
[    1.784178] 0x000000100000-0x000000500000 : "uImage"
[    1.789571] 0x000000500000-0x000002500000 : "rootfs"
[    1.795021] 0x000002500000-0x000010000000 : "data"
[    1.801403] libphy: Fixed MDIO Bus: probed
[    1.805858] libphy: orion_mdio_bus: probed
[    1.817242] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.903984] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:2a:23:13
[    2.912941] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.919532] ehci-pci: EHCI PCI platform driver
[    2.924083] ehci-orion: EHCI orion driver
[    2.928293] orion-ehci f1050000.ehci: EHCI Host Controller
[    2.933861] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    2.941703] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    2.963281] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    2.969510] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.976360] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.983634] usb usb1: Product: EHCI Host Controller
[    2.988534] usb usb1: Manufacturer: Linux 4.0.0-kirkwood-tld-1 ehci_hcd
[    2.995197] usb usb1: SerialNumber: f1050000.ehci
[    3.000667] hub 1-0:1.0: USB hub found
[    3.004521] hub 1-0:1.0: 1 port detected
[    3.009331] mousedev: PS/2 mouse device common for all mice
[    3.015640] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    3.022705] i2c /dev entries driver
[    3.027671] hidraw: raw HID events driver (C) Jiri Kosina
[    3.033494] drop_monitor: Initializing network drop monitor service
[    3.040028] TCP: cubic registered
[    3.043407] NET: Registered protocol family 17
[    3.047994] Key type dns_resolver registered
[    3.053151] Loading compiled-in X.509 certificates
[    3.058026] registered taskstats version 1
[    3.063171] rtc-mv f1010300.rtc: setting system clock to 2015-04-28 06:20:42 UTC (1430202042)
[    3.072985] PM: Hibernation image not present or could not be loaded.
[    3.074117] Freeing unused kernel memory: 268K (c0777000 - c07ba000)
[    3.134197] udevd[57]: starting version 175
[    3.323408] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    3.480064] SCSI subsystem initialized
[    3.495220] usb 1-1: New USB device found, idVendor=125f, idProduct=a11a
[    3.501983] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[    3.521901] usb 1-1: Product: CH11
[    3.531519] usb 1-1: Manufacturer: ADATA
[    3.535555] usb 1-1: SerialNumber: 1204800911050600006A
[    3.571092] libata version 3.00 loaded.
[    3.577666] sata_mv f1080000.sata: version 1.28
[    3.577888] sata_mv f1080000.sata: slots 32 ports 1
[    3.613470] scsi host0: sata_mv
[    3.623984] ata1: SATA max UDMA/133 irq 32
[    3.685184] usb-storage 1-1:1.0: USB Mass Storage device detected
[    3.691662] scsi host1: usb-storage 1-1:1.0
[    3.697821] usbcore: registered new interface driver usb-storage
[    3.707028] usbcore: registered new interface driver uas
[    4.133365] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[    4.173325] ata1.00: ATA-8: ST3500320AS, SD1A, max UDMA/133
[    4.178929] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    4.243366] ata1.00: configured for UDMA/133
[    4.263655] scsi 0:0:0:0: Direct-Access     ATA      ST3500320AS      SD1A PQ: 0 ANSI: 5
[    4.292472] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[    4.301382] sd 0:0:0:0: [sda] Write Protect is off
[    4.306371] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    4.306508] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    4.358049]  sda: sda1 sda2 sda3 sda4
[    4.364837] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.381439] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    6.447706] scsi 1:0:0:0: Direct-Access     ADATA    CH11             AX00 PQ: 0 ANSI: 5
[    6.464509] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[    6.472161] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    6.481920] sd 1:0:0:0: [sdb] Write Protect is off
[    6.493039] sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00
[    6.493768] sd 1:0:0:0: [sdb] No Caching mode page found
[    6.499114] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[    6.520744]  sdb: sdb1
[    6.537641] sd 1:0:0:0: [sdb] Attached SCSI disk
[   16.384198] udevd[277]: starting version 175
[   17.268006] orion_wdt: Initial timeout 21 sec
[   17.322267] random: nonblocking pool is initialized
[   18.628882] Adding 373756k swap on /dev/sda2.  Priority:-1 extents:1 across:373756k FS
[   23.903414] kjournald starting.  Commit interval 5 seconds
[   23.909401] EXT3-fs (sdb1): using internal journal
[   23.914264] EXT3-fs (sdb1): mounted filesystem with ordered data mode
[   25.392194] NET: Registered protocol family 10
[   26.636985] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   28.309052] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 100 Mb/s, full duplex, flow control disabled
[   28.318893] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

@sylvester,

It wont affect the current kernel, since your uimage and uinitrd are generated from that set of kernel files. However, you should purge the old kernels to free up space any way:

dpkg -l | grep linux-image

And then purge each one (where linux-image-3.2.xx.xx is each one in the list of old kerlnels):

dpkg --purge linux-image-3.2.xx.xx

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Upgrade completed. Thanks, bodhi.

I just carried out "apt-get upgrade" the first time after upgrading to jessie.

I noticed it regenerated initrd.img in the last step:

Setting up php5 (5.6.9+dfsg-0+deb8u1) ...
Processing triggers for libc-bin (2.19-18) ...
Processing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-4.0.0-kirkwood-tld-1

Is that normal? Should I be worried? Do I need to regenerate uInitrd?

sylvester Wrote:
-------------------------------------------------------
> I just carried out "apt-get upgrade" the first
> time after upgrading to jessie.
>
> I noticed it regenerated initrd.img in the last
> step:
>
>

> Setting up php5 (5.6.9+dfsg-0+deb8u1) ...
> Processing triggers for libc-bin (2.19-18) ...
> Processing triggers for initramfs-tools (0.120)
> ...
> update-initramfs: Generating
> /boot/initrd.img-4.0.0-kirkwood-tld-1
>

>
> Is that normal? Should I be worried? Do I need
> to regenerate uInitrd?

Yes, it is normal. And you do need to regenerate uInitrd so that the new packages hooks are used. Old uInird is still usable for booting, but will point to the older hooks.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/07/2015 11:09PM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> Yes, it is normal. And you do need to regenerate
> uInitrd so that the new packages hooks are used.
> Old uInird is still usable for booting, but will
> point to the older hooks.


So does it mean that every time I do apt-get upgrade I need to regenerate uInitrd?

In that case I may as well just capture the list of upgraded packages with "apt-get -s upgrade" and do apt-get install instead.

sylvester Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > Yes, it is normal. And you do need to
> regenerate
> > uInitrd so that the new packages hooks are
> used.
> > Old uInird is still usable for booting, but
> will
> > point to the older hooks.
>
>
> So does it mean that every time I do apt-get
> upgrade I need to regenerate uInitrd?
>
> In that case I may as well just capture the list
> of upgraded packages with "apt-get -s upgrade"
> and do apt-get install instead.

No, you should do apt-get upgrade and watch if initrd img is regenerated (most of the time it stays the same). Then remake uInitrd it needed.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I see. Thanks for the info.

I just noticed I can't do ping as a normal user. Okay with root or sudo.

$ ping 127.0.0.1
ping: icmp open socket: Operation not permitted

Not too sure when this issues started, however,

Permission check:
$ ls -l /bin/ping
-rwxr-xr-x 1 root root 38840 Nov 9 2014 /bin/ping

From my old backup just before upgrading to Jessie:
-rwsr-xr-x 270 root root 34936 Apr 13 2011 bin/ping

My questions:
1. Is this behaviour normal with Jessie?
2. Is the permission for the version in Jessie correct?

Edit:
I read some references to the libcap2-bin in Debian that supposedly enable the ping. When I tried
$ getcap /bin/ping

Nothing returns. Do I supposedly to get something like:
/bin/ping = cap_net_raw+p


Thanks.



Edited 1 time(s). Last edit at 07/12/2015 10:55PM by sylvester.

sylvester,

> 1. Is this behaviour normal with Jessie?
> 2. Is the permission for the version in Jessie
> correct?

Yes. But you can set the sticky bit to allow normal user to ping

chmod u+s /bin/ping

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

>
> > 1. Is this behaviour normal with Jessie?
> > 2. Is the permission for the version in Jessie
> > correct?
>
> Yes. But you can set the sticky bit to allow
> normal user to ping
>

Thanks, bodhi.

I thought I may have screwed it up when I restore my system after a disk failure. Good to know my backup and restore are in fact okay.

A bit out off topic: I have experienced disk failure twice since I put debian on my goflex home 20 months ago and running it 24x7. I have the whole system running off the SATA disk.

I wonder it is just me or others in the community also experience disk problem so often.

sylvester,

> A bit out off topic: I have experienced disk
> failure twice since I put debian on my goflex home
> 20 months ago and running it 24x7. I have the
> whole system running off the SATA disk.

Is it GoFlex Net or GoFlex Home?

By "disk failure" you meant the disk failed, or the file system was corrupted? If the disk failed completely and became unusable then it might be other factors. But if it can be revived with low level formatting then the cause might have been power supply.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> sylvester,
>
> > A bit out off topic: I have experienced disk
> > failure twice since I put debian on my goflex
> home
> > 20 months ago and running it 24x7. I have the
> > whole system running off the SATA disk.
>
> Is it GoFlex Net or GoFlex Home?
>
> By "disk failure" you meant the disk failed, or
> the file system was corrupted? If the disk failed
> completely and became unusable then it might be
> other factors. But if it can be revived with low
> level formatting then the cause might have been
> power supply.

GoFlex Home.

Not file system problem. Disk I/O error.

The first one was sent back to Seagate (still under warranty at the time). Unfortunately I have got rid of the second one. Will bear that in mind if it happens again (hope not :)

Thanks.

sylvester Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > sylvester,
> >
> > > A bit out off topic: I have experienced disk
> > > failure twice since I put debian on my goflex
> > home
> > > 20 months ago and running it 24x7. I have
> the
> > > whole system running off the SATA disk.
> >
> > Is it GoFlex Net or GoFlex Home?
> >
> > By "disk failure" you meant the disk failed, or
> > the file system was corrupted? If the disk
> failed
> > completely and became unusable then it might be
> > other factors. But if it can be revived with
> low
> > level formatting then the cause might have been
> > power supply.
>
> GoFlex Home.
>

GoflexHome should have 2A power supply.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
>
> GoflexHome should have 2A power supply.


I am using the power supply came with the unit. No good?

sylvester Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> >
> > GoflexHome should have 2A power supply.
>
>
> I am using the power supply came with the unit.
> No good?

It should be OK. But doublecheck the power rating (printed on the unit), just to be sure it's 2A.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)