Reply
SanDisk User
Posts: 23
Registered: ‎05-10-2015

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB

I've been having the same problem ever since April 15, when I bought a Sandisk Cruzer Ultra USB 3.0 32GB to which I dd-ed the image of my 16GB SanDisk Cruzer Glide.

 

I contacted tech support and after arguing with the rep, who was barely knowledgeable regarding anything IT related, I got transferred and the rep came back and said that his supervisor had approved an RMA. I asked if I could just get a reference number for the case, so I could try to debug the problem, and if I wasn't successful, I'd RMA the drive.

 

The problem is exactly the same as yours :

 

 

/init: line 7: can't open /dev/sr0: No medium found

 

 

and then, after a while :

 

 

(initramfs)Unable to find a medium containing a live file system.

 

 

I did extensive debugging : I enabled early kernel debug/printk messages, maximum loglevel, "set -vx" in init and /scripts/casper in a custom initrd.lz and sent everything over to a another machine running "netcat -u -l 6666" with the netconsole directive properly configured on the problem flash drive.

 

I looked at casper.log but I couldn't trace down the problem, even with "set -vx" enabled and debugging echos inserted into critical places. The netconsole output did show the possible cause though :

 

 

[   21.546102] usb 2-1.2: device descriptor read/64, error -110
[   26.733116] usb 2-1.2: device descriptor read/64, error -71
[   26.909409] usb 2-1.2: new high-speed USB device number 4 using ehci-pci
[   26.993284] usb 2-1.2: device descriptor read/64, error -71
[   27.181399] usb 2-1.2: device descriptor read/64, error -71
[   27.357527] usb 2-1.2: new high-speed USB device number 5 using ehci-pci
[   27.773693] usb 2-1.2: device not accepting address 5, error -71
[   27.845809] usb 2-1.2: new high-speed USB device number 6 using ehci-pci
[   28.262016] usb 2-1.2: device not accepting address 6, error -71
[   28.262219] hub 2-1:1.0: unable to enumerate USB device on port 2

 

So Linux is trying to enumerate the drive but fails, therefore it fails to mount the fat32/vfat partition which contains the filesystem.squashfs and hence "Unable to find a medium containing a live file system."

 

I tried this on four different machines, with different hardware.

 

As a last resort I wanted to rule out the possibility that my byte-by-byte copy from the previous drive had somehow screwed up the new drive's bootup process, so I wiped the disk and performed a fresh install of Linux Mint 17.1 Cinnamon 64-bit using Unetbootin -- same result, on all 4 different machines.

 

Today I RMA-ed the drive. I own dozens of flash sticks and I have never had a problem with any of them booting Linux. If SanDisk produces devices that somehow deviate from the official USB spec, then I'd strongly recommend anyone looking to boot Linux off of a USB flash drive select another manufacturer. We'll see -- In my RMA I said I wanted a drive with the same specs but with its firmware updated so as to support booting Linux.

 

Regards,

 

jdb2 

SanDisk Guru
Posts: 2,538
Registered: ‎07-23-2010

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB

Impressive debugging jdb2

 

IMO Rather than hardware issues possible problem areas include USB 3.0 drivers for Unetbootin and Cinnamon, 64-bit drivers for Unetbootin and Cinnamon and Unetbootin and Mint 17.1 Cinnamon 64-bit themselves. 

 

Try using a different boot utility, see if that helps.  I like Easy2Boot.  Try using Cinnamon 17.1 32-bit version. 

Ed
Important files = Backed up files
SanDisk User
Posts: 23
Registered: ‎05-10-2015

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB


Ed_P wrote:

Impressive debugging jdb2

 

IMO Rather than hardware issues possible problem areas include USB 3.0 drivers for Unetbootin and Cinnamon, 64-bit drivers for Unetbootin and Cinnamon and Unetbootin and Mint 17.1 Cinnamon 64-bit themselves. 

 

Try using a different boot utility, see if that helps.  I like Easy2Boot.  Try using Cinnamon 17.1 32-bit version. 


 

You're welcome Smiley Happy

 

In "hardware issues,"  I didn't mean to say that the drive is defective per se, but that it is somehow incompatible with the Linux boot process, due to a deviation from the USB 3.0 spec -- I have several other USB 3.0 drives which boot this version of Mint just fine.

 

To this end, I plugged the drive into two systems which were only USB 2.0 capable. I got the same results. I tried enabling and disabling all combination s of "BIOS EHCI Handoff," "BIOS XHCI Handoff," "Legacy USB emulation" and "Legacy floppy drive emulation," all with the same results. Then I tried to boot the drive in a system with native USB 3.0 ports which was configured to use UEFI. This time I got a Grub boot prompt, but the end result was the same : "unable to find live file system" . I then disabled and enabled all combinations of the aforementioned settings, with no success. So, I turned UEFI off -- no success. I then disabled USB 3.0 in the BIOS and told it to emulate a USB 2.0 controller -- still no success.

 

I could grab the latest upstream mainline kernel source for Linux Mint 17.1 64-bit, configure the kernel with USB 3.0 support turned off  ( #CONFIG_USB_XHCI_HCD ), compile said kernel, and remaster a new Mint live DVD. But, I've already wiped the drive I'm RMA-ing and I intend to return it soon, so there's no point in going through the trouble with this particular drive. If the replacement has the same problems, I'll do the above.

 

Regards,

 

jdb2

 

SanDisk User
Posts: 72
Registered: ‎04-02-2015

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB

Thanks for the pointers Jdb, now it makes a whole lot of sense.

SanDisk User
Posts: 23
Registered: ‎05-10-2015

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB


sauberlime wrote:

Thanks for the pointers Jdb, now it makes a whole lot of sense.


I have an autism spectrum disorder ( Asperger's ), so I may be way off on this, but do I detect a hint of sarcasm or facetiousness? Smiley Tongue I know I went out on a technical tangent. Smiley Wink

 

 

Regards,

 

jdb2

SanDisk Guru
Posts: 2,538
Registered: ‎07-23-2010

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB

jdb2, when you get your new drive be sure to clone it.  And do a hex display of the first block.  The first block will either appear as a MBR or a BPB (Bios Parameter Block) of a "superfloppy".

Ed
Important files = Backed up files
SanDisk User
Posts: 23
Registered: ‎05-10-2015

Re: can't boot a Mint Cin 17.1 live Sandisk Ultra Fit 3.0 32GB


Ed_P wrote:

jdb2, when you get your new drive be sure to clone it.  And do a hex display of the first block.  The first block will either appear as a MBR or a BPB (Bios Parameter Block) of a "superfloppy".


Thanks for the tip! Smiley Happy When I receive the RMA-ed replacement drive I'll clone it and perform a hex dump -- I'll post the results, or a link to the results, in this thread.

 

Regards,

 

jdb2

SanDisk User
Posts: 23
Registered: ‎05-10-2015

Ok, here we go again -- again, again and again. I don't k...

[ Edited ]

Ok, here we go again -- again, again and again. I don't know if someone is deleting my posts or they just aren't being posted/saved. Sorry if this is a dup.

 

 


 

 

I received the RMA-ed drive a few days ago. The drive looks the same, except that the activity LED has been moved towered the lowe left, it's read/orange instead of blue and it blinks more rapidly. Also, I noticed that the read speed was at least twice that of the drive which I RMA-ed.

 

Here's some info on the drive :

 

mint@mint /media/mint/c6dc16a4-8ea0-470c-a196-d1eb5c84a170 $ file sandisk-ultra-rma.img 
sandisk-ultra-rma.img: x86 boot sector
mint@mint ~ $ file sector0.bin 
sector0.bin: x86 boot sector
mint@mint ~ $ sudo smartctl -a -T verypermissive -d scsi /dev/sdg
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-37-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SanDisk
Product:              SanDisk Ultra
Revision:             PMAP
User Capacity:        31,625,052,160 bytes [31.6 GB]
Logical block size:   512 bytes
scsiModePageOffset: response length too short, resp_len=4 offset=12 bd_len=8
Logical Unit id:      [censored for privacy reasons]
Serial number:        [censored for privacy reasons]
Device type:          disk
scsiModePageOffset: response length too short, resp_len=4 offset=12 bd_len=8
Local Time is:        Fri May 22 18:33:08 2015 CDT
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Error Counter logging not supported

scsiModePageOffset: response length too short, resp_len=4 offset=12 bd_len=8
Device does not support Self Test logging
mint@mint /media/mint/c6dc16a4-8ea0-470c-a196-d1eb5c84a170 $ sudo udevadm info --query=all --name=sdg
P: /devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/host19/target19:0:0/19:0:0:0/block/sdg
N: sdg
S: disk/by-id/usb-SanDisk_SanDisk_Ultra_[censored for privacy reasons]-0:0
S: disk/by-path/pci-0000:00:1a.7-usb-0:2:1.0-scsi-0:0:0:0
E: DEVLINKS=/dev/disk/by-id/usb-SanDisk_SanDisk_Ultra_[censored for privacy reasons]-0:0 /dev/disk/by-path/pci-0000:00:1a.7-usb-0:2:1.0-scsi-0:0:0:0
E: DEVNAME=/dev/sdg
E: DEVPATH=/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/host19/target19:0:0/19:0:0:0/block/sdg
E: DEVTYPE=disk
E: ID_BUS=usb
E: ID_INSTANCE=0:0
E: ID_MODEL=SanDisk_Ultra
E: ID_MODEL_ENC=SanDisk\x20Ultra\x20\x20\x20
E: ID_MODEL_ID=5581
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:00:1a.7-usb-0:2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_1a_7-usb-0_2_1_0-scsi-0_0_0_0
E: ID_REVISION=PMAP
E: ID_SERIAL=SanDisk_SanDisk_Ultra_[censored for privacy reasons]-0:0
E: ID_SERIAL_SHORT=[censored for privacy reasons]
E: ID_TYPE=disk
E: ID_USB_DRIVER=usb-storage
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk\x20
E: ID_VENDOR_ID=0781
E: MAJOR=8
E: MINOR=96
E: SUBSYSTEM=block
E: UDISKS_PARTITION_TABLE=1
E: UDISKS_PARTITION_TABLE_COUNT=1
E: UDISKS_PARTITION_TABLE_SCHEME=mbr
E: UDISKS_PRESENTATION_NOPOLICY=0
E: USEC_INITIALIZED=83772257093
mint@mint /media/mint/c6dc16a4-8ea0-470c-a196-d1eb5c84a170 $ sudo /lib/udev/udisks-part-id /dev/sdg
using device_file=/dev/sdg syspath=/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2/1-2:1.0/host19/target19:0:0/19:0:0:0/block/sdg, offset=0 ao=0 and number=0 for /dev/sdg
Entering MS-DOS parser (offset=0, size=31625052160)
MSDOS_MAGIC found
looking at part 0 (offset 4128768, size 31620923392, type 0x0c)
new part entry
looking at part 1 (offset 0, size 0, type 0x00)
new part entry
looking at part 2 (offset 0, size 0, type 0x00)
new part entry
looking at part 3 (offset 0, size 0, type 0x00)
new part entry
Exiting MS-DOS parser
MSDOS partition table detected
UDISKS_PARTITION_TABLE=1
UDISKS_PARTITION_TABLE_SCHEME=mbr
UDISKS_PARTITION_TABLE_COUNT=1
mint@mint ~ $ hexdump -C sector0.bin 
00000000  33 c0 8e d0 bc 00 7c fb  50 07 50 1f fc be 1b 7c  |3.....|.P.P....||
00000010  bf 1b 06 50 57 b9 e5 01  f3 a4 cb bd be 07 b1 04  |...PW...........|
00000020  38 6e 00 7c 09 75 13 83  c5 10 e2 f4 cd 18 8b f5  |8n.|.u..........|
00000030  83 c6 10 49 74 19 38 2c  74 f6 a0 b5 07 b4 07 8b  |...It.8,t.......|
00000040  f0 ac 3c 00 74 fc bb 07  00 b4 0e cd 10 eb f2 88  |..<.t...........|
00000050  4e 10 e8 46 00 73 2a fe  46 10 80 7e 04 0b 74 0b  |N..F.s*.F..~..t.|
00000060  80 7e 04 0c 74 05 a0 b6  07 75 d2 80 46 02 06 83  |.~..t....u..F...|
00000070  46 08 06 83 56 0a 00 e8  21 00 73 05 a0 b6 07 eb  |F...V...!.s.....|
00000080  bc 81 3e fe 7d 55 aa 74  0b 80 7e 10 00 74 c8 a0  |..>.}U.t..~..t..|
00000090  b7 07 eb a9 8b fc 1e 57  8b f5 cb bf 05 00 8a 56  |.......W.......V|
000000a0  00 b4 08 cd 13 72 23 8a  c1 24 3f 98 8a de 8a fc  |.....r#..$?.....|
000000b0  43 f7 e3 8b d1 86 d6 b1  06 d2 ee 42 f7 e2 39 56  |C..........B..9V|
000000c0  0a 77 23 72 05 39 46 08  73 1c b8 01 02 bb 00 7c  |.w#r.9F.s......||
000000d0  8b 4e 02 8b 56 00 cd 13  73 51 4f 74 4e 32 e4 8a  |.N..V...sQOtN2..|
000000e0  56 00 cd 13 eb e4 8a 56  00 60 bb aa 55 b4 41 cd  |V......V.`..U.A.|
000000f0  13 72 36 81 fb 55 aa 75  30 f6 c1 01 74 2b 61 60  |.r6..U.u0...t+a`|
00000100  6a 00 6a 00 ff 76 0a ff  76 08 6a 00 68 00 7c 6a  |j.j..v..v.j.h.|j|
00000110  01 6a 10 b4 42 8b f4 cd  13 61 61 73 0e 4f 74 0b  |.j..B....aas.Ot.|
00000120  32 e4 8a 56 00 cd 13 eb  d6 61 f9 c3 49 6e 76 61  |2..V.....a..Inva|
00000130  6c 69 64 20 70 61 72 74  69 74 69 6f 6e 20 74 61  |lid partition ta|
00000140  62 6c 65 00 45 72 72 6f  72 20 6c 6f 61 64 69 6e  |ble.Error loadin|
00000150  67 20 6f 70 65 72 61 74  69 6e 67 20 73 79 73 74  |g operating syst|
00000160  65 6d 00 4d 69 73 73 69  6e 67 20 6f 70 65 72 61  |em.Missing opera|
00000170  74 69 6e 67 20 73 79 73  74 65 6d 00 00 00 00 00  |ting system.....|
00000180  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  00 00 00 00 00 2c 44 63  98 bd 06 8b 00 00 00 00  |.....,Dc........|
000001c0  01 01 0c 57 58 ea 80 1f  00 00 80 60 ae 03 00 00  |...WX......`....|
000001d0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200

I've already installed Linux, via dd-ing my old Linux Mint 17.1 64-bit Cinnamon Live USB install from a USB 2.0 16GB SanDisk Cruzer flash drive to the new, RMA-ed, 32GB USB 3.0 SanDisk Cruzer Ultra. I've been booting off of it with no problems for days.

 

Instead of posting a link to the zipped sector 0, I'll uuencode it and post it as a code comment below ( use uudecode to get the binary ) :

 

begin-base64 644 sector0-uudecoded.bin
M8CO0LwAfPtQB1Af/L4bfL8bBlBXueUB86TLvb4HsQQ4bgB8CXUTg8UQ4vTN
GIv1g8YQSXQZOCx09qC1B7QHi/CsPAB0/LsHALQOzRDr8ohOEOhGAHMq/kYQ
gH4EC3QLgH4EDHQFoLYHddKARgIGg0YIBoNWCgDoIQBzBaC2B+u8gT7+fVWq
dAuAfhAAdMigtwfrqYv8HleL9cu/BQCKVgC0CM0TciOKwSQ/mIreivxD9+OL
0YbWsQbS7kL34jlWCncjcgU5RghzHLgBArsAfItOAotWAM0Tc1FPdE4y5IpW
AM0T6+SKVgBgu6pVtEHNE3I2gftVqnUw9sEBdCthYGoAagD/dgr/dghqAGgA
fGoBahC0Qov0zRNhYXMOT3QLMuSKVgDNE+vWYfnDSW52YWxpZCBwYXJ0aXRp
b24gdGFibGUARXJyb3IgbG9hZGluZyBvcGVyYXRpbmcgc3lzdGVtAE1pc3Np
bmcgb3BlcmF0aW5nIHN5c3RlbQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsRGOYvQaLAAAAAAEB
DFdY6oAfAACAYK4DAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAVao=
====

 

I'm saving the HTML source of this message ( again ), in case someone tries to delete my posts again, for no good reason.

 

 

Regards,

 

jdb2

 

 

EDIT : Apparently the subject was too long -- my posts were going to the bit bucket even when the forum CMS backend said that I had successfully posted a message. But, this SanDisk forum CMS software is crap and didn't give me clue as to the problem.

Newbie
Posts: 1
Registered: ‎06-04-2015

Re: Ok, here we go again

Hi jdb2,

 

I noticed that you are using different flash drive (Cruiser Ultra), but it looks like you know what you are doing (can't say that about me when it comes to linux).

I'm totally lost about sector0. Could you explain in more detail what to do with it, please? Do you think it could work on Ultra Fit flash drive?

I also noticed difference in partitions. Mine is:

looking at part 0 (offset 1048576, size 31098667008, type 0x0b)

whereas yours is:

looking at part 0 (offset 4128768, size 31620923392, type 0x0c)

 

Attaching rest of the logs:

mydlo@mint ~ $ sudo smartctl -a -T verypermissive -d scsi /dev/sdb
smartctl 6.2 2013-07-26 r3841 [i686-linux-3.13.0-37-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               SanDisk
Product:              Ultra Fit
Revision:             1.00
User Capacity:        31,104,958,464 bytes [31.1 GB]
Logical block size:   512 bytes
Serial number:        [censored]
Device type:          disk
Local Time is:        Wed Jun  3 23:54:00 2015 CEST
SMART support is:     Available - device has SMART capability.
SMART support is:     Enabled
Temperature Warning:  Disabled or Not Supported

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Error Counter logging not supported

Device does not support Self Test logging
mydlo@mint ~ $ sudo udevadm info --query=all --name=sdb
P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/host3/target3:0:0/3:0:0:0/block/sdb
N: sdb
S: disk/by-id/usb-SanDisk_Ultra_Fit_[censored]-0:0
S: disk/by-path/pci-0000:00:1d.7-usb-0:6:1.0-scsi-0:0:0:0
E: DEVLINKS=/dev/disk/by-id/usb-SanDisk_Ultra_Fit_[censored]-0:0 /dev/disk/by-path/pci-0000:00:1d.7-usb-0:6:1.0-scsi-0:0:0:0
E: DEVNAME=/dev/sdb
E: DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/host3/target3:0:0/3:0:0:0/block/sdb
E: DEVTYPE=disk
E: ID_BUS=usb
E: ID_INSTANCE=0:0
E: ID_MODEL=Ultra_Fit
E: ID_MODEL_ENC=Ultra\x20Fit\x20\x20\x20\x20\x20\x20\x20
E: ID_MODEL_ID=5583
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:00:1d.7-usb-0:6:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_1d_7-usb-0_6_1_0-scsi-0_0_0_0
E: ID_REVISION=1.00
E: ID_SERIAL=SanDisk_Ultra_Fit_[censored]-0:0
E: ID_SERIAL_SHORT=[censored]
E: ID_TYPE=disk
E: ID_USB_DRIVER=usb-storage
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=SanDisk
E: ID_VENDOR_ENC=SanDisk\x20
E: ID_VENDOR_ID=0781
E: MAJOR=8
E: MINOR=16
E: SUBSYSTEM=block
E: UDISKS_PARTITION_TABLE=1
E: UDISKS_PARTITION_TABLE_COUNT=1
E: UDISKS_PARTITION_TABLE_SCHEME=mbr
E: UDISKS_PRESENTATION_NOPOLICY=0
E: USEC_INITIALIZED=3636733
mydlo@mint ~ $ sudo /lib/udev/udisks-part-id /dev/sdb
using device_file=/dev/sdb syspath=/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/host3/target3:0:0/3:0:0:0/block/sdb, offset=0 ao=0 and number=0 for /dev/sdb
Entering MS-DOS parser (offset=0, size=31104958464)
MSDOS_MAGIC found
looking at part 0 (offset 1048576, size 31098667008, type 0x0b)
new part entry
looking at part 1 (offset 0, size 0, type 0x00)
new part entry
looking at part 2 (offset 0, size 0, type 0x00)
new part entry
looking at part 3 (offset 0, size 0, type 0x00)
new part entry
Exiting MS-DOS parser
MSDOS partition table detected
UDISKS_PARTITION_TABLE=1
UDISKS_PARTITION_TABLE_SCHEME=mbr
UDISKS_PARTITION_TABLE_COUNT=1

 

I will really appreciate if you could help me with this issue.

Thank you in advance,

mydlo

 

 

SanDisk User
Posts: 23
Registered: ‎05-10-2015

Re: Ok, here we go again


mydlo wrote:

Hi jdb2,

 

I noticed that you are using different flash drive (Cruiser Ultra), but it looks like you know what you are doing (can't say that about me when it comes to linux).

I'm totally lost about sector0. Could you explain in more detail what to do with it, please? Do you think it could work on Ultra Fit flash drive?

I also noticed difference in partitions. Mine is:

looking at part 0 (offset 1048576, size 31098667008, type 0x0b)

whereas yours is:

looking at part 0 (offset 4128768, size 31620923392, type 0x0c)

 

 

The "0x0c"  is due to the fact that I have the LBA flag set. 

 

Could you please run the following commands in a terminal? :

 

cd ~/

sudo dd if=/dev/sdX of=sector0.bin bs=512 count=1

xxd sector0.bin > sector0.hex

# Note : Please replace the "X" in "sdX" with the letter that corresponds to your USB flash drive's block device file.

After the above, you can either attach the .hex file or just post the hex listing in a CODE section.

 



I will really appreciate if you could help me with this issue.

Thank you in advance,

mydlo

 

 


You are welcome Smiley Happy

 

Regards,

 

jdb2