crazytony Posted February 12, 2011 Share Posted February 12, 2011 4.6 and 4.7 boot just fine but when I boot 5b4 and assign disks I get the following: I'm thinking that this is because that last disk is on the adaptec controller and didn't have a serial number in the array screen but did have one on the devices page. Thoughts on moving forward? Link to comment
Stokkes Posted February 12, 2011 Share Posted February 12, 2011 IMPORTANT Does that drive that's indicated in blue have any data on it or is it empty? IF IT CONTAINS DATA, DO NOT START YOUR ARRAY! I had the same thing happen on thankfully a mostly empty disk (just a few time machine backup tests) and it was formatted, nuking everything on the disk. unRAID didn't detect the "signature" and nuked it with impunity. You may want to revert back to 4.7 and wait for these 5.0 bugs to be ironed out. Link to comment
crazytony Posted February 12, 2011 Author Share Posted February 12, 2011 it has a little data on it -- I was thinking that it would format and rebuild from parity in the worst case scenario. Good to know that it's a tactical nuke. :'( Have already swapped the 4.6 and the 5b4 sticks and the array is back and operational. Link to comment
Stokkes Posted February 12, 2011 Share Posted February 12, 2011 I'm not saying it's a tactical nuke, but you never know unRAID writes a signature to the mbr that tells the system it's a valid unraid drive. If it's blue, it's almost as though it hasn't detected anything on the drive and you run the risk of having it nuked but not rebuilt upon array start. As much as I enjoy 5.0, there are still some weird quirks that need to be worked out. Link to comment
limetech Posted February 12, 2011 Share Posted February 12, 2011 Before you 'start' that array, please post output of this command: ls -l /dev/disk/by-id Link to comment
crazytony Posted February 12, 2011 Author Share Posted February 12, 2011 I'm currently in the process of backing up the data on that disk. Here is what the output for 4.6 looks like: lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-02-12 11:38 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516 -> ../../sda lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417 -> ../../sdb lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-02-12 11:38 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-02-12 11:38 usb-HP_v220w_0000000000002C-0:0 -> ../../sdi once I have the data backed up, I will boot into 5.0b4 and let you know what that looks like. Link to comment
crazytony Posted February 12, 2011 Author Share Posted February 12, 2011 sorry about the delay. Only had to move over about 500GB but I wasn't paying attention and I used rsync with the -z option. Whoops. lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 12 19:30 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516 -> ../../sda lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA0765516-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-1ATA_WDC_WD20EARS-00MVWB0_WD-WMAZA3483417-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615 -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20101615-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383 -> ../../sdg lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20116383-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386 -> ../../sde lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZ20187386-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817 -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0368817-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846 -> ../../sdh lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0371846-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 12 19:30 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1669301-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 usb-SanDisk_Cruzer_Blade_2005173882162BA1275E-0:0 -> ../../sdi lrwxrwxrwx 1 root root 10 Feb 12 19:30 usb-SanDisk_Cruzer_Blade_2005173882162BA1275E-0:0-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee057a1e164 -> ../../sdh lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee057a1e164-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee0acf775ca -> ../../sdf lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee0acf775ca-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee6002f406d -> ../../sdc lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee6002f406d-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee6558480fa -> ../../sde lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee6558480fa-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee655854d3e -> ../../sdg lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee655854d3e-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Feb 12 19:30 wwn-0x50014ee6ab379741 -> ../../sdd lrwxrwxrwx 1 root root 10 Feb 12 19:30 wwn-0x50014ee6ab379741-part1 -> ../../sdd1 thoughts? I have a feeling that if I push that button, I can't go back to 4.6 or 4.7 without pushing that button again.... Link to comment
crazytony Posted February 12, 2011 Author Share Posted February 12, 2011 ok I punched it because I desperately want the 5.0 kernel. Will let you know in 13 hours. Link to comment
lionelhutz Posted February 12, 2011 Share Posted February 12, 2011 It does say it's upgrading the disk and rebuilding the data so I suspect you will be OK and the disk will rebuild rather than clear. It appears the disk was identified differently and 5.0b4 likely didn't drop the -1ATA_ from beginning of the s/n. Another question, where is disk WD-WMAZA3483417 being used? I see 8 disks in your lists but only 7 on your screen capture. I'm wondering if setting your motherboard and/or that expansion card to use AHCI would help. Peter Link to comment
crazytony Posted February 12, 2011 Author Share Posted February 12, 2011 It looks like it rebuilt just fine. I'm checking md5 sums now. Update: md5sums are all ok between the backup and the restored disk. I keep a warm swap disk: precleared but not added to the array just in case a disk dies. Whenever I need capacity, I buy another disk, preclear it and add the warm swap. I think the reason the mobo is not set to AHCI is that I had problems booting with 6 disks plugged in. I'll have to check -- it's been about 6 months since I built the thing. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.