Ostrich Posted June 11, 2009 Share Posted June 11, 2009 hi all, been using unRAID successfully (very) for a few days now. Had it booting up and coming online very well, even used the method outlined in forum to x-fer all my files onto raid array via eSATA. However, now i have xferred files onto array, i removed some old unused hard drives from my unRAID server, and now it wont come online. It has green lights next to the HDDs (on web interface), and puts reds next to them if i try to swap them (and refers to the previously correct drive), but every time i click start it goes to "refresh", when i click refresh it acts like its offline again. HDDs were moved from sde and sdf to now sdb and sdd, sdc is the eSATA drive. sda appears to be the unRAID server (combined 2TB total). I copied across syslog, pasted below for trouble shooting. Problem appears to be it cannot identify one of the disks? (sda). sdb is the seagate 1TB, sdd is the WD 1TB that were previously mapped as sde and sdf. sdc is the WD 1TB connected as eSATA that i was planning on using as parity once everything was up and running. i also cant mount sdb and sdd manually. using free version (limit 3 HDDs) v4.4 at moment. all drives connected via highpoint rocketraid expansion card. Jun 12 09:28:22 Tower kernel: sata_mv: Highpoint RocketRAID BIOS CORRUPTS DATA on all attached drives, regardless of if/how they are configured. BEWARE! Jun 12 09:28:22 Tower kernel: sata_mv: For data safety, do not use sectors 8-9 on "Legacy" drives, and avoid the final two gigabytes on all RocketRAID BIOS initialized drives. Jun 12 09:28:22 Tower kernel: sata_mv 0000:02:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx Jun 12 09:28:22 Tower kernel: sata_mv 0000:02:00.0: setting latency timer to 64 Jun 12 09:28:22 Tower kernel: scsi5 : sata_mv Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] 4078080 512-byte hardware sectors (2088 MB) Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] 4078080 512-byte hardware sectors (2088 MB) Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through Jun 12 09:28:22 Tower kernel: sda: Jun 12 09:28:22 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Jun 12 09:28:22 Tower kernel: usb-storage: device scan complete Jun 12 09:28:22 Tower kernel: ata7: link is slow to respond, please be patient (ready=0) Jun 12 09:28:22 Tower kernel: ata7: SRST failed (errno=-16) Jun 12 09:28:22 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 12 09:28:22 Tower kernel: ata7: link online but device misclassified, retrying Jun 12 09:28:22 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 12 09:28:22 Tower kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x40) Jun 12 09:28:22 Tower kernel: ata7: link is slow to respond, please be patient (ready=0) Jun 12 09:28:22 Tower kernel: ata7: SRST failed (errno=-16) Jun 12 09:28:22 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 12 09:28:22 Tower kernel: ata7: link online but device misclassified, retrying Jun 12 09:28:22 Tower kernel: ata7: link is slow to respond, please be patient (ready=0) Jun 12 09:28:22 Tower kernel: ata7: SRST failed (errno=-16) Jun 12 09:28:22 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 12 09:28:22 Tower kernel: ata7: link online but device misclassified, retrying Jun 12 09:28:22 Tower kernel: ata7: link is slow to respond, please be patient (ready=0) Jun 12 09:28:22 Tower kernel: ata7: SRST failed (errno=-16) Jun 12 09:28:22 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 12 09:28:22 Tower kernel: ata7: link online but device misclassified, retrying Jun 12 09:28:22 Tower kernel: ata7: limiting SATA link speed to 1.5 Gbps Jun 12 09:28:22 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 12 09:28:22 Tower kernel: ata7.00: ATA-8: WDC WD10EADS-00L5B1, 01.01A01, max UDMA/133 Jun 12 09:28:22 Tower kernel: ata7.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) Jun 12 09:28:22 Tower kernel: ata7.00: configured for UDMA/133 Jun 12 09:28:22 Tower kernel: ata7: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x1 t4 Jun 12 09:28:22 Tower kernel: ata7: edma_err_cause=00000020 pp_flags=00000000, SError=00180000 Jun 12 09:28:22 Tower kernel: ata7.00: configured for UDMA/133 Jun 12 09:28:22 Tower kernel: ata7: EH complete Jun 12 09:28:22 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 12 09:28:22 Tower kernel: ata8.00: ATA-8: WDC WD10EACS-00D6B1, 01.01A01, max UDMA/133 Jun 12 09:28:22 Tower kernel: ata8.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) Jun 12 09:28:22 Tower kernel: ata8.00: configured for UDMA/133 Jun 12 09:28:22 Tower kernel: scsi 6:0:0:0: Direct-Access ATA ST31000340AS SD81 PQ: 0 ANSI: 5 Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB) Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB) Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 12 09:28:22 Tower kernel: sdb: Jun 12 09:28:22 Tower kernel: sd 6:0:0:0: [sdb] Attached SCSI disk Jun 12 09:28:22 Tower kernel: scsi 7:0:0:0: Direct-Access ATA WDC WD10EADS-00L 01.0 PQ: 0 ANSI: 5 Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB) Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] 1953525168 512-byte hardware sectors (1000205 MB) Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 12 09:28:22 Tower kernel: sdc: sdc1 Jun 12 09:28:22 Tower kernel: sd 7:0:0:0: [sdc] Attached SCSI disk Jun 12 09:28:22 Tower kernel: scsi 8:0:0:0: Direct-Access ATA WDC WD10EACS-00D 01.0 PQ: 0 ANSI: 5 Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] 1953525168 512-byte hardware sectors (1000205 MB) Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] 1953525168 512-byte hardware sectors (1000205 MB) Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Write Protect is off Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 12 09:28:22 Tower kernel: sdd: Jun 12 09:28:22 Tower kernel: sd 8:0:0:0: [sdd] Attached SCSI disk Jun 12 09:28:22 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Jun 12 09:28:22 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Jun 12 09:28:22 Tower emhttp: pci-0000:02:00.0-scsi-1:0:0:0 (sdb) ata-ST31000340AS_9QJ1567T Jun 12 09:28:22 Tower emhttp: pci-0000:02:00.0-scsi-2:0:0:0 (sdc) ata-WDC_WD10EADS-00L5B1_WD-WCAU49654684 Jun 12 09:28:22 Tower emhttp: pci-0000:02:00.0-scsi-3:0:0:0 (sdd) ata-WDC_WD10EACS-00D6B1_WD-WCAU44722880 Jun 12 09:28:22 Tower emhttp: get_fstype: open /dev/sdb1: No such file or directory Jun 12 09:28:22 Tower emhttp: get_fstype: open /dev/sdd1: No such file or directory Jun 12 09:28:22 Tower emhttp: shcmd (1): rmmod md-mod >>/var/log/go 2>&1 Jun 12 09:28:22 Tower emhttp: shcmd: shcmd (1): exit status: 1 Jun 12 09:28:22 Tower emhttp: shcmd (2): modprobe md-mod super=/boot/config/super.dat slots=0,0,8,16,8,48 >>/var/log/go 2>&1 Jun 12 09:28:22 Tower kernel: md: unRAID driver 0.95.0 installed Jun 12 09:28:22 Tower kernel: md: xor using function: p5_mmx (6588.000 MB/sec) Jun 12 09:28:22 Tower kernel: md: disk0 removed Jun 12 09:28:22 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:22 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:23 Tower kernel: md: disk0 removed Jun 12 09:28:23 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:23 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:24 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:24 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:24 Tower kernel: md: do_run: lock_rdev error: -6 Jun 12 09:28:24 Tower kernel: md: disk0 removed Jun 12 09:28:24 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:24 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:24 Tower emhttp: shcmd (: cp /etc/exports- /etc/exports Jun 12 09:28:24 Tower emhttp: shcmd (9): killall -HUP smbd Jun 12 09:28:24 Tower emhttp: shcmd (10): /etc/rc.d/rc.nfsd restart >/dev/null Jun 12 09:28:36 Tower kernel: md: disk0 removed Jun 12 09:28:36 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:36 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:40 Tower kernel: md: disk0 removed Jun 12 09:28:40 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:40 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:41 Tower kernel: md: disk0 removed Jun 12 09:28:41 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:41 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:41 Tower emhttp: shcmd (11): /etc/rc.d/rc.samba stop >/dev/null Jun 12 09:28:41 Tower emhttp: shcmd (12): /etc/rc.d/rc.nfsd stop >/dev/null Jun 12 09:28:42 Tower emhttp: shcmd (13): cp /etc/exports- /etc/exports Jun 12 09:28:42 Tower emhttp: shcmd (14): /etc/rc.d/rc.samba start >/dev/null Jun 12 09:28:42 Tower emhttp: shcmd (15): /etc/rc.d/rc.nfsd start >/dev/null Jun 12 09:28:42 Tower kernel: mdcmd (: start Jun 12 09:28:42 Tower kernel: md: disk0 removed Jun 12 09:28:42 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:42 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:42 Tower kernel: md: do_run: lock_rdev error: -6 Jun 12 09:28:42 Tower kernel: md: disk0 removed Jun 12 09:28:42 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:42 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:42 Tower emhttp: shcmd (16): cp /etc/exports- /etc/exports Jun 12 09:28:42 Tower emhttp: shcmd (17): killall -HUP smbd Jun 12 09:28:42 Tower emhttp: shcmd (18): /etc/rc.d/rc.nfsd restart >/dev/null Jun 12 09:28:43 Tower kernel: md: disk0 removed Jun 12 09:28:43 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:43 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:46 Tower kernel: md: disk0 removed Jun 12 09:28:46 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:46 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:49 Tower emhttp: Spinning up all drives... Jun 12 09:28:49 Tower kernel: md: disk0 removed Jun 12 09:28:49 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:49 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:51 Tower emhttp: shcmd (19): sync Jun 12 09:28:51 Tower emhttp: shcmd (20): /usr/sbin/hdparm -y /dev/sdb >/dev/null Jun 12 09:28:51 Tower emhttp: shcmd (21): /usr/sbin/hdparm -y /dev/sdd >/dev/null Jun 12 09:28:52 Tower kernel: md: disk0 removed Jun 12 09:28:52 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:52 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:54 Tower emhttp: Spinning up all drives... Jun 12 09:28:57 Tower kernel: md: disk0 removed Jun 12 09:28:57 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:57 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:28:59 Tower kernel: md: disk0 removed Jun 12 09:28:59 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:28:59 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Jun 12 09:29:00 Tower kernel: md: disk0 removed Jun 12 09:29:00 Tower kernel: md: import disk1: [8,16] (sdb) ST31000340AS 9QJ1567T offset: 63 size: 976762552 Jun 12 09:29:00 Tower kernel: md: import disk2: [8,48] (sdd) WDC WD10EACS-00D6B1 WD-WCAU44722880 offset: 63 size: 976762552 Link to comment
RobJ Posted June 11, 2009 Share Posted June 11, 2009 Howdy, and welcome to unRAID! It's almost always best to attach the entire syslog for analysis. It looks like you cut-and-pasted parts of the syslog, as if it was one continuous section, but there are important gaps within it, and a lot of important information is missing. There is a part of the controller setup of scsi5, but none of the drive setup for it. There is some of the initial drive setup for scsi7 and scsi8 (but not scsi6), then the final drive setup for scsi6, scsi7, and scsi8, but none of the controller setup for them. And the setup for sda is incomplete. Posting the entire syslog would still help, but I'll make some comments based on what I can see. sda appears to be a 2GB USB flash drive, (need the info directly above its setup), but un-partitioned! Later, the super.dat is loaded from an unRAID flash drive mounted as /boot, so unRAID is identifying its flash drive correctly, but something is wrong with its setup. It should be partitioned. Jun 12 09:28:22 Tower emhttp: pci-0000:02:00.0-scsi-1:0:0:0 (sdb) ata-ST31000340AS_9QJ1567T Jun 12 09:28:22 Tower emhttp: pci-0000:02:00.0-scsi-2:0:0:0 (sdc) ata-WDC_WD10EADS-00L5B1_WD-WCAU49654684 Jun 12 09:28:22 Tower emhttp: pci-0000:02:00.0-scsi-3:0:0:0 (sdd) ata-WDC_WD10EACS-00D6B1_WD-WCAU44722880 Of the 3 drives found, only sdc has a partition (sdc1), and therefore may have data on it. Drives sdb and sdd do not have any partitions, and therefore cannot be mounted, and are considered empty. The connection to sdc (on scsi7 - ata7) is unreliable. I don't know if it is because it is a bad eSATA cable, or a bad port, but it had considerable trouble identifying the attached drive, until it gave up on 3.0 Gbps and dropped to 1.5 Gbps. The drive and controller both support the full 3.0 Gbps, so the port, connection, connectors, or cable must be bad. When you completely change the array configuration, you will want to click the Restore button, which will throw out the old configuration (forget the old drives) and setup a fresh config. That would have prepared a new system to be populated with the new drives you have. I don't quite understand some of your post. You stated that you are using the free version, which has only 2 data drives, and you transferred files onto your array, but then removed hard drives, which would seem to imply the loss of the 2 data drives? I'm going to guess that what you meant was that you were *practicing* transferring data from your WD 1TB drive to the old drives, and are now setting up a new array to transfer the files to. By clicking the Restore button, you will have a new array, which should allow you to format the Seagate and the other WD, and then transfer all of the current good WD 1TB to them, then assign that WD as parity drive. all drives connected via highpoint rocketraid expansion card. Jun 12 09:28:22 Tower kernel: sata_mv: Highpoint RocketRAID BIOS CORRUPTS DATA on all attached drives, regardless of if/how they are configured. BEWARE! Jun 12 09:28:22 Tower kernel: sata_mv: For data safety, do not use sectors 8-9 on "Legacy" drives, and avoid the final two gigabytes on all RocketRAID BIOS initialized drives. This looks serious to me. I would be VERY hesitant to use this RocketRAID card for any unRAID drives! Link to comment
Joe L. Posted June 11, 2009 Share Posted June 11, 2009 Jun 12 09:28:22 Tower kernel: sata_mv: Highpoint RocketRAID BIOS CORRUPTS DATA on all attached drives, regardless of if/how they are configured. BEWARE! Jun 12 09:28:22 Tower kernel: sata_mv: For data safety, do not use sectors 8-9 on "Legacy" drives, and avoid the final two gigabytes on all RocketRAID BIOS initialized drives. This looks serious to me. I would be VERY hesitant to use this RocketRAID card for any unRAID drives! the full comment in the driver source code looks like this: + /* + * Highpoint RocketRAID PCIe 23xx series cards: + * + * Unconfigured drives are treated as "Legacy" + * by the BIOS, and it overwrites sector 8 with + * a "Lgcy" metadata block prior to Linux boot. + * + * Configured drives (RAID or JBOD) leave sector 8 + * alone, but instead overwrite a high numbered + * sector for the RAID metadata. This sector can + * be determined exactly, by truncating the physical + * drive capacity to a nice even GB value. + * + * RAID metadata is at: (dev->n_sectors & ~0xfffff) + * + * Warn the user, lest they think we're just buggy. + */ + printk(KERN_WARNING DRV_NAME ": Highpoint RocketRAID" + " BIOS CORRUPTS DATA on all attached drives," + " regardless of if/how they are configured." + " BEWARE!\n"); + printk(KERN_WARNING DRV_NAME ": For data safety, do not" + " use sectors 8-9 on \"Legacy\" drives," + " and avoid the final two gigabytes on" + " all RocketRAID BIOS initialized drives.\n"); I'd stay far far away from this disk controller... It is ONLY ok if you can completely control the partitioning, but on unRAID you cannot change the partitioning... and on unRAId you cannot avoid the last two gigabytes on each drive..., so there is no way to comply with the warnings. As they say in the movies... Danger, Will Robertson Joe L. Link to comment
Ostrich Posted June 11, 2009 Author Share Posted June 11, 2009 hi guys, thanks for the responses. I did some playing around (4am this morning, couldnt sleep thinking all my data disappeared) and your right the drives are appearing empty to unraid. I connected disks to another machine and tried some data recovery programs, all say there is no partition but one is able to scan the drive and recreate the contents, which it appears to be doing ok. So ill restore the info to another machine, and then resetup the raid array again. Link to comment
henris Posted October 21, 2009 Share Posted October 21, 2009 Jun 12 09:28:22 Tower kernel: sata_mv: Highpoint RocketRAID BIOS CORRUPTS DATA on all attached drives, regardless of if/how they are configured. BEWARE! Jun 12 09:28:22 Tower kernel: sata_mv: For data safety, do not use sectors 8-9 on "Legacy" drives, and avoid the final two gigabytes on all RocketRAID BIOS initialized drives. This looks serious to me. I would be VERY hesitant to use this RocketRAID card for any unRAID drives! the full comment in the driver source code looks like this: + /* + * Highpoint RocketRAID PCIe 23xx series cards: + * + * Unconfigured drives are treated as "Legacy" + * by the BIOS, and it overwrites sector 8 with + * a "Lgcy" metadata block prior to Linux boot. + * + * Configured drives (RAID or JBOD) leave sector 8 + * alone, but instead overwrite a high numbered + * sector for the RAID metadata. This sector can + * be determined exactly, by truncating the physical + * drive capacity to a nice even GB value. + * + * RAID metadata is at: (dev->n_sectors & ~0xfffff) + * + * Warn the user, lest they think we're just buggy. + */ + printk(KERN_WARNING DRV_NAME ": Highpoint RocketRAID" + " BIOS CORRUPTS DATA on all attached drives," + " regardless of if/how they are configured." + " BEWARE!\n"); + printk(KERN_WARNING DRV_NAME ": For data safety, do not" + " use sectors 8-9 on \"Legacy\" drives," + " and avoid the final two gigabytes on" + " all RocketRAID BIOS initialized drives.\n"); I'd stay far far away from this disk controller... It is ONLY ok if you can completely control the partitioning, but on unRAID you cannot change the partitioning... and on unRAId you cannot avoid the last two gigabytes on each drive..., so there is no way to comply with the warnings. As they say in the movies... Danger, Will Robertson Joe L. I stumbled upon this thread accidentally. I'm currently using Highpoint RocketRaid 2310 (4 port, SATA-II, PCI-E4x) in my UnRAID setup. Except for the initial setup hassle I haven't had any problems with the card or the drives attached to it. I have never seen such a syslog entry. However I was never able to use the BIOS initialised drives in UnRAID (like jbod or RAID1), full story in here http://lime-technology.com/forum/index.php?topic=3896.0. So all the drives connected to RR2310 are thus in "legacy" mode. To me it seems the most severe problem is with configured drives. Why I'm not seeing this message in my syslog (UnRAID 4.4.2)? I assume the driver comment was from v4.4.2 as it posted this summer. Most importantly do I need to worry? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.