similar to: problem mounting external drive

Hi all, I'm running a pretty updated CentOS4 x86_64 server (Still on kernel 2.6.9-42.0.2, but appart from that fully up to date against the official repos) with a USB-disk attached (the USB-disk is a 750G Seagate disk in a Seagate enclosure) over a USB hub. I've noticed several times that after longish periods of activity, the disk drops out (log from last time, below). In this case,

Il 30/01/19 16:49, Simon Matter ha scritto: >> On 01/30/19 03:45, Alessandro Baggi wrote: >>> Il 29/01/19 20:42, mark ha scritto: >>>> Alessandro Baggi wrote: >>>>> Il 29/01/19 18:47, mark ha scritto: >>>>>> Alessandro Baggi wrote: >>>>>>> Il 29/01/19 15:03, mark ha scritto: >>>>>>>

Hi, When I upgraded my cluster, df started returning some odd numbers for my legacy volumes. Newly created volumes after the upgrade, df works just fine. I have been researching since Monday and have not found any reference to this symptom. "vm-images" is the old legacy volume, "test" is the new one. [root at st-srv-03 ~]# (df -h|grep bricks;ssh st-srv-02 'df -h|grep

Hi, I have a 'little' issue with my bootable USB keys... The following used to work (isolinux 3.11-4): Device Boot Start End Blocks Id System /dev/sdg1 * 1 3 23126 6 FAT16 /dev/sdg2 4 1023 7873380 83 Linux mkfs.vfat -n BOOT /dev/sdg1 mkfs.ext2 -m 0 -b 4096 -L DATA /dev/sdg2 syslinux -s /dev/sdg1 cd

Hello, new Linux user here and I cannot mount a new (empty) WD MyBook Essentials 3TB USB external hard drive (Model WDBACW0030HBK-NESN). I'm only about 3 weeks into this linux thing and so please forgive me if any of my syntax is off My linux OS is CentOS 5.4 x86-64 running on a dedicated HP z400. The WD MyBook is to back up the large data files we are creating on the HP400 (it's

I got the email that a drive in my 4-drive RAID10 setup failed. What are my options? Drives are WD1000FYPS (Western Digital 1 TB 3.5" SATA). mdadm.conf: # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md/root level=raid10 num-devices=4 UUID=942f512e:2db8dc6c:71667abc:daf408c3 /proc/mdstat: Personalities : [raid10] md127 : active raid10 sdf1[2](F)

On 01/30/19 03:45, Alessandro Baggi wrote: > Il 29/01/19 20:42, mark ha scritto: >> Alessandro Baggi wrote: >>> Il 29/01/19 18:47, mark ha scritto: >>>> Alessandro Baggi wrote: >>>>> Il 29/01/19 15:03, mark ha scritto: >>>>> >>>>>> I've no idea what happened, but the box I was working on last week

I have a WD Elements 2TB USB hard drive. I would like to encrypt the whole drive with TrueCrypt on my CentOS box. Could someone direct me to a tutorial on how to do this? Ideally, I would also like to access it with my WinXP box, but this part is optional. Thanks for your help. Mike.

I see a really good price, and better for quantity, for 3TB drives. Now, I've been down on WD for a couple of years, since I found that they'd protected certain h/d parms from being changed (like TLER). The ones I'm looking at are the Red, which seems to be a new color (at least to me), and one technical review I've read says that they're intended for NAS, etc, and you can

Hi all, Please can you help with my ZFS troubles: I currently have 3 x 400 GB Seagate NL35''s and a 500 GB Samsung Spinpoint in a RAIDZ array that I wish to expand by systematically replacing each drive with a 750 GB Western Digital Caviar. After failing miserably, I''d like to start from scratch again if possible. When I last tried, the replace command hung for an age, network

I got a WD 1TB My Book with eSATA/USB/Firewire400 connectivity to backup data on a client Centos 5.1 machine. USB 2.0 works fine out of the box but is rather slow, Nautilus predicts about 1+ hour to fully backup just one day's worth of data or about 100GB. So I was hoping Firewire would be faster, which is why we got the version with all 3 interfaces to experiment with first. Following the

Alessandro Baggi wrote: > Il 29/01/19 15:03, mark ha scritto: > >> I've no idea what happened, but the box I was working on last week has >> a *second* bad drive. Actually, I'm starting to wonder about that >> particulare hot-swap bay. >> >> Anyway, mdadm --detail shows /dev/sdb1 remove. I've added /dev/sdi1... >> but see both /dev/sdh1 and

I have a desktop system with 2 ZFS mirrors. One drive in one mirror is starting to produce read errors and slowing things down dramatically. I detached it and the system is running fine. I can''t tell which drive it is though! The error message and format command let me know which pair the bad drive is in, but I don''t know how to get any more info than that like the serial number

I have 3 4TB WD drives I want to put in a RAID1 array. Two WD4000FYYZ and One WD4000F9YZ All enterprise class but two are WD Re and one is WD Se. I ordered the first two thinking 2 drives in the raid array would be sufficient but later decided its a long drive to the server so I would rather have 3 drives and ordered a third in accidentally did not get EXACT same thing. Would there be ANY

I was rsync'ing data from one system to another, and the recipient suddenly started throwing DRDY errors. Now, it's a fairly new WD Red 3TB, and I'd think it was just a bad drive... but I'm really confused by this, from the logs: Jun 15 15:34:43 <servername> kernel: ata3: SError: { Dispar } Dispar? And googling, every reference I find to that word always has something else

Hi list, I'm having one of those 'I'm stupid' -problems with LVM on CentOS 5.2. I've been working with traditional partitions until now, but I've finally been sold on the theoretical benefits of using LVM, but for now I only have a huge pile of broken filesystems to show for my efforts. My scenario; I attach a disk, either over USB or iSCSI. I create a PV on this

Another issue to tackle - I have an external 1 TB drive (2 500GB on a RAID). When I plug it into the server, it sees, via /var/log/messages, that a USB device was plugged in, but that's it. fdisk -l doesn't see it. dmesg doesn't do much, either. It is a Western Digital My Book II device. I want to format it and use it for external storage, but can't until I get to it.

Alessandro Baggi wrote: > Il 29/01/19 18:47, mark ha scritto: >> Alessandro Baggi wrote: >>> Il 29/01/19 15:03, mark ha scritto: >>> >>>> I've no idea what happened, but the box I was working on last week >>>> has a *second* bad drive. Actually, I'm starting to wonder about >>>> that particulare hot-swap bay. >>>>

Hi R users, I am trying to use the optim function to maximize a likelihood funciton, and I got the following warning messages. Could anyone explain to me what messege 31 means exactly? Is it a cause for concern? Since the value of convergence turns out to be zero, it means that the converging is successful, right? So can I assume that the parameter estimates generated thereafter are reliable MLE

A user's system had a hard drive failure over the weekend. Linux RAID 6. I identified the drive, brought the system down (8 drives, and I didn't know the s/n of the bad one. why it was there in the box, rather than where I started looking...) Brought it up, RAID not working. I finally found that I had to do an mdadm --stop /dev/md0, then I could do an assemble, then I could add the new